Linux

Linux diagnostics for IT support

admin-tools creates an individual Bash script for selected system, network and Wi-Fi checks. Windows and Linux use separate diagnostic paths with their own commands and result views.

See a sample result

This static, entirely fictional Linux sample result is available without an account, script execution or upload.

Linux sample result

Checks can provide clues for these support cases

DNS or host names

Name resolution with getent and DNS queries with dig or nslookup show whether a selected name resolves. DNS configuration is also recorded.

Routing and network path

IPv4 and IPv6 routes and responding hops from tracepath or traceroute can show the local network path to a target.

TCP service unreachable or slow

A TCP check measures the connection to a selected host and port; connection errors, timeouts and timings are recorded. A result does not fix anything or establish a certain cause by itself.

A failed test can also result from filtering, the remote endpoint or temporary network conditions. By itself, it does not prove a fault.

Guide: troubleshoot Linux DNS problems systematically

How a real diagnosis works

  1. Sign inAn account is required to configure a real diagnosis and get the script.
  2. Choose checksChoose checks, targets and manual or automatic upload.
  3. Review and run the scriptRead admin-tools_Linux.sh before running it on Linux as a normal user: bash admin-tools_Linux.sh.
  4. Transfer the logWith manual upload, the log first stays on the computer and is then uploaded through “Results”. Automatic mode sends it over HTTPS and deletes it only after a confirmed successful response; otherwise it remains local.
  5. View the resultAfter server-side processing, the result appears in the results list.

Technical requirements

Linux, Bash and Python 3.8 or newer are required. The script runs as a normal user; execution as root is rejected. It installs no packages and makes no permanent changes. Selected checks run in sequence and write a local log file. Individual commands may be unavailable depending on the distribution, installed tools and permissions.

Checks in detail

System and hardware

  • Drive storageTotal and available bytes for local filesystems as a point-in-time snapshot; network and virtual filesystems are excluded.
  • MemoryTotal RAM and MemAvailable plus separate swap values when available.
  • CPU utilisationAggregate system CPU utilisation over about five seconds from kernel counter deltas; no process details. A short spike does not establish sustained load.
  • System uptimeUptime and, when available in /proc/stat, the last system start as a UTC timestamp.
  • Inode usageTotal, free and used inodes on local filesystems. Missing inodes can prevent new files even when storage space remains.
  • SystemHostname, system version, kernel, CPU, memory and the executing user.
  • Processes and driversProcesses without command-line arguments, plus kernel modules and PCI driver mappings.
  • Kernel modules and PCIReads loaded kernel modules and PCI devices with their driver mappings. Output may be unavailable depending on permissions or installed tools.

Network and connections

  • NetworkShares, adapters, IP addresses, DNS configuration, routes, connections and neighbour table.
  • IPv4 and IPv6 routingReads separate IPv4 and IPv6 routing tables. These tables show local network paths and may reveal internal network structure.
  • TCP and UDP connectionsReads active TCP and UDP endpoints with ss. Process details may be unavailable without sufficient permissions.
  • Proxy environmentThe check only reports whether relevant proxy environment variables are set; values and credentials are not read.

DNS and reachability

  • ReachabilityPing, name resolution, DNS query, traceroute and TCP port checks. These checks may generate network traffic.
  • HTTP/HTTPS reachabilityChecks only explicitly configured URLs with HEAD and a bounded GET fallback. Status and duration are recorded, not response content, cookies or full headers. 401/403 means the service responds but access is restricted.
  • TLS certificateChecks HTTPS with normal trust and host name validation plus SNI. Certificate validation is never bypassed; individual certificate details may be unavailable on failure.
  • IPv4/IPv6 comparisonResolves A and AAAA addresses and makes the same bounded number of TCP attempts per address family. A missing AAAA record or local IPv6 support alone is not an error.
  • DNS with dig or nslookupPerforms a DNS query. If dig is unavailable, nslookup is tried; if both tools are missing, the check is reported as unavailable.

Wi-Fi

  • Wi-FiNetworkManager devices, existing scan results, driver capabilities, adapters and profile names.
  • Wi-Fi capabilities and profilesReads driver capabilities, Wi-Fi adapters, and NetworkManager profile names and types. Passwords are not requested.

Data and limits

Depending on the selection, the diagnosis may process the hostname, Linux version, kernel, CPU, memory, username, process names, IP addresses, DNS, routing, connection and neighbour data, explicitly configured HTTP(S) URLs with response status and duration, TLS validity period and validation result, A/AAAA resolution and TCP results by address family, traceroute hops, kernel modules, PCI devices, Wi-Fi scan results and NetworkManager profile names. HTTP response content, cookies and full headers are not logged. Credentials, query strings and fragments are not accepted in HTTP(S) targets. The Linux diagnostics do not request Wi-Fi passwords, proxy credentials or process command lines.

Missing tools, restricted permissions and timeouts are reported as technical limitations. A failed ping or refused TCP connection alone does not prove a fault in the examined system. Full processing information is provided in the privacy policy.

Sign in to configure a diagnosis Privacy policy