We have 3 Debian Wheezy VM's all on different ESXi hypervisors in
different offices, two running CUPS 1.5.3, one running CUPS 1.6.2.
CUPS daemon on all 3 VMs crash at seemingly random intervals with the
only error_log message consistently appearing before the crash being
'Closing on unknown HTTP state 0'.
These print servers handle thousands of print jobs a day with many
different printers each and each crashes approximately 4 times / week.
I have put a very, very ugly workaround in place - cronned the following
bash script to run every minute:
/etc/init.d/cups status
if [ $? == 1 ]; then
/etc/init.d/cups restart
date >> /var/log/restart-cups
fi
Clients printing to it are all Mac OS X computers ranging from 10.6.8 - 10.8.5.
I have not noticed it specifically crash when accessing the web
interface, but do have Icinga checks checking the output from
http://server:631 every few minutes.
Is there any other information I could supply from my problematic
servers that might help the troubleshooting process?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/512220
Title:
cupsd crash "Closing on unknown HTTP state 0"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/512220/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
