-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Files in spool directory cause cupsd-startup to fail: "Child exited on signal 11" #82
Comments
CUPS.org User: pipitas More info: You'll notice that I am using a few additional backends What I changed on this system today:
|
CUPS.org User: mike The testipp program in the cups subdirectory can be used to list the attributes in the job control file. The control file for job 2226 has a job-state attribute of type nameWithoutLanguage (it should be an enum...) This is likely the cause of the problem... I'll update the code to check for this and log this error if found, however we need to determine how this happened... |
CUPS.org User: mike The attached patch should correct this problem and has been commited to CVS for rc5. |
"cupsd.conf": ServerName 10.160.51.60 |
"cupsd-str82.patch": Index: ipp.cRCS file: /development/cvs/cups/scheduler/ipp.c,v
-static void
@@ -5984,6 +5986,12 @@ /*
@@ -6076,25 +6084,125 @@
- */
Index: job.cRCS file: /development/cvs/cups/scheduler/job.c,v
|
Version: 1.1.19rc4
CUPS.org User: pipitas
I can reproduce this at will....
Certain printfiles on hold in the spool directory cause
cupsd to fail starting. If I move the files away the startup
completes. If I move only one of the files back, it fails.
kde-bitshop:/usr/lib/cups/backend # /etc/init.d/cups start
cupsd: Child exited on signal 11!
cups: unable to start scheduler.
This is how far the scheduler logs its startup phase (LogLevel debug2
can be created on demand):
I [10/May/2003:19:05:31 +0200] Sending browsing info to ffffffff:631
D [10/May/2003:19:05:31 +0200] AddLocation: added location 'CUPS_INTERNAL_BROWSE_ACL'
D [10/May/2003:19:05:31 +0200] DenyIP: CUPS_INTERNAL_BROWSE_ACL deny ffffffff/00000000
D [10/May/2003:19:05:31 +0200] AllowIP: CUPS_INTERNAL_BROWSE_ACL allow 00000000/00000000
I [10/May/2003:19:05:31 +0200] Loaded configuration file "/etc/cups/cupsd.conf"
I [10/May/2003:19:05:31 +0200] Configured for up to 100 clients.
I [10/May/2003:19:05:31 +0200] Allowing up to 100 client connections per host.
I [10/May/2003:19:05:31 +0200] Full reload is required.
[.........]
D [10/May/2003:19:05:59 +0200] SetJobHoldUntil: hold_until = 0
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 1498...
D [10/May/2003:19:05:59 +0200] SetJobHoldUntil(1498, "indefinite")
D [10/May/2003:19:05:59 +0200] SetJobHoldUntil: hold_until = 0
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 1499...
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 1500...
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 2152...
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 2156...
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 2157...
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 2163...
D [10/May/2003:19:05:59 +0200] LoadAllJobs: Loading attributes for job 2226...
kde-bitshop:/usr/lib/cups/backend # ls -tlar /var/spool/cups/2226
-rw------- 1 lp sys 583 May 10 15:32 /var/spool/cups/c02226
I moved all job (simple ASCII) and control files from the spool directory.
one after the other and re-started again. The signal 11 always occured after
loading job attributes for job 2163. Only when everything above 2226 was
away, did the scheduler start up completely.
So -- what's up with these files' job attributes to cause such a nasty
error? The files are simple ASCII, and the c-files are revealing nothing
special if looked at with the strings utiliy.... (Attached to STR)
Cheers,
Kurt [ BTW, is there a utility to look at the content of the c-files?
Appart from KDEPrint's "IPP report" feature, I mean? ]
The text was updated successfully, but these errors were encountered: