[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#840327: stopped working, no helpful feedback



On Mon 10 Oct 2016 at 18:15:15 +0200, Daniel Pocock wrote:

> Package: cups
> Version: 1.7.5-11+deb8u1
> 
> Printing had been working fine for a long time but about 20 minutes ago
> I tried to print something and an error popup appeared in GNOME asking
> if I wanted to diagnose the printer.  My document appeared paused in the
> queue.

Printing "working fine" for a long time must indicate something to you.
Then it stops working. How is this a bug rather than a matter for
debian-user? Computer systems don't generally go into meltdown because
they feel unappreciated.

> I looked at /var/log/cups/*log and found nothing about the error

You had debug logging enabled?

> I went to the control panel and also the CUPS web interface on port 631
> and tried re-enabling the printer and each time I did that it failed again.
> 
> I looked at /var/log/daemon.log and observed:
> 
> hpcups[16590]: prnt/hpcups/HPCupsFilter.cpp 707: First raster data plane..
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 1...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 2...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 3...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 4...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 5...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 6...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 7...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 8...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 9...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 10...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 11...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 12...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 13...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 14...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 15...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 16...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 17...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 18...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 19...
> hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 20...
> hp[16592]: io/hpmud/jd.c 816: error timeout mdns lookup ABC123DEF.local
> hp[16592]: io/hpmud/jd.c 93: unable to read device-id
> hp[16592]: prnt/backend/hp.c 808: ERROR: open device failed stat=12:
> hp:/net/HP_LaserJet_3055?zc=ABC123DEF

This is a symptom indicating you have done something to the system. It
never happened before; why should it happen now? Things don't generally
occur out of the blue.
 
> I killed the cups process and modified /etc/cups/printers.conf to change
> the URI from:
> 
> DeviceURI hp:/net/HP_LaserJet_3055?zc=ABC123DEF
> 
> to something like:
> 
> DeviceURI hp:/net/HP_LaserJet_3055?ip=192.168.1.234
> 
> 
> and started cups again and now printing works again.
> 
> What is really wrong here?

Who knows? Having to do this is a sign of a non-optimal setup in some
way. You are the one in charge of the system. You've not touched
anything in the last year (or twenty minutes)?
 
> Why did the popup not tell me the root cause of the problem?  Why did I
> have to go hunting around in the log files like this?  How many
> non-developers would be comfortable troubleshooting a problem like that
> without more details?

System administrators should always feel comfortable about trouble
shooting. Admit it; you really love log files. :)

I'd set up the print queue again from scratch. Maybe.

Regards,

Brian.


Reply to: