Hullo there,
I've just upgraded my debian amd64 server to etch. cups print server is now misbehaving.
If I use the web interface on ipp 631, clicking on any of the links request I use https:blah, rather than http:blah, and offer the URL, but following that link causes the page to hang and cupsys to be restarted. Previously I would be asked for a login and password.
If I try printing a test page from the web interface, I get the error "Printer not connected; will retry in 30 seconds". The error log on the server says: "D [01/Mar/2007:19:34:07 +0000] cupsdAuthorize: No authentication data provided."
I have a queue of daughters waiting to print homework, help!
These are the packages I've been upgraded to: dpkg -l | grep cupsys ii cupsys 1.2.7-4 Common UNIX Printing System(tm) - server ii cupsys-bsd 1.2.7-4 Common UNIX Printing System(tm) - BSD comman ii cupsys-client 1.2.7-4 Common UNIX Printing System(tm) - client pro ii cupsys-common 1.2.7-4 Common UNIX Printing System(tm) - common fil ii cupsys-driver-gimpprint 5.0.0-3 printer drivers for CUPS ii cupsys-driver-gutenprint 5.0.0-3 printer drivers for CUPS ii libcupsys2 1.2.7-4 Common UNIX Printing System(tm) - libs ii libcupsys2-gnutls10 1.2.7-4 Common UNIX Printing System(tm) - dummy libs
Thanks,
Jenny
On 01/03/07, Jenny Hopkins hopkins.jenny@gmail.com wrote:
If I try printing a test page from the web interface, I get the error "Printer not connected; will retry in 30 seconds". The error log on the server says: "D [01/Mar/2007:19:34:07 +0000] cupsdAuthorize: No authentication data provided."
Further on this: the problem seems to be two-fold. I used openssl to create an ssl certificate in /etc/cups/ssl, and this cured the problem of not being able to log in and use the https pages for web administration. The error "printer not connected" is still happening, though, and nothing will print.
I've got the printer on the usb port.
Thanks, Jenny
Ewww
The reason I'd imagine that you cannot get to the https file is that the package upgrade has not generated the certificates.
A quick workaround should be to go into /etc/cups/client.conf and comment out the lines
Encryption Always Encryption Required and Encryption Never
Then restart cups This should put it back to what was/is the default of Encryption if the client requests it.
After you have restarted cups you should be able to access the http web interface again and your printers should start working again without authentication
On 01/03/07, Wayne Stallwood ALUGlist@digimatic.co.uk wrote:
Ewww
Quite. Bang has gone my evening with my nose in a book. Thanks, Dave and Wayne. The ssl problem is sorted as per my second mail. I also tried removing cupsys, moving cups to cups.old and reinstalling, then copying back in my confs, but the same error is occurring re. the printer not being connected. (Yes, Brett, I did check the cable :-))
Could it be that the upgrade has interfered with the usb modules in some way?
Thanks, Jenny (sorry, Wayne, replied to just you first time)
On Thu, Mar 01, 2007 at 09:02:01PM +0000, Jenny Hopkins wrote:
On 01/03/07, Wayne Stallwood ALUGlist@digimatic.co.uk wrote:
Ewww
Quite. Bang has gone my evening with my nose in a book. Thanks, Dave and Wayne. The ssl problem is sorted as per my second mail. I also tried removing cupsys, moving cups to cups.old and reinstalling, then copying back in my confs, but the same error is occurring re. the printer not being connected. (Yes, Brett, I did check the cable :-))
Oi! What makes you think that I'd ask that?! ;)
(on a different note, have you tried unplugging and replugging the printer - might be that something has changed in hotplug/udev - might also be worth checking the permissions on the printer device to make sure it's in the right group, if it isn't then it's probably a udev bug).
Blah.
On 01/03/07, Brett Parker iDunno@sommitrealweird.co.uk wrote:
Oi! What makes you think that I'd ask that?! ;)
ha!
(on a different note, have you tried unplugging and replugging the printer - might be that something has changed in hotplug/udev - might also be worth checking the permissions on the printer device to make sure it's in the right group, if it isn't then it's probably a udev bug).
Yes, I had tried that. Things have now gone from bad to worse, as I rebooted the server on the offchance that it might reset a bunch of stuff, and now the ethernet no longer works either. Routing and netstat all look ok, pings itself (on the eth0 interface), but can't seem to get external connection of any kind.
Bah.
Jenny
Hi Jenny
On Thursday 01 March 2007 22:07, Jenny Hopkins wrote:
Things have now gone from bad to worse, as I rebooted the server on the offchance that it might reset a bunch of stuff, and now the ethernet no longer works either. Routing and netstat all look ok, pings itself (on the eth0 interface), but can't seem to get external connection of any kind.
Try `ifdown eth0 && ifup eth0`
You said earlier:
I've just upgraded my debian amd64 server to etch.
Was that a dist-upgrade from Sarge to Etch ??
/me is thinking something else might have got broken in the process...
Regards, Paul.
On 01/03/07, Paul lists@bulldoghome.com wrote:
You said earlier:
I've just upgraded my debian amd64 server to etch.
Was that a dist-upgrade from Sarge to Etch ??
Indeed it was. The kernel was upgraded in the process from 2.6.16-em64t-p4 to 2.6.18-3-amd64. Rebooting back into the old kernel has given me back network, but the printer still not recognised as a device on usb0. (I got your mail too late to try ifdown)
/me is thinking something else might have got broken in the process...
Acht. Now I remember why I seldom upgrade things.
Thanks, jenny
Hi Jenny
On Thursday 01 March 2007 22:24, Jenny Hopkins wrote:
The kernel was upgraded in the process from 2.6.16-em64t-p4 to 2.6.18-3-amd64.
Hrmmm... On *this box, the kernel is 2.6.18-4-amd64
/me is thinking something else might have got broken in the process...
Acht. Now I remember why I seldom upgrade things.
Might be worth resyncing the apt sources and checking to see what else is tagged for an upgrade.. One gotcha might be hotplug needs purging when udev gets installed.. Keep an eye on anything that doesn't get updated and comment out the sarge repository.
Isn't life fun (after spending the last week testing a well hacked kernel).. ;)
Regards, Paul.
On 01/03/07, Paul lists@bulldoghome.com wrote:
Hi Jenny
On Thursday 01 March 2007 22:24, Jenny Hopkins wrote:
The kernel was upgraded in the process from 2.6.16-em64t-p4 to 2.6.18-3-amd64.
Hrmmm... On *this box, the kernel is 2.6.18-4-amd64
/me is thinking something else might have got broken in the process...
Acht. Now I remember why I seldom upgrade things.
Might be worth resyncing the apt sources and checking to see what else is tagged for an upgrade.. One gotcha might be hotplug needs purging when udev gets installed.. Keep an eye on anything that doesn't get updated and comment out the sarge repository.
I'll try this, Paul. Thankyou.
Is there a command line I can send to the printer from the server cli using cupsys-bsd rather than lpr? I'm a bit hazy in this area.
Isn't life fun (after spending the last week testing a well hacked kernel).. ;)
If it weren't for the homework, I'd be having a ball ;-)
Thanks, Jen
Regards, Paul.
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Thu, 2007-03-01 at 22:24 +0000, Jenny Hopkins wrote:
Indeed it was. The kernel was upgraded in the process from 2.6.16-em64t-p4 to 2.6.18-3-amd64. Rebooting back into the old kernel has given me back network, but the printer still not recognised as a device on usb0. (I got your mail too late to try ifdown)
Have a look at the output of lsusb and just check it can see something that at least looks like it is your printer.
Then tail messages and just see if sensible things happen when you unplug and replug the printer. You should at the very least get something like a message from the usb subsystem saying that a new device is trying to register followed by usb lp0 popping up saying it has found a device (which will have matching vendor and product id's to what you saw in lsusb.
On 01/03/07, Wayne Stallwood ALUGlist@digimatic.co.uk wrote:
Then tail messages and just see if sensible things happen when you unplug and replug the printer. You should at the very least get something like a message from the usb subsystem saying that a new device is trying to register followed by usb lp0 popping up saying it has found a device (which will have matching vendor and product id's to what you saw in lsusb.
Thanks Wayne,
Help much appreciated.
This all looks just fine, but another attempt at a test print page still shows "device not connected". Output below.
Jenny
Mar 1 22:44:27 nutmeg kernel: usb 2-1: USB disconnect, address 3 Mar 1 22:44:27 nutmeg kernel: drivers/usb/class/usblp.c: usblp0: removed Mar 1 22:44:29 nutmeg kernel: usb 2-1: new full speed USB device using uhci_hcd and address 4 Mar 1 22:44:29 nutmeg kernel: usb 2-1: configuration #1 chosen from 1 choice Mar 1 22:44:29 nutmeg kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4911 Mar 1 22:44:29 nutmeg kernel: scsi3 : SCSI emulation for USB Mass Storage devices Mar 1 22:44:32 nutmeg kernel: usb 2-1: USB disconnect, address 4 Mar 1 22:44:32 nutmeg kernel: drivers/usb/class/usblp.c: usblp0: removed Mar 1 22:44:52 nutmeg kernel: usb 2-1: new full speed USB device using uhci_hcd and address 5 Mar 1 22:44:52 nutmeg kernel: usb 2-1: configuration #1 chosen from 1 choice Mar 1 22:44:52 nutmeg kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x4911 Mar 1 22:44:52 nutmeg kernel: scsi4 : SCSI emulation for USB Mass Storage devices Mar 1 22:44:57 nutmeg kernel: Vendor: HP Model: PSC 2355 Rev: 1.00 Mar 1 22:44:57 nutmeg kernel: Type: Direct-Access ANSI SCSI revision: 02 Mar 1 22:44:57 nutmeg kernel: sd 4:0:0:0: Attached scsi removable disk sdc
nutmeg:/var/log# lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 005: ID 03f0:4911 Hewlett-Packard Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000
Mar 1 22:44:57 nutmeg kernel: Vendor: HP Model: PSC 2355 Rev: 1.00 Mar 1 22:44:57 nutmeg kernel: Type: Direct-Access ANSI SCSI revision: 02 Mar 1 22:44:57 nutmeg kernel: sd 4:0:0:0: Attached scsi removable disk sdc
nutmeg:/var/log# lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 005: ID 03f0:4911 Hewlett-Packard Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000
Hi Jenny,
Is hplip installed and running correctly? This is the HP driver package for printers and scanners?
You should have something like this
ganymede ~ # ps ax |grep hp 2260 ? S 0:00 [khpsbpkt] 7838 ? S 0:00 /usr/bin/python /usr/share/hplip/hpssd.py 11359 pts/0 S+ 0:00 grep hp ganymede ~ #
If not, it's available from here http://hplip.sourceforge.net/
I've goto an HP C6180 all in one thing and it was really easy to set up. In fact it took me 15mins to get it working in Linux (scanner as well) and almost an hour in XP :-)
HTH
Chris
On Fri, 2007-03-02 at 00:43 +0000, Chris Glover wrote:
I've goto an HP C6180 all in one thing and it was really easy to set up. In fact it took me 15mins to get it working in Linux (scanner as well) and almost an hour in XP :-)
Was that hour spent waiting for the HP driver installation to finish installing 400MB of crudware onto your machine ?
I want the printer driver, not 3 programs that duplicate functionality (badly) that is already built into the operating system and some vague attempt at software that makes greeting cards.
If ever there was an argument for it being desirable for manufacturers _not_ to support linux this would be it. If this is the sort of rubbish they get us to install on Windows I'd rather let the OSS crowd figure it out. :-)
On Fri, 2007-03-02 at 01:27 +0000, Wayne Stallwood wrote:
On Fri, 2007-03-02 at 00:43 +0000, Chris Glover wrote:
I've goto an HP C6180 all in one thing and it was really easy to set up. In fact it took me 15mins to get it working in Linux (scanner as well) and almost an hour in XP :-)
Was that hour spent waiting for the HP driver installation to finish installing 400MB of crudware onto your machine ?
Yes and no.... It was partly that it complained the old photosmart drivers for my previous printer were still installed and they had a fight. :-)
Chris
On 02/03/07, Chris Glover chris@glovercc.plus.com wrote:
Hi Jenny,
Is hplip installed and running correctly? This is the HP driver package for printers and scanners?
Hi Chris, I thought this was the answer: apt-get did install hplip (it was installed before the upgrade|), but still same error. nutmeg:/dev# ps ax | grep hp 3030 ? S 0:00 [shpchpd_event] 10848 ? Ss 0:00 /usr/sbin/hpiod 10851 ? S 0:00 python /usr/sbin/hpssd 10971 ? S 0:00 gs -sstdout=%stderr -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs -sDeviceManufacturer=HEWLETT-PACKARD -sDeviceModel=deskjet 5600 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dDuplex=false -r300 -sIjsParams=Quality:Quality=0,Quality:ColorMode=2,Quality:MediaType=0,Quality:PenSet=2,PS:MediaPosition=7 -dIjsUseOutputFD -sOutputFile=%stdout - 10974 ? S 0:00 hpijs 11113 pts/0 S+ 0:00 grep hp
I've swapped the usb cable to another port on server to no avail.
Thanks, Jenny
On Fri, 2007-03-02 at 07:59 +0000, Jenny Hopkins wrote:
On 02/03/07, Chris Glover chris@glovercc.plus.com wrote:
Hi Jenny,
Is hplip installed and running correctly? This is the HP driver package for printers and scanners?
Hi Chris, I thought this was the answer: apt-get did install hplip (it was installed before the upgrade|), but still same error. nutmeg:/dev# ps ax | grep hp 3030 ? S 0:00 [shpchpd_event] 10848 ? Ss 0:00 /usr/sbin/hpiod 10851 ? S 0:00 python /usr/sbin/hpssd 10971 ? S 0:00 gs -sstdout=%stderr -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs -sDeviceManufacturer=HEWLETT-PACKARD -sDeviceModel=deskjet 5600 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dDuplex=false -r300 -sIjsParams=Quality:Quality=0,Quality:ColorMode=2,Quality:MediaType=0,Quality:PenSet=2,PS:MediaPosition=7 -dIjsUseOutputFD -sOutputFile=%stdout - 10974 ? S 0:00 hpijs 11113 pts/0 S+ 0:00 grep hp
I've swapped the usb cable to another port on server to no avail.
Hi Jenny,
Just realised my hplip got broken on one of my machines! DOH! At least it was an easy fix.
hpiod should also be running.
What does running hp-toolbox give you? This has a wizard for adding printers, see if that can find your device.
HTH
Chris
On 02/03/07, Chris Glover chris@glovercc.plus.com wrote:
Just realised my hplip got broken on one of my machines! DOH! At least it was an easy fix.
Fixed before you realised it was broken!
hpiod should also be running.
Yes, it is.
What does running hp-toolbox give you? This has a wizard for adding printers, see if that can find your device.
I'm not running an x-server, alas. There was some rune or other to export the display to another computer running X, but I'll be damned if I can remember it.
It's as if everything is working just as it ought to, except the usb is bust. There is a module running I've never noticed before: usblp, but it might have been there before when cups was working.
Thanks,
Jenny
On Fri, 2007-03-02 at 12:41 +0000, Jenny Hopkins wrote:
On 02/03/07, Chris Glover chris@glovercc.plus.com wrote:
Just realised my hplip got broken on one of my machines! DOH! At least it was an easy fix.
Fixed before you realised it was broken!
Yep, fortunately I hadn't tried printing from this machine since I upgraded the snmp bit!
hpiod should also be running.
Yes, it is.
What does running hp-toolbox give you? This has a wizard for adding printers, see if that can find your device.
I'm not running an x-server, alas. There was some rune or other to export the display to another computer running X, but I'll be damned if I can remember it.
ssh into the box you're trying to talk to using ssh -X hostname
and then run hp-toolbox, and it should magically appear on your display (assuming you've got ssh set up correctly!)
Good luck
Chris
On Fri, Mar 02, 2007 at 12:50:46PM +0000, Chris Glover wrote:
I'm not running an x-server, alas. There was some rune or other to export the display to another computer running X, but I'll be damned if I can remember it.
ssh into the box you're trying to talk to using ssh -X hostname
and then run hp-toolbox, and it should magically appear on your display (assuming you've got ssh set up correctly!)
Magic isn't it.
The other thing you *sometimes* need is "ssh -Y hostname" this does clever things with the X security stuff. I need it when I connect from my home machine into the work Solaris systems if I want to run X applications on my home screen.
On 02/03/07, Eur Ing Chris Green cl@isbd.net wrote:
ssh into the box you're trying to talk to using ssh -X hostname
and then run hp-toolbox, and it should magically appear on your display (assuming you've got ssh set up correctly!)
Magic isn't it.
If you can get it to work :-) I'm running into as many problems with this as I am with the original post! I won't deviate from my original post by going off on an X-server tangent, though. I'll return when I get there and get a response from hp-toolbox.
Thanks, Jenny
-
Brett Parker -
Chris Glover -
Eur Ing Chris Green -
Jenny Hopkins -
Paul -
Wayne Stallwood