Error: Accept mutex: flock (Default: flock)

Question

Level 1

30 points

Error: Accept mutex: flock (Default: flock)

Recently, I had an outage with my ISP and when services were returned my server has not run properly and after Googling this error and scoruing the Apple site here, I'm still a bit confused and hope someone can steer me in the right direction to resolve this problem.

Does anyone know where to start investigating this error?
Accept mutex: flock (Default: flock)

My error log continues to stop at this point. I'm working from OSX 10.3 through a Lynksys router and Sprint DSL and unable to get my server back up and running at idav.com, although I can ping it, but the error logs still render the same error with no display. Any help appreciated...
thanks.

David

[Wed Nov 23 12:01:33 2005] [notice] Apache/1.3.28 (Darwin) configured -- resuming normal operations
[Wed Nov 23 12:01:33 2005] [notice] Accept mutex: flock (Default: flock)

Quicksilver Dualie, Mac OS X (10.3.9)

Posted on Nov 23, 2005 9:40 AM

Reply

Answer 1

Dec 16, 2005 6:57 AM in response to David Cate

I have the same issue. Have you solved your problem?

Reply

Answer 2

David Cate Author

Level 1

30 points

Dec 28, 2005 10:07 AM in response to Stephen Strand

Hello. Still have the same problem for some reason and I've been unable to locate any details on the web.

Quicksilver Dualie Mac OS X (10.3.9)

Reply

Answer 3

Camelot

Level 9

58,527 points

Dec 28, 2005 10:22 AM in response to David Cate

Keep looking. The mutex message you list is not any kind of problem.

The 'mutex' message is just telling you how Apache is handling mutual exclusions - that is, multiple processes (or threads) accessing the same file at the same time. The message is telling you it's using the 'file locking' ('flock') method where the process that's modifying a file locks it to prevent others from changing it. Additionally the message is telling you that 'flock' is also the default mode.

In other words, this is a status message indicating, essentially, 'situation normal'.

If your site is not working then there's some other issue at fault.

Can you hit the server locally?
If that's truly all your logs say then I don't think your site is getting any traffic, in which case I'd be looking at router/port forwarding setups, and the like.

Reply