Debian Linux Triage

Debian Linux Triage is an AI skill that helps system administrators diagnose and resolve issues on Debian-based Linux systems. It provides structured troubleshooting workflows for APT package management problems, service failures, kernel issues, networking configuration, and system boot problems specific to the Debian ecosystem including stable, testing, and unstable release branches.

What Is This?

Overview

Debian Linux Triage delivers systematic diagnostic procedures tailored to Debian conventions and tooling. It understands APT and dpkg package management, systemd service administration, kernel module handling, network configuration through ifupdown and NetworkManager, and the Debian release cycle with its stability guarantees. When presented with error messages or symptoms, the skill identifies root causes and provides resolution steps that align with Debian best practices and package maintainer guidelines. This includes interpreting common APT error codes, recognizing patterns in dpkg output, and distinguishing between issues caused by local configuration changes versus upstream package updates.

Who Should Use This

This skill serves system administrators managing Debian servers in production environments, developers using Debian as their development platform, DevOps engineers maintaining Debian-based container images and infrastructure, and users running Debian derivatives such as Ubuntu or Linux Mint who encounter issues rooted in Debian-specific package behavior.

Why Use It?

Problems It Solves

Debian systems can encounter issues with held packages blocking upgrades, dependency conflicts when mixing release branches, services failing after configuration file changes during package updates, and kernel module incompatibilities after upgrades. The conffile prompt system during package upgrades can leave configurations in unexpected states when administrators choose incorrectly. Unattended upgrades can also introduce these problems silently, making post-upgrade triage particularly valuable in automated environments.

Core Highlights

The skill provides APT-specific diagnostic commands that reveal dependency trees, held packages, and repository configuration issues. It includes dpkg recovery procedures for interrupted installations, systemd journal analysis patterns for service debugging, and kernel management workflows for handling DKMS module failures. Each diagnostic path prioritizes non-destructive investigation before suggesting system modifications.

How to Use It?

Basic Usage

apt --fix-broken install --dry-run

apt-mark showhold

apt-cache depends package-name
apt-cache rdepends package-name

dpkg --configure -a

debsums --changed

Real-World Examples

systemctl status nginx
journalctl -u nginx --since "1 hour ago" --no-pager

dpkg --status nginx | grep -i conffile
find /etc/nginx -name "*.dpkg-*" -o -name "*.ucf-*"

diff /etc/nginx/nginx.conf /etc/nginx/nginx.conf.dpkg-dist

nginx -t
systemctl restart nginx

rm /etc/nginx/nginx.conf.dpkg-dist

Advanced Tips

Use apt-listchanges and needrestart packages to get advance notice of important changes during upgrades. The needrestart tool is particularly useful on long-running servers where updated libraries are loaded by services that have not yet been restarted. Pin critical packages to specific versions using APT preferences when stability is more important than staying current. Before major upgrades, save the current package state with dpkg get-selections for quick recovery if needed.

When to Use It?

Use Cases

Use Debian Linux Triage when APT dependency resolution fails and blocks system updates, when services break after package upgrades due to configuration changes, when the dpkg database becomes corrupted or an installation is interrupted, or when kernel upgrades cause module failures or boot issues.

Related Topics

APT package management, dpkg internals, systemd service debugging, Debian release upgrade procedures, kernel and DKMS module management, and unattended-upgrades configuration all complement the troubleshooting workflows this skill provides.

Important Notes

Requirements

Root or sudo access is required for most diagnostic and repair operations. The apt and dpkg tools must be functional for package-related troubleshooting. A bootable Debian USB should be available for situations requiring filesystem repair or chroot recovery. Network access to configured APT repositories is needed for package reinstallation and dependency resolution.

Usage Recommendations

Do: read APT and dpkg output carefully before accepting suggested resolutions. Keep the dpkg conffile backups until you have verified that services work correctly with the new configuration. Test major upgrades on a staging system before applying them to production servers.

Don't: force-remove packages with dpkg without checking reverse dependencies first, as this can trigger a cascade of broken dependencies. Mix packages from different Debian release branches without understanding APT pinning priorities. Delete files from /var/lib/dpkg manually, as this can corrupt the package database beyond easy recovery.

Limitations

The skill covers Debian stable, testing, and unstable branches. Third-party repository issues depend on the specific repository maintainer practices. Hardware-specific driver problems may require vendor documentation beyond standard Debian triage. Complex multi-architecture dependency conflicts sometimes need manual resolution beyond automated suggestions.