It may help in this case, after some further testing, I can reproducible and presumably say, that choosing a setting different of "MaxLogSize 0" in cupsd.conf results in approx. weekly crashing of CUPS showing the "Closing on unknown HTTP state 0" error.
So "MaxLogSize 0" deactivates CUPS' internal logrotating and causes CUPS to run stable. This is at a current stable Debian Wheezy x86_64 version including the standard package of CUPS, but could apply to Ubuntu as well. It's a somewhat annoying bug, logging needed to solve an error causes the error... Regards -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
