We've also randomly seen this "unable to alloc <number between 1-2M> bytes" error message when starting 3.4. In our case, it's not a VM resource problem - it's some other kind of weirdness. It displays this message, exits, init respawns it, then it starts okay. Probably not at all related to your situation, since you're getting 100 processes...
> We are running aolserver 4GM on debian and are having trouble keeping it > alive. The problem seems to be that somehow, aolserver continually respawns > until there are ~100 or more processes running (identified by a ps). At that > point, aolserver either just hangs, with nothing notable in the log file, or > sometimes it will stop with an error message like: > > unable to alloc 2849420 bytes > > This respawning happens whether we run it from the inittab or not. > > It is running on a dedicated machine that runs only 1 instance of aolserver. > The box has dual processors and 1G RAM. > > As the number of processes grows, the amount of available memory decreases. > > Any help on this would be greatly appreciated. > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with > the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field > of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
