|
|||
|
hello
i have few servers where i deleted domlogs folders because that was above 10-20 GB suddenly after few hours i suddenly discovered that apache fails every few seconds i then recreated domlogs made sure that domlogs have same permission and owner # ll total 76 drwxr-xr-x 15 root root 4096 Feb 5 22:00 ./ drwxr-xr-x 23 root root 4096 Jan 10 20:00 ../ drwxr-xr-x 2 root root 4096 Jan 21 00:33 bin/ drwxr-xr-x 2 root root 4096 Jan 21 01:04 cgi-bin/ drwxr-xr-x 11 root root 4096 Feb 5 22:35 conf/ drwxr-xr-x 9 root root 4096 Nov 23 14:02 conf_pre_ea3/ drwx--x--x 2 root wheel 12288 Feb 5 22:42 domlogs/ drwxr-xr-x 70 root wheel 12288 Feb 5 21:45 domlogsx/ drwxr-xr-x 4 root root 4096 Feb 4 17:06 htdocs/ drwxr-xr-x 3 root root 4096 Jan 21 00:33 icons/ drwxr-xr-x 3 root root 4096 Jan 21 00:33 include/ drwxr-xr-x 2 root root 4096 Jan 21 00:48 libexec/ drwxr-xr-x 2 root root 4096 Feb 5 22:48 logs/ drwxr-xr-x 4 root root 4096 Jan 21 00:33 man/ drwxr-xr-x 2 nobody nobody 4096 Jan 21 00:33 proxy/ then restarted and problem repeated then i commented out the #CustomLog #BytesLog and restarted but same problem i rebuilded apache and php several times with different versions and it didn't help either i have the same problem on all the servers from which i delete domlogs on var/log/messages nothing on apache error log there is [Tue Feb 4 12:16:04 2008] [notice] caught SIGTERM, shutting down which usually apache dies after it appear please do help me waiting .......... |
|
|||
|
1. Do any files get created in the domlogs directory?
2. Does the process dies immediately ? 3. Have you tried to strace the apache process ? |
|
|||
|
i saw this on one of the affected server before apache dies too
[Wed Feb 6 00:05:03 2008] [error] Bad pid (7747) in scoreboard slot 23 [Wed Feb 6 00:05:03 2008] [error] Bad pid (7809) in scoreboard slot 24 [Wed Feb 6 00:05:03 2008] [error] Bad pid (9910) in scoreboard slot 25 [Wed Feb 6 00:05:03 2008] [error] Bad pid (10105) in scoreboard slot 26 [Wed Feb 6 00:05:03 2008] [error] Bad pid (7461) in scoreboard slot 22 [Wed Feb 6 00:05:03 2008] [error] Bad pid (7747) in scoreboard slot 23 [Wed Feb 6 00:05:03 2008] [error] Bad pid (7809) in scoreboard slot 24 [Wed Feb 6 00:05:03 2008] [error] Bad pid (9910) in scoreboard slot 25 [Wed Feb 6 00:05:03 2008] [error] Bad pid (10105) in scoreboard slot 26 [Wed Feb 6 00:05:03 2008] [notice] caught SIGTERM, shutting down now running your command |
|
|||
|
Try to run the following command:
Code:
strace -o /tmp/lala -f /usr/local/apache/bin/httpd -DSSL |
|
|||
|
Quote:
Is apache already running ???? this means that a process is already bind to TCP port 443. Try Code:
lsof -i tcp |grep https |
|
|||
|
now apache dies again
attached is the lala file at the time oif apache failure this reappaeared in error log [Wed Feb 6 00:10:07 2008] [error] Bad pid (28416) in scoreboard slot 16 [Wed Feb 6 00:10:07 2008] [error] Bad pid (22008) in scoreboard slot 18 [Wed Feb 6 00:10:07 2008] [error] Bad pid (28574) in scoreboard slot 19 [Wed Feb 6 00:10:07 2008] [error] Bad pid (22136) in scoreboard slot 21 [Wed Feb 6 00:10:07 2008] [error] Bad pid (22518) in scoreboard slot 22 [Wed Feb 6 00:10:07 2008] [error] Bad pid (23590) in scoreboard slot 23 [Wed Feb 6 00:10:07 2008] [error] Bad pid (23634) in scoreboard slot 25 [Wed Feb 6 00:10:07 2008] [error] Bad pid (23664) in scoreboard slot 26 [Wed Feb 6 00:10:07 2008] [error] Bad pid (28416) in scoreboard slot 16 [Wed Feb 6 00:10:07 2008] [error] Bad pid (22008) in scoreboard slot 18 [Wed Feb 6 00:10:07 2008] [error] Bad pid (28574) in scoreboard slot 19 [Wed Feb 6 00:10:07 2008] [error] Bad pid (22136) in scoreboard slot 21 [Wed Feb 6 00:10:07 2008] [error] Bad pid (22518) in scoreboard slot 22 [Wed Feb 6 00:10:07 2008] [error] Bad pid (23590) in scoreboard slot 23 [Wed Feb 6 00:10:07 2008] [error] Bad pid (23634) in scoreboard slot 25 [Wed Feb 6 00:10:07 2008] [error] Bad pid (23664) in scoreboard slot 26 [Wed Feb 6 00:10:07 2008] [notice] caught SIGTERM, shutting down |
|
|||
|
thanks for your interest in helping me
while httpd was down there were nothing listening to the https port but after i restarted it , its only https httpd 27962 root 16u IPv4 29004321 TCP *:https (LISTEN) httpd 28034 nobody 16u IPv4 29004321 TCP *:https (LISTEN) httpd 28035 nobody 16u IPv4 29004321 TCP *:https (LISTEN) httpd 28036 nobody 16u IPv4 29004321 TCP *:https (LISTEN) httpd 28037 nobody 16u IPv4 29004321 TCP *:https (LISTEN) httpd 28038 nobody 16u IPv4 29004321 TCP *:https (LISTEN) also apache dies only after [Wed Feb 6 00:10:07 2008] [notice] caught SIGTERM, shutting down however the error of listening on ssl port happens but it doesn't kill apache |
|
|||
|
Can you please post the file again but run it with the command (please make sure that no apache processes are still running, if any, and post also the results of lsof i ask ed you befora:
Code:
strace -s 512 -o /tmp/lala -f /usr/local/apache/bin/httpd -DSSL |
|
|||
|
died again
this time i see only [Wed Feb 6 00:35:03 2008] [notice] caught SIGTERM, shutting down i commented out all php extensions in error log 200+ mb this time so here are the last 100 lines of it Quote:
|
|
|||
|
Not very helpful. If you zip the file how big is it ? Please try to run it again under strace but instead of 512 (in -s 512) try 64 to see it the trace file gets smaller. Also try to compress it with gzip -9 in order to get maximum compression.
|
|
|||
|
That's not good. One last try to see if the file gets smaller:
Code:
strace -s 64 -o /tmp/lala -f /usr/local/apache/bin/httpd -F -DSSL If the file is huge again I have to try to guess... 1. Disable any php modules in your configuration file. 2. Disable any other loaded modules (one at a time). |
![]() |
| Thread Tools | |
| Display Modes | |
|
|