Hi Paolo, On Wed, 18 Oct 2006, Paolo Lucente wrote:
> If you see, such processes are not taking CPU, they are just laying out > there. This is because they are all on their LOCK, waiting for the green > light. LOCK serializes things: selects one of those processes, allows it > to do its job and terminate, then selects another one, etc. I think you're right that they weren't taking CPU, but they do take memory. And creating increasing numbers of them is unlikely to help the box come back to life after such an incident. > You should avoid such a queue to come up. It might be related to the low > specs box. But it might also be that you are not aggregating things that > much (are you?). Take a look to the discussion happened on the list just > earlier this month about database, performances, etc. Then, using MySQL, > you can also take a look to the following configuration directives in > CONFIG-KEYS: sql_dont_try_update and sql_multi_values. They usually > help. It seems to be partly related to this. The problem is that I do actually want to log a lot of data, and I want to see how much I can get away with on this old box. Preferably without killing it, because it's also our firewall and LDAP server. And it seems to be doing fine under normal conditions. But when the box does get overloaded, pmacct doesn't degrade gracefully. The original source of the problem is actually horde, which I'm trying to set up for use with pmacct-fe. While I'm configuring it, it keeps getting into a state where it just does infinite loops. Before I reined in the Apache configuration, it also tried to create 150 apache processes which is what brought the box to its knees. It's a shame that I probably won't be able to even try pmacct-fe if I can't get Horde working, because it looks good and I really want to try it. Cheers, Chris. -- (aidworld) chris wilson | chief engineer (http://www.aidworld.org) _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
