Am I right deducing, that I should attempt recompiling perl with
-DEMERGENCY_SBRK?
Try to, but this doesn't solve the original problem. You still have to
try to narrow down the code that causes the problem. Using ab or a
similar load tester might help to stress test.
Using tools
Recently I happened to get the error log flooded with the message
callback called exit
(repeated a couple of million times, probably by one process or a few
processes).
This was some side-effect of the lack of memory (earlier in the logs I
found messages about allocation failures), which
Marcin Kasperski wrote:
Recently I happened to get the error log flooded with the message
callback called exit
(repeated a couple of million times, probably by one process or a few
processes).
This was some side-effect of the lack of memory (earlier in the logs I
found messages about
Stas Bekman [EMAIL PROTECTED] writes:
Marcin Kasperski wrote:
Recently I happened to get the error log flooded with the message
callback called exit
(repeated a couple of million times, probably by one process or a few
processes).
This was some side-effect of the lack of
Marcin Kasperski wrote:
Stas Bekman [EMAIL PROTECTED] writes:
Marcin Kasperski wrote:
Recently I happened to get the error log flooded with the message
callback called exit
(repeated a couple of million times, probably by one process or a few
processes).
This was some side-effect of
