Description of problem:
cupsd is randomly segfaulting on a number of machines
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Here is whats in dmesg from three machines all FC5/x86-64:
cupsd general protection rip:2ad4ce361600 rsp:7fffdd3b29d8 error:0
cupsd: segfault at 0000000000000021 rip 00002ae20f80b6ac rsp
00007fff9bb26350 error 6
cupsd: segfault at 0000000000000001 rip 00002b0c31d27040 rsp
00007fff799e4108 error 4
cupsd: segfault at 0000000000000001 rip 00002ada30b7d5e0 rsp
00007fff7ab931b8 error 4
Please try this test update:
Does that fix the problem?
How frequently does this happen?
Any news on whether the test update fixes the problem?
I'd tentatively say yes. It's been a few weeks and no problems.
Just had cups die on another machine around here. The machine printed someting
then wouldn't print no more...
FC5, cups-1.2.2-1.1, which seems to be the same version as the update I'm running.
Any clues about what happened? Any dmesg messages look relevant?
Please attach the /var/log/cups/error_log from that machine (or at least the
last few lines of it..).
cupsd: segfault at 0000000000000000 rip 00002afffff9b040 rsp
00007fffab8ed1c8 error 4
I've attached all the entries for today from the cups error_log
(I'm seeing a lot of references to a printer which is long gone. Possibly some
other machine is trying to print to that. But I don't think thats causing cups
This looks like the few line before and after death.
I [17/Aug/2006:15:35:24 +0100] Job 1353 queued on "sage-raw" by "lorraine".
I [17/Aug/2006:15:35:24 +0100] Started backend /usr/lib/cups/backend/usb (PID
4311) for job 1353.
W [17/Aug/2006:15:46:17 +0100] "AuthClass System" is deprecated; consider using
"Require @SYSTEM" on line 840.
I [17/Aug/2006:15:46:17 +0100] Sending browsing info to 126.96.36.199:631 (IPv4)
I [17/Aug/2006:15:46:17 +0100] Sending browsing info to 188.8.131.52:631 (IPv4)
sage-raw is just a raw print queue for a windows machine.
Created attachment 134399 [details]
Snippet of cups error_log
Please change /etc/cups/cupsd.conf so that the 'LogLevel' line reads:
That way when it happens again we'll have lots more information about what went
Oh, I forgot to mention -- if this is on an always-on server you'll need to
restart cups as well (/sbin/service cups restart).
Thanks. Let me know if/when it happens again.. (I'll leave this in NEEDINFO
Closing. Please re-open if this happens again.