[cups.general] Ongoing 'Cannot allocate memory' and 'Bad request line' error messages from 1.3.9 server

[Michael R Sweet]

John A. Murdie wrote:
> We're continuing to see:
> 
> E [dd/mmm/yyyy:hh:mm:ss +0000] Unable to fork /usr/lib/cups/cgi-bin/printers.cgi - Cannot allocate memory.
> 
> messages in our 1.3.9 cupsd error_log file. When this happens, service becomes very glitchy (lots of '404 Not Found' messages from the web interface) and the server has to be restarted - about once a week. A memory leak, I presume.

What do you have MaxJobs set to?

If you run "top", what is the resident memory size of cupsd?

How about running cupsd in valgrind - any memory leaks there?

> We also see lots of:
> 
> E [dd/mmm/yyyy:hh:mm:ss +0000] Bad request line "^W^C^A" from A.B.C.D!
> 
> messages. It doesn't seem to break anything, but I'd like to know what causes these. Our Linux clients have CUPS 1.3.9 also.

I think that is an issue with Expect handling that may be fixed in the
upcoming 1.3.10 release.

-- 
______________________________________________________________________
Michael R Sweet                        Senior Printing System Engineer