1

I have just configured a new server that keeps dying from time to time. The error log indicated the following problem:

[Thu Feb 11 03:21:15.261690 2016] [mpm_prefork:emerg] [pid 1273] (43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 11 03:21:15.640431 2016] [core:alert] [pid 1256] AH00050: Child 1258 returned a Fatal error... Apache is exiting!

I tried the solution listed here (basically to add AcceptMutex flock to httpd.conf) , but Apache wouldn't start:

Invalid command 'AcceptMutex', perhaps misspelled or defined by a module not included in the server

So now I don't know what else to do.

Improve this question

2 Answers 2

Reset to default
4

If you go back and look at the page you linked to, there's a line a little bit further down that says:

With apache 2.4, use Mutex instead of AcceptMutex

Improve this answer
2
  • Well...I feel so stupid.
    – carla
    Feb 12, 2016 at 14:35
  • 1
    @carla Been there, done that...
    – Jenny D
    Feb 12, 2016 at 14:59
1

Try adding

AcceptMutex posixsem

in your apache conf

Improve this answer
2
  • Yes, I tried, and the same "Invalid Command" message appeared when I tried to restart Apache.
    – carla
    Feb 12, 2016 at 14:23
  • 1
    @carla if you use apache 2.4 Mutex posixsem
    – ZiTAL
    Jul 14, 2018 at 15:09

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .