Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 543
  • Last Modified:

Apache is Exiting!

Around 2am today and yesterday, this message is in the Apache logs:
Child 3403 returned a Fatal error... \nApache is exiting!

A manual start of the httpd service brought it back up fine.  Any ideas to see what happened, and troubleshoot?

The server has 2gb of ram installed and [free] currently says:
-/+ buffers/cache:     used: 294k   free: 1771k
From the log file:
 
accept_mutex_on: Invalid argument
No log handling enabled - turning on stderr logging
read_config_store open failure on /var/net-snmp/snmpapp.conf
read_config_store open failure on /var/net-snmp/snmpapp.conf
read_config_store open failure on /var/net-snmp/snmpapp.conf
[Wed May 20 02:35:21 2009] [alert] Child 3403 returned a Fatal error... \nApache is exiting!
accept_mutex_off: Invalid argument
No log handling enabled - turning on stderr logging
read_config_store open failure on /var/net-snmp/snmpapp.conf
read_config_store open failure on /var/net-snmp/snmpapp.conf
read_config_store open failure on /var/net-snmp/snmpapp.conf

Open in new window

0
M256
Asked:
M256
1 Solution
 
elf_binCommented:
Often PHP or a PHP module is responsible for that.  Have you recompiled Apache recently?
Another cause is excessively large log files (rotate them if they are large).
I seem to remember a bug in Apache about version 1.3.34-4 that was very similar, is that the version of Apache you're using?
Basically the mutex thing is a semaphore - so a "lock".  That could really be anything unfortunately.  If you have support, phone the provider and let them sort it out.  If you don't have support, check all scripts used for any semaphore activity.  Recompile Apache.  Upgrade to the latest version of everything.
Also I note you've not configured logging, that would be a good idea to configure logging.  Plus your web server is trying to read a SNMP configuration file (/var/net-snmp/snmpapp.conf) but can't open the file.  That may or may not have something to do with it, depending on how the file is being opened.
0
 
random_ruCommented:
is it the same process id every time? use: pstree -p to find out what it is
0
 
M256Author Commented:
I cleaned up the log files, but still no joy.
I can't update 'cause of OS issues, so I'm switching to a clean install.  I think this will fix it.  Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now