This should be common to all mpm's. Not just peruser. Something went
horribly wrong so it seems and recovery doesn't seem an option.
On 25.01.2011 15:37, Hannes Landeholm wrote:
FYI got this very unusual error just after reloading apache configuration:
[Tue Jan 25 13:15:40 2011] [emerg] (13)Permission denied: couldn't
grab the accept mutex
[Tue Jan 25 13:15:41 2011] [error] [client 92.32.203.112] File does
not exist: /campusbokhandeln.se/img/admin_bg.pn
<http://campusbokhandeln.se/img/admin_bg.pn>, referer:
http://www.karlstad.campusbokh$
[Tue Jan 25 13:15:41 2011] [alert] Child 31436 returned a Fatal
error... Apache is exiting!
[Tue Jan 25 13:15:41 2011] [emerg] (43)Identifier removed: couldn't
grab the accept mutex
[Tue Jan 25 13:15:41 2011] [emerg] (43)Identifier removed: couldn't
grab the accept mutex
[Tue Jan 25 13:15:41 2011] [emerg] (43)Identifier removed: couldn't
grab the accept mutex
[Tue Jan 25 13:15:41 2011] [emerg] (43)Identifier removed: couldn't
grab the accept mutex
[Tue Jan 25 13:15:41 2011] [emerg] (22)Invalid argument: couldn't
release the accept mute
As you can see the whole apache server was brought down just because I
child returned a fatal error. That dangerous and exploitable reaction
should be removed IMO. Childs should NEVER be able to stop the entire
server. If they return a fatal error they should promptly be killed
and replaced.
Regards,
Hannes
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
