Troubleshooting¶
Basic troubleshooting¶
Connect to the office network
Check Uptime Kuma & Grafana
Check the confirm toolbox
Check the Filesystems
Check the systemd services
Useful commands¶
confirm toolbox¶
Use the confirm toolbox to get a fast overview:
confirm-server purpose # Prints the purpose of the server
confirm-server notes # Prints the notes for the server
confirm-server status # Prints the status of all required systemd service units
confirm-server info # Prints OS / hardware info
Filesystems¶
Check the filesystems by running the following command:
df -h
mount
systemd services¶
Check the failed systemd units by running the following command:
systemctl --failed
To get more information about a failed service, use one of the following commands:
systemctl status {service}
journalctl -fu {service}
To start, stop, or restart the service use the following commands:
systemctl start {service}
systemctl stop {service}
systemctl restart {service}
Infrastructure issues¶
There might already have been a similar issue with a server, or service. Thus there might be an issue which already describes that problem, and hopefully provides a solution, or workaround.
Just head over to the infrastructure issues and see if you can find something.
Hardware issues¶
Grub on UEFI systems¶
In case you’ve an UEFI-compatible mainboard and your BIOS is bitching around because it hasn’t found a bootable device, then you might have a problem with your GRUB installation. You need to ensure GRUB is installed properly for UEFI (instead of legacy x86/PC boot).
Boot a Debian Rescue system from an USB stick in UEFI mode and reinstall GRUB.
Important
You need to boot the USB stick in UEFI mode! You can check the boot mode by looking for a /sys/firmware/efi file. Is the file missing, your USB stick is booted in legacy mode instead of UEFI.
Hint
Debian has a good wiki page for GRUB EFI reinstall.