cups-pdf - stops with status 249!

Helge Blischke h.blischke at srz.de
Thu Apr 7 04:26:34 PDT 2005


Anonymous wrote:
> 
> Hi all,
> 
> There doesnt appear to be a forum for cups-pdf printing. I have installed cups-pdf with the defaults as per installation instructions on http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/ Basiucally I chose postscript as the vendor and colour for the driver. Colour was the only option available.
> 
> When I print a test page from the cups-admin web app all goes well. Whenever I try and print from a client machine the printer crashes and the following appears in my cups error-log.
> 
> ==================
> 
> I [06/Apr/2005:19:09:58 +0200] Job 301 queued on 'PDF' by 'abd'.
> I [06/Apr/2005:19:09:58 +0200] Started filter /usr/lib/cups/filter/pstops (PID 17714) for job 301.
> I [06/Apr/2005:19:09:58 +0200] Started backend /usr/lib/cups/backend/cups-pdf (PID 17715) for job 301.
> E [06/Apr/2005:19:09:58 +0200] PID 17715 stopped with status 249!
> I [06/Apr/2005:19:09:58 +0200] Hint: Try setting the LogLevel to "debug" to find out more.
> I [06/Apr/2005:19:09:58 +0200] Saving printers.conf...
> E [06/Apr/2005:19:10:28 +0200] Bad request line "g" from 192.168.10.225!
> E [06/Apr/2005:19:10:28 +0200] Bad request line "g" from 192.168.10.225!
> E [06/Apr/2005:19:10:30 +0200] Bad request line "g" from 192.168.10.225!
> =================
> 
> Enabling the log level to debug results in tons of output in which I cannot find any clues. Maybe because I dont know what I am looking for. What is status 249?

Well, in fact it is status -7 (0xfffffff9), but CUPS logs only the
contents of the 
rightmost byte (as the rest is reserved for a signal number, IIRC), and
0xf9 is 249.

Looking into the source of the pdf backend you use, this return code
means
"failed to set file mode for PDF file",
thus I suspect it is an issue of directory permissions.

Perhaps you should ask the author of this backend to prepend messages
written to 
the CPERROR file descriptor by "ERROR:" so that these messages appear in
the error log.
(of course, if you compiled the backend from source, you could do this
hack easily by
yourself).

Helge


-- 
Helge Blischke
Softwareentwicklung
SRZ Berlin | Firmengruppe besscom
http://www.srz.de




More information about the cups mailing list