📖 ~1 min read
Table of contents
Symptom & Impact
Print jobs remain pending and documents are not produced.
Environment & Reproduction
Seen after network printer IP changes or backend errors.
lpstat -t
systemctl status cups
lpstat -p -d
Root Cause Analysis
Queue paused, stale backend URI, or filter crash blocks job processing.
Quick Triage
Check printer enablement and recent error logs.
lpstat -W not-completed
journalctl -u cups -n 120 --no-pager
lpoptions -p -l
Step-by-Step Diagnosis
Validate backend reachability and queue health.
lpstat -v
ping -c 3
sudo tail -n 100 /var/log/cups/error_log

Solution – Primary Fix
Purge stuck jobs, resume printer, and restart CUPS.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
cancel -a
cupsenable
cupsaccept
sudo systemctl restart cups

Solution – Alternative Approaches
Recreate printer with corrected URI and driver.
sudo lpadmin -x
sudo lpadmin -p -E -v ipp:///ipp/print -m everywhere
Verification & Acceptance Criteria
Test page prints and queue drains to zero jobs.
lp -d /etc/hosts
lpstat -W not-completed
lpstat -p
Rollback Plan
Restore previous printer definition from backup script.
lpstat -v > /var/tmp/printers.before.txt
# restore with saved lpadmin commands
Prevention & Hardening
Use static printer IP reservations and monitor CUPS errors.
journalctl -u cups --since -24h --no-pager | grep -i error
lpstat -t
Related Errors & Cross-Refs
Often paired with DNS failures for printer hostnames.
Related tutorial: View the step-by-step tutorial for Ubuntu 24.04 LTS.
View all Ubuntu 24.04 LTS tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Ubuntu CUPS administration and IPP Everywhere setup docs.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.