Apache crashing

ne0phyte

Verified User
Joined
Mar 18, 2006
Messages
7
Hi,

I have a Debian system with Directadmin 1.26.1.

Apparently i've been having a problem with Apache crashing every 2 hours, but as the service restarted automatically, i didn't notice it.

In error.log i see following:

[Sun Mar 5 08:11:01 2006] [notice] Caught SIGTERM, shutting down
[Sun Mar 5 08:11:02 2006] [notice] Apache configured -- resuming normal operations
[Sun Mar 5 08:11:02 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Mar 5 08:11:02 2006] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sun Mar 5 10:10:01 2006] [notice] SIGHUP received. Attempting to restart
[Sun Mar 5 10:10:01 2006] [notice] Apache configured -- resuming normal operations
[Sun Mar 5 10:10:01 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Mar 5 10:10:01 2006] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sun Mar 5 10:11:01 2006] [notice] caught SIGTERM, shutting down
[Sun Mar 5 10:11:01 2006] [notice] Apache configured -- resuming normal operations
[Sun Mar 5 10:11:01 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Mar 5 10:11:01 2006] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sun Mar 5 12:11:01 2006] [notice] SIGHUP received. Attempting to restart

it's like that approximately every 2 hours.

Now i didn't notice this untill i installed a new kernel with grsec support. Now it doesn't automatically restart apache, i get weird errors like this:

[Sat Mar 18 18:11:01 2006] [notice] SIGHUP received. Attempting to restart
Syntax error on line 1 of /dev/null:
Invalid command '397x165', perhaps mis-spelled or defined by a module not included in the server configuration
Syntax error on line 4 of /dev/null:
Invalid command 'Connection', perhaps mis-spelled or defined by a module not included in the server configuration

now this is probably due to the new kernel, although i can't image what, but the main problem is apache shutting down.

Has anyone ever seen anything like this before?
 
So now I'm getting these DA messages stating Apache is down.

Right before that i'm now getting following message from DA:

Your hostname, , and the servername you have set in DirectAdmin, blackbox.lsnet.be, do not match. It is recommended that these two values are the same.

Solution:

Either change the servername in DirectAdmin or run the 'hostname.sh' script via ssh to change your hostname

Unable to resolve your hostname, . This will cause major issues when sending email.

Solution:

Create an A record for your hostname (.) in your DNS control panel. Point the hostname to your server's main IP address. Also check /etc/hosts to ensure that the server ip is correctly set.

I have an A record for my hostname, always have and /etc/hostname & the one i've added in DA under Admin Settings are the same.

I've also found that just before my apache crashes following cron is executed:

syslog:Mar 18 22:10:01 ******* /USR/SBIN/CRON[23866]: (root) CMD (/usr/local/directadmin/dataskq)
syslog:Mar 18 22:10:01 ****** /USR/SBIN/CRON[23868]: (root) CMD (echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue)

1 second after that my apache gets receives a Sighup.

my /usr/local/directadmin/log is empty :(

any ideas?
 
Last edited:
Back
Top