[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Has anyone upgraded to 14.04 yet? If so, do you still see this issue? -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
I disabled internal logging with MaxLogSize 0 but we have the issue again. Also I can confirm it really depends on what you are printing, since we have 10 identically configured servers and on some of them it's not visibel at all, on others it's happen almost daily. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
** Changed in: cups (Ubuntu) Assignee: Kip Warner (kip) = (unassigned) -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Hi ! I enabled a greater debug level. It seems that cups try to write to a client while the connection is already closed. Here the log before the crash : Returning IPP successful-ok for Get-Job-Attributes (ipp://fichdc:631/printers/AL-C3800_cdi) from 172.16.1.23 cupsdProcessIPPRequest: ippLength(response)=352 cupsdAddSelect(fd=24, read_cb=0x7f8860956d60, write_cb=0x7f8860956720, data=0x7f8861d6c8f0) select_timeout(0): 26 seconds to write dirty config/state files cupsdReadClient(con=0x7f8861d6c8f0(24)) con-http.error=0 con-http.used=0, con-http.state=7 con-data_encoding=HTTP_ENCODE_LENGTH, con-data_remaining=352, con-file=-1 cupsdReadClient: 24 Closing on EOF cupsdCloseClient: 24 cupsdSetBusyState: newbusy=Dirty files, busy=Active clients and dirty files cupsdRemoveSelect(fd=24) cupsdWriteClient(con=0x7f8861d6c8f0(1642895136)) response=(nil)(-1), file=-1 pipe_pid=0 state=0 cupsdWriteClient: 1587435144 Closing on unknown HTTP state 1641466080 First cups open the client for reading on file descriptor 24 : cupsdAddSelect(fd=24 ... select_timeout(0): 26 seconds... Then Cups read from client (why ?) on fd=24 : cupsdReadClient(con=0x7f8861d6c8f0(24) cupsdReadClient: 24 Closing on EOF Finally cups close the connection : cupsdCloseClient: 24 cupsdSetBusyState: newbusy=Dirty files, busy=Active clients and dirty files cupsdRemoveSelect(fd=24) But just after cups try to write again on the same connection con=0x7f8861d6c8f0 where all the structure is nil ! cupsdWriteClient(con=0x7f8861d6c8f0(1642895136)) response=(nil)(-1), file=-1 pipe_pid=0 state=0 cupsdWriteClient: 1587435144 Closing on unknown HTTP state 1641466080 Everything in less than 1 second. Difficult to understand for me what cups trying to do... Baptiste. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Here the full log concerning the connection con=0x7f8861d6c8f0 that made the crash. Baptiste. ** Attachment added: cups_write_bug.txt https://bugs.launchpad.net/ubuntu/+source/cups/+bug/512220/+attachment/4124153/+files/cups_write_bug.txt -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
I think that I understand more precisely the bug. I will comment the above log where the client make two request : - It request the printer attributes and next - the job attributes The first request works, the second crash. ### The first request ### 1) The client query the printer attributes (... read request data from client ... and next ) cupsdReadClient: 24 2.0 Get-Printer-Attributes 1 cupsdProcessIPPRequest(0x7f8861d6c8f0[24]): operation_id = 000b Get-Printer-Attributes ipp://fichdc:631/printers/AL-C3800_cdi get_printer_attrs(0x7f8861d6c8f0[24], ipp://fichdc:631/printers/AL-C3800_cdi) ... 2) CUPS query the printer attributes and write it in a struct copy_attrs(to=0x7f886185bbe0, from=0x7f8861ee47e0, ra=0x7f8861d4b0d0, group=0, quickcopy=0) copy_attribute(0x7f886185bbe0, 0x7f8861973c60[marker-colors,4,42]) copy_attribute(0x7f886185bbe0, 0x7f8861973cf0[marker-levels,4,21]) ... copy_attribute(0x7f886185bbe0, 0x7f8862000780[operations-supported,4,23]) Returning IPP successful-ok for Get-Printer-Attributes (ipp://fichdc:631/printers/AL-C3800_cdi) from 172.16.1.23 3) Cups write the attributes to the client cupsdProcessIPPRequest: ippLength(response)=2153 cupsdAddSelect(fd=24, read_cb=0x7f8860956d60, write_cb=0x7f8860956720, data=0x7f8861d6c8f0) select_timeout(0): 26 seconds to write dirty config/state files cupsdWriteClient(con=0x7f8861d6c8f0(24)) response=0x7f886185bbe0(0), file=-1 pipe_pid=0 state=7 ... cupsdWriteClient(con=0x7f8861d6c8f0(24)) response=0x7f886185bbe0(2), file=-1 pipe_pid=0 state=7 ### The second request ### 1) The client query the job attribute (... read request data from client ... and next ) cupsdReadClient: 24 2.0 Get-Job-Attributes 1 cupsdProcessIPPRequest(0x7f8861d6c8f0[24]): operation_id = 0009 Get-Job-Attributes ipp://fichdc:631/printers/AL-C3800_cdi get_job_attrs(0x7f8861d6c8f0[24], ipp://fichdc:631/printers/AL-C3800_cdi) 2) CUPS query the job attributes and write it in a struct copy_attrs(to=0x7f8861d5a390, from=0x7f8861d49af0, ra=0x7f8861d4b0d0, group=2, quickcopy=0) copy_attribute(0x7f8861d5a390, 0x7f8861d49d70[job-originating-user-name,2,42]) copy_attribute(0x7f8861d5a390, 0x7f8861d5f260[job-media-sheets-completed,2,21]) Returning IPP successful-ok for Get-Job-Attributes (ipp://fichdc:631/printers/AL-C3800_cdi) from 172.16.1.23 3) BUT instead of WRITE the result to the client CUPS do a READ : cupsdProcessIPPRequest: ippLength(response)=352 cupsdAddSelect(fd=24, read_cb=0x7f8860956d60, write_cb=0x7f8860956720, data=0x7f8861d6c8f0) select_timeout(0): 26 seconds to write dirty config/state files cupsdReadClient(con=0x7f8861d6c8f0(24)) con-http.error=0 con-http.used=0, con-http.state=7, con-data_encoding=HTTP_ENCODE_LENGTH, con-data_remaining=352, con-file=-1 cupsdReadClient: 24 Closing on EOF cupsdCloseClient: 24 We see that in the cupsdReadClient call the con-data_remaining=352 correspond to the size of the attributes retourned by the Get-Job- Attributes process. Strange no ? Baptiste. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@Prunkdump: Sorry for the late reply, I was out of the office. 1) We use cups to be able to print from our Linux systems to our Windows print servers. So, most of the printers setup in cups just connect to the windows print server. We also have a few virtual printers installed using custom shell scripts as backends (to print to PDF files in various locations). 2) We do not require authentication for printing on the cups server. Access to the cups admin pages is controlled via Linux group membership and credentials. The only major configuration change we made is the following in cupsd.conf: MaxJobs 2 MaxJobsPerPrinter 15000 We do sometimes have that many jobs coming in at once in nightly processing, so we do need those queue sizes. BTW, the problem hasn't surfaced a single time since we told BIRT / the application using Java printing api to use the testing system. So I guess do expose the bug, we both need lots of print jobs occasionally (which we don't have on the testing system) and an application requesting printer information and status like BIRT. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
** Changed in: cups (Ubuntu) Assignee: (unassigned) = Kip Warner (kip) -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Hi, @Johannes and Daniel Maybe we can search what we have in common ? 1) Are your printers shared upon multiple printer servers ? (windows 2003, debian linux in my case) 2) Do you use a special authentification system ? (samba4 winbind in my case) I attach the log of two recent bugs if it can help. ** Attachment added: cup_bug.tar.gz https://bugs.launchpad.net/ubuntu/+source/cups/+bug/512220/+attachment/4076884/+files/cup_bug.tar.gz -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Hi, just a short update: neither our production server nor the testing environment have exhibited any crashes lately. We still have the java printing api application (the one using BIRT) configured to access the testing system. So that explains why the production system does not crash any more. The testing system hardly gets any print jobs at all. So I guess for the server to crash we need both at least a moderate load of regular print jobs and an application accessing the printer list or details (such as Firefox or BIRT). I haven't had much time in the last couple of weeks to look into this, and I'll be out of the office for most of the next months, so I won't be able to work on this for the next couple of weeks. Regards Johannes -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@Daniel: Things I would be interested in: 1. Do your VMs have multiple virtual CPUs or just one? If multiple, could you reconfigure one of them to only one CPU and check if the problem persists? 2. Could you post the last couple lines (maybe about 100) before a crash from your error log ? 3. How do your clients print to the cups servers? Just using lp or lpr or some cups aware GUI? I guess since they are Macs, it really is a cups aware GUI, which also means they use http requests to figure out the list of printers. Note: On ubuntu, we don't need your workaround to restart cups, because upstart is configured to restart cups automatically when it crashes (which also made it quite hard for me to figure out what was wrong because I didn't notice the crashes till I investigated the log files more thoroughly). -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
1. All three VMs only have 1 virtual CPU each. 2. See attached tarball with 5 separate 1000-line error_log files, each ending with the last log entry before cups daemon quit. These are from 3 separate servers. 3. Printers added via OS X built in CUPS aware GUI (System Preferences - Print Scan - + button - then add a Bonjour Shared printer from the Default tab) -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Sorry forgot attachment for of logs for point 2. ** Attachment added: error_logs https://bugs.launchpad.net/ubuntu/+source/cups/+bug/512220/+attachment/4046082/+files/cups-error-logs-before-crash.tar.bz2 -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@Daniel We would need the valgrind logs to identify the issue. @Johannes I have a quad core bare metal h/w, on which I am unable to reproduce this issue. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Refining the setup needed to reproduce the simple case (reload the web interface) would also be very valuable. Starting with a fresh install, step by step, until you get the crash. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@prunkdump: The last lines in the log file do not look like they are neccessarily caused by the print jobs submitted just before. Are there any cupsdReadClient lines before those lines? Do they look like this: D [07/Mar/2014:07:15:35 +0100] cupsdReadClient: 19 GET /printers/some-printer-name.ppd HTTP/1.1 Then it's definitely not a print job but some other client enumerating the available printers, which seems to be what Firefox is doing and also what the Java printing API is doing. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@Ritesh Bryan: I just noticed our testing instance only has a single CPU, so maybe the problem will not occur at all in the testing environment. If it hasn't surfaced within a week, I will allot another CPU to the VM and keep trying to reproduce the problem. Maybe this is also the reason why you couldn't reproduce the problem with a live CD yet. The other reason might be that the live CD will not be able to recover a saved firefox session as reported in the original bug description. I have not attempted to reproduce the problem with a live CD or with Firefox yet. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@prunkdump: I've also reported the bug also on Canonical's internal (subscription based) support portal before I knew it had been reported on launchpad as well. Ritesh told me earlier to run a special debug version of cupsd under valgrind. The logrotate configuration for cupsd did not work well with valgrind, so I disabled logrotate for cupsd. I than ran cupsd under valgrind for some time, and the crashes were gone. To make sure it wasn't valgrind that caused the bug to disappear, I then ran the debug version of cupsd without valgrind, but forgot to reenable logrotate. cupsd still did not crash. Then I noticed that logrotate was disabled. I reenabled logrotate, and soon after, cupsd showed the regular crashes. I subsequently identified a web application using Java printing API to always be involved in the crashes (i.e. a number of requests from the machine showing in the logs just before the crashes). A couple of days ago, I redirected that web application to a testing cups instance to try to reproduce the problem there. The production instance hasn't crashed since. The testing instance hasn't crashed either, but the crashes usually only occur every couple of days. So they might still come. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@Bryan Ritesh: Note that the ProcCpuinfo.txt attachment from Per Ångström also shows a dual cpu machine. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
This bug has also been reported upstream: http://www.cups.org/str.php?L4108 -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Another reference: http://www.cups.org/str.php?L3432 -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@ritesh: I'm trying to reproduce the problem in our testing environment. The problem with running cups under valgrind is that I have to disable logrotate, and the reload of cups cause by logrotate seems to be an integral part of the problem. Or I have to modify logrotate to cause the reload of cups without terminating valgrind. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@johannes: Why do you thinks about a logrotate problem ? In my case, the last crash happened 2 hours after to log have been rotated. The last job : AL-M7000_prof user1 247 [24/Mar/2014:09:10:07 +0100] 1 1 - 172.16.1.15 TF etude - - AL-M7000_prof user1 248 [24/Mar/2014:09:10:26 +0100] 1 1 - 172.16.1.15 TF etude 1 - - AL-M7000_prof user1 248 [24/Mar/2014:09:10:34 +0100] total 1 - 172.16.1.15 TF etude 1 - - AL-M7000_prof user1 249 [24/Mar/2014:09:10:43 +0100] 1 1 - 172.16.1.15 TF etude 2 - - AL-M7000_prof user1249 [24/Mar/2014:09:11:19 +0100] total 3 - 172.16.1.15 TF etude 2 - - AL-M7000_prof user1250 [24/Mar/2014:09:11:28 +0100] 1 1 - 172.16.1.15 TF etude 3 - - AL-M7000_prof user1250 [24/Mar/2014:09:11:36 +0100] total 1 - 172.16.1.15 TF etude 3 - - AL-M7000_prof user1251 [24/Mar/2014:09:11:45 +0100] 1 1 - 172.16.1.15 verif - - AL-M7000_prof user1251 [24/Mar/2014:09:12:13 +0100] total 3 - 172.16.1.15 verif - - The last log file : I [24/Mar/2014:07:35:01 +0100] Listening to 0.0.0.0:631 (IPv4) I [24/Mar/2014:07:35:01 +0100] Listening to [v1.::]:631 (IPv6) .. D [24/Mar/2014:09:12:21 +0100] cupsdReadClient: 19 WAITING Closing on EOF D [24/Mar/2014:09:12:21 +0100] cupsdCloseClient: 19 D [24/Mar/2014:09:12:21 +0100] cupsdSetBusyState: newbusy=Active clients, busy=Active clients D [24/Mar/2014:09:12:21 +0100] cupsdReadClient: 18 Closing on EOF D [24/Mar/2014:09:12:21 +0100] cupsdCloseClient: 18 D [24/Mar/2014:09:12:21 +0100] cupsdSetBusyState: newbusy=Active clients, busy=Active clients D [24/Mar/2014:09:12:21 +0100] cupsdWriteClient: -282160320 Closing on unknown HTTP state 0 D [24/Mar/2014:09:12:21 +0100] cupsdCloseClient: -343906872 -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Hi @Johannes Thanks, but I am not able to reproduce this locally on precise/trusty. Is it possible for you to start cups under valgrind[1] , and attach the relevant logs . This would help us track the memory corruption issue ( probably a race condition ) . [1] https://wiki.ubuntu.com/Valgrind Thanks -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Hi, Same problem on Debian Wheezy with cups 1.5.3. So it is not a ubuntu specific issue. There is no need to access cups by http to reproduce the problem. For me sending a job can produce the crash. Thanks. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
@prunkdump We need a better way to reproduce it. Can you provide step by step instructions to reproduce it from a clean install (or better yet on a livecd environment). (Ideally using just virtual printers). I'm guessing there is some element we are missing in this bug. Have you changed anything in cups' config? How many printers have you installed? Also, if anyone can reproduce this on Trusty or Debian's Jessy), that would test out the newer version of cups to see if this has already been fixed. -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Yes, the problem still occurs with Ubuntu 12.04.3 LTS, all current updates applied. To reproduce the problem, it is appareantly not required to restart the complete system but sufficient to reload cups using invoke-rc.d --quiet cups force-reload as done by logrotate. ** Changed in: cups (Ubuntu) Status: Expired = Confirmed -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete = Expired -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Is this still seen ? ** Changed in: cups (Ubuntu) Status: New = Incomplete -- 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
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
** Tags added: crash -- cupsd crash Closing on unknown HTTP state 0 https://bugs.launchpad.net/bugs/512220 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
I'm still seeing this bug almost every time I restart my computer. I have updated the bug description with a how-to-reproduce section. ** Description changed: Binary package hint: cups - I often get trouble with Cups crashing and Apport saying the following: + I often get trouble with cupsd crashing and Apport saying the following: The problem cannot be reported: The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes. I think the crash is due to my having a saved Firefox session with Cups' administration window (http://localhost:631/admin) in it. The crash seems to occur when this session is restored as part of the session restore when I log in to my desktop environment. I have turned on debug-logging and can see the following: D [25/Jan/2010:08:57:16 +0100] cupsdReadClient: 11 GET /images/cups-icon.png HTTP/1.1 D [25/Jan/2010:08:57:16 +0100] cupsdSetBusyState: Active clients D [25/Jan/2010:08:57:16 +0100] cupsdAuthorize: No authentication data provided. D [25/Jan/2010:08:57:16 +0100] cupsdReadClient: 11 Closing on EOF D [25/Jan/2010:08:57:16 +0100] cupsdCloseClient: 11 D [25/Jan/2010:08:57:16 +0100] cupsdSetBusyState: Not busy D [25/Jan/2010:08:57:16 +0100] cupsdWriteClient: 1354538648 Closing on unknown HTTP state 0 D [25/Jan/2010:08:57:16 +0100] cupsdCloseClient: 1354538648 - It is not consistently reproducible. It occurs mostly when I'm not - expecting it. + How to reproduce: + 0) Make sure you have session restore activated. Make sure your favorite browser is set to restore the last session on reload. + 1) Load http://localhost:631/admin in your favorite browser. + 2) Restart your computer. + 3) Log in to your desktop environment. + + Expected result: The CUPS administration window should be loaded in your browser. + Actual result: The CUPS administration window fails to load. The browser says: The connection to the server was reset while the page was loading. + + It is not consistently reproducible, but I would say I see a failure + rate of 80 %. It happens on both of my test machines. ProblemType: Bug Architecture: amd64 Date: Mon Jan 25 09:00:30 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LG Electronics P300-T.APE4V NonfreeKernelModules: nvidia Package: cups 1.4.2-6 Papersize: letter ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-11-generic root=UUID=01ebab7a-379c-48c8-87d6-a2800f6dccfd ro quiet splash ProcVersionSignature: Ubuntu 2.6.32-11.15-generic SourcePackage: cups Uname: Linux 2.6.32-11-generic x86_64 dmi.bios.date: 06/30/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: ELGNSF18 dmi.board.name: ELGON dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrELGNSF18:bd06/30/2008:svnLGElectronics:pnP300-T.APE4V:pvrNotApplicable:rvnLGElectronics:rnELGON:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P300-T.APE4V dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics -- cupsd crash Closing on unknown HTTP state 0 https://bugs.launchpad.net/bugs/512220 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
** Summary changed: - cups crash Closing on unknown HTTP state 0 + cupsd crash Closing on unknown HTTP state 0 -- cupsd crash Closing on unknown HTTP state 0 https://bugs.launchpad.net/bugs/512220 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
