|Request Entity Too Large|
The request is too large for this server to process.HTTP/1.1 413 Request Entity Too Large Date: Fri, 29 Jun 2007 19:09:52 GMT Server: CUPS/1.1 Content-Language: en_US Upgrade: TLS/1.0,HTTP/1.1 Connection: close Content-Type: text/html Content-Length: 168
Request Entity Too Large
The request is too large for this server to process.
| [on the printed test page]|
**** Unable to open the initial device, quitting.
I [29/Jun/2007:18:59:26 +0000] Job 7 queued on 'OfficeJetG85' by 'root'.
I [29/Jun/2007:18:59:26 +0000] Started filter /usr/lib/cups/filter/pstops (PID 1588) for job 7.
I [29/Jun/2007:18:59:26 +0000] Started filter /usr/lib/cups/filter/foomatic-rip (PID 1589) for job 7.
I [29/Jun/2007:18:59:26 +0000] Started backend /usr/lib/cups/backend/hp (PID 1590) for job 7.
E [29/Jun/2007:18:59:27 +0000] PID 1589 stopped with status 3!
I [29/Jun/2007:18:59:27 +0000] Hint: Try setting the LogLevel to "debug" to find out more.
|Try setting the LogLevel to "debug"|
|If I understand corectly, you're suggesting to change the permissions on /var/spool/cups to dsl/staff, is that correct?|
|I'd love to set the log level to debug, but how?|
|Switch on the "debug" mode in the LogLevel directive for your CUPS daemon. Edit /etc/cups/cupsd.conf (or wherever this configuration file is installed in your case) to have the line "LogLevel debug" there. Then restart your CUPS daemon /etc/software/init.d/cups start (the command may be customized by your Linux distribution; f.e. SuSE will take "rccups start").|
Now print a job. Watch what is written to your CUPS error log. It normally sits in /var/log/cups/error_log. In debug level, nearly every action of the CUPS daemon is logged. You can see which filters and backends are called in which order. Very often you'll get a hint about what is missing for the print job to succeed.
D [30/Jun/2007:18:00:05 +0000] [Job 3] GNU Ghostscript 7.05: Could not open the scratch file /var/spool/cups/tmp/gs_AStYqN