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 in turn was caused by
some non-apache process allocating too much. Nevertheless, I am trying
to find what happened to my apache/modperl process
(processess?). After all, aborting some processes due to lack of
memory is ok, but filling the whole disk with error log is not.
It is possible that the problem is not caused by the modperl itself
(for instance some of additional modules we implemented in both C and
perl could go wild). But trying to understand the problem I would like
to ask the following questions:
a) Have anyone anywhere observed similar behaviour?
b) When is the message 'callback called exit' printed - and can it be
disabled?
c) Do you have any idea of what should I pay attention to?
--
( Marcin Kasperski | Królik to brzmi dumnie! Wszystko dla szympansa! )
( http://www.mk.w.pl | Chomikiem jestem, wszystko mi wolno! (Mrożek) )
(----------------------------------------------------------------------------)
( Sztuczki i kruczki w C++: http://www.mk.w.pl/porady/porady_cplusplus )
