cupsd is running amok

Hi,
I have various computers where cupsd is running at a cpu usage of 60 to 99%. They are part of a network with two cups servers that are actually connected to printers. All the other clients connect to them via the broadcast function.

Now, various clients have a cups server that is using so much cpu power. There is nothing unusual in the logs, I have configured all clients the same and some are working normally. Printing is no longer possible as the programmes wanting to print just freeze.

Where can I start looking for a solution?

It is a Debian Etch system.

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: cupsd is running amok

Quote:
Where can I start looking for a solution?

The key files you'll want to edit are under /etc/cups. In particular, you'll want to go over the cupsd.conf with a fine toothed comb.

Is your cupsd.conf heavily modified? The Debian defaults are usually pretty sane. You might want to remove and reinstall cups and then add in changes incrementally, checking for odd behavior after each change.

Re: cupsd is running amok

The strange thing is, I haven't altered any config files.

CPU usage...

That's bizarre. I've never run into that problem. I wind up only tweaking the config file's access parameters and it works like a charm.

It's probably worth doing a top-down reconfiguration. These two tutorials (#1, #2) may prove useful.

Also, this article has some advice on restricting CPU usage...

cups runs amok

It is indeed a very weird behaviour. There is no hint of what is happening. It seems that openoffice.org is one of the casualties of that behaviour. I have a lot of openoffice.org freezes on the network. I am still trying to find out whether this is always on computers with cups using all system resources but I have found some computers where this is the case.
Might this have to do with my setup?
I have one cups server that sends browsing information about the printers into the network and the other printers just use that information. As far as I know this is the standard procedure for cups although the howto you mentioned gives a different setup. Working on my network has become quite an ordeal for my users.
I have found out that this starts when I try to print. Even after a restart of cupsd, the situation stays the same. Only when I delete the files in /var/spool/cups/, the cpu usage goes down to 0% again. There is no unusual message in the logfiles. The printing job does not reach my main server.

Syndicate content