Had an interesting problem with my 10 year old HP PSC500 printer, whilst trying to print a PDF file from Document Viewer.
Not having been aware of changing anything since this last worked, I was assuming that my Ubuntu box's configuration hadn't changed drastically, and I'd already checked the power and parallel ( old skool ) printer cables.
The error message that kept popping up was: -
"Failed To Print Document, Too Many Failed Attempts"
which wasn't particularly meaningful.
I started and stopped the printer via the CUPS web UI at: -
http://localhost:631/printers/
but to no avail.
I'd also tried starting and stopping CUPS, via the shell commands: -
sudo service cups restart
When I checked the CUPS error log /var/logs/cups/error.log, I saw the following errors, which appeared relevant: -
E [31/Dec/2009:13:56:27 +0000] cupsdReadClient: 17 IPP Read Error!
E [31/Dec/2009:13:58:13 +0000] cupsdReadClient: 17 IPP Read Error!
E [31/Dec/2009:14:00:01 +0000] cupsdReadClient: 17 IPP Read Error!
A quick Google search suggested that the problem might be with Samba (!) rather than CUPS, even though I'm printing directly from the application on the PC to which the printer is connected.
Be that as it may, I tried restarting Samba: -
sudo service samba restart
and tried to reprint the offending document.
Lo and behold, the printer started printing and we're back in the game ....
Weird but true ...
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV
Subscribe to:
Post Comments (Atom)
TIL - read-only variables in Linux
A co-worker was seeing an exception: - line 8: TMOUT: readonly variable when trying to SCP a file from a remote Linux box. I did some digg...
-
After an unscheduled reboot of the VMs that host my K8s cluster, I was struggling to work out why the kubelet wasn't starting properly...
-
I hit a wee snag earlier today, whilst attempting to unpack some IBM software on my NAS. Being a command-line junkie, I'd SSH'd into...
-
I've just spent ~1 hour trying to get a pair of Powerline adapters to .... pair. This involved pressing a "Pair" button on one...
No comments:
Post a Comment