i'm having similar errors (I do have limits and scheduler set, using
rlimits (as, rss, nproc) and scheduler) whenever i do stress testing,
(overloading mta or web server for example).
during a stress test, some applications die because of no memory
available or can't fork, some stop with segmentation fault (not able
to do vserver <vs> enter),. when attacking httpd might have httpd
the only thing helps is apps configuration overview, i.e. for httpd
I've changed maxServers to a smaller number for others something esle.
I didn't think about it as something bad, always tought it's because
of limits, am I wrong?
what I don't like when such things happen, some apps die and you have
to start them manualy again.
I'm using this patch on fc4, should I try something else?
On 12/11/05, Herbert Poetzl <firstname.lastname@example.org> wrote:
> On Sun, Dec 11, 2005 at 08:19:11PM +0200, Roché Compaan wrote:
> > The following is logged quite often to the syslog in a vserver and I'm
> > worried since I don't see this in any of our regular servers:
> > postfix/sendmail: warning: fork: Cannot allocate memory
> interesting, what does your /proc/virtual/<xid>/limits
> file (with the xid of that guest) show?
> > This is on Debian sarge on a 2.6 kernel with vserver v 2.0. The postfix
> > server in question is not busy at all and the vserver has plenty of
> > memory to spare.
> > Any reason to worry here?
> well, I would try with a recent patch and see if it
> is still an issues ...
> > --
> > Roché Compaan
> > Upfront Systems http://www.upfrontsystems.co.za
> > _______________________________________________
> > Vserver mailing list
> > Vserver@list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
> Vserver mailing list
Vserver mailing list
Received on Sun Dec 11 19:34:33 2005