Apache still crashes out.

[Peter]

[Thu Mar 4 00:13:02 2004] [warn] child process 15080 still did not exit, sending a SIGTERM
[Thu Mar 4 00:13:02 2004] [warn] child process 24522 still did not exit, sending a SIGTERM
[Thu Mar 4 00:13:11 2004] [crit] (98)Address already in use: make_sock: could not bind to port 8090



I think the last one is the real problem, since it goes down after that every time.

Please help. (BTW, it's almost everytime about midnight).

[DirectAdmin Support]

Hello,

I don't think that port is even need to be open. You can just comment out the frontpage virtualhost at the bottom of the /etc/httpd/conf/httpd.conf file and restart apache.

John

[Peter]

Listen 8090
<VirtualHost _default_:8090>
DocumentRoot /usr/local/frontpage/version5.0/admin-exes
DirectoryIndex fpadmcgi.exe
<Directory /usr/local/frontpage/version5.0/admin-exes/>
AddHandler cgi-script .exe
Options ExecCGI
</Directory>
</VirtualHost>

So what should i tag out?
Ill just tag out all for the moment

[DirectAdmin Support]

Yes, I don't believe anything uses it thus there is no reason to have it open.

John

[Peter]

So no frontpage extensions or what?

[DirectAdmin Support]

Hello,

I think frontpage uses 80. Thats just for the web based frontpage admin area which isn't setup.

John

[Peter]

Oh ok, probably all problems solved now then.
Thanks

[Peter]

Oh no....

[Sat Mar 6 00:12:10 2004] [crit] (98)Address already in use: make_sock: could not bind to port 443


What is wrong with my server??

[ProWebUK]

Check if it is being used..

netstat -lnp | grep "443"

If its being used by httpd, try stopping then starting:

service httpd stop
*wait a few seconds...*
service httpd start

You should also be able to kill the PID from netstat if that fails..

Chris

[Peter]

Problem is, this happens every night....
I just don't know how this can happen every time, i don't want my server to be unreachable every night...

[ProWebUK]

Have you tried rebuilding apache and rebooting the system since its occured... is there anything in your log files?

Chris

[DirectAdmin Support]

Hello,

So what happens when you run "service httpd restart" ?... you get the socket errors? (FreeBSD: /usr/local/etc/rc.d/httpd restart) ... if the shutdown isn't happenning fast enough, then you may need to add a pause between the "stop" and the "start" to ensure it has enough time to come to a full stop before starting up again. (so that no apache processes are running)

John

[Peter]

John, nothing happens, it just starts ok, but when it runs for about 12/13 hours, it crashes out.

[TurtleBay]

I have this problem, too. At the 12:13am log file restart, Apache will crash with an error related to front page. Then, if I'm not up to notice it, the server stays down all night...

Is there anything else we can do to be sure that Apache gets restarted OK? DA thinks Apache is still running (and it is, but its frozen) Can DA actually request a page or something so it can see if Apache is really working?

Thanks,
John

[Peter]

We probably found the problem, Zend, when we disabled it, everything worked (well atleast for 2 days now).

But we need to find something about it though.

[TurtleBay]

Interesting...But I'm not using Zend, so that's not the cause of my problem...

John

[Peter]

You haven't even installed it?
What error message does your log file give you?

[TurtleBay]

No, not Zend Optimizer. When I tried to install it last time, it made Apache segfault. I have not tried to install it lately.

Log file looks like this:

[Tue Mar 9 00:15:02 2004] [warn] child process 30162 still did not exit, sending a SIGTERM
[Tue Mar 9 00:15:05 2004] [error] Cannot remove module mod_frontpage.c: not found in module list
[Tue Mar 9 00:15:05 2004] [crit] (98)Address already in use: make_sock: could not bind to port 443


Apache then sits in memory, but not responding to anything.

John

[Peter]

I had exactly the same problem.

[TurtleBay]

I double checked to be sure, I do not have Zend Optimizer installed. I do have ioncube php extension running though.

John

[Peter]

I guess that is not changing anything to PHP...

[koos]

mmm i did post already on a other place but i'm thinking that i have to post here..:)

Since i did update php 4.3.4 --> 4.3.5
and MySQL 4.0.16 --> 4.0.18
i have troubles with httpd.
my http-error.log
[Mon Apr 12 22:42:01 2004] [warn] child process 14266 still did not exit, sending a SIGTERM
[Mon Apr 12 22:42:05 2004] [crit] (98)Address already in use: make_sock: could not bind to port 8090

:confused: :confused:
Who can help me... why does httpd stops...
I have really problems with it.


Thanks for help

[DirectAdmin Support]

Hello,

Did you remove/update the configure.apache_ssl and configure.php before doing the update?

rm -f configure.*
./build clean
./build update
./build all

Give that a go.

John

[ClayRabbit]

You can try to solve that promlem by modifying 'service apache restart' command to wait until all apache processes exit before starting server again.

Edit /etc/init.d/httpd and add following function to script:

wait_after_stop(){
count=${2:-30}
while [ 0$count -gt 0 ]
do
PIDS=`ps -C$prog --no-heading e | grep $httpd` || break
PIDS=`echo "$PIDS" | awk '{print $1}' | tr '\n' ' '`
echo Remaining processes: $PIDS
stop
sleep 2
count=`expr $count - 1`
done
if [ 0$count -eq 0 ];
then
echo Remaining processes: $PIDS
return 1
fi
return 0
}

Replace
restart)
stop
start
;;
with restart)
stop
wait_after_stop "httpd" 20
start
;;


With that modifications 10 days ago we have solved "daily apache crash problem" on 2 our servers. Seems it's works without problems.
(I have found that solution at http://forum.plesk.com/showthread.php?s=&threadid=2409 and modified it a little.)

[DirectAdmin Support]

Great "active checking" solution :) Thanks.

John

[koos]

apache didn't crash after monday 22.42. Whe have now a script thats is checking apache and restart if apache fails and send us a email.

[duke27]

I CAN PUT THIS SCRIPT WHERE I WANT IN
/etc/init.d/httpd ??

I MEAN AT THE END OR AT THE BEGIN OF THE FILE ITS CHANGE NOTHING??

[Wunk]

See my reply in this thread:
http://www.directadmin.com/forum/showthread.php?s=&threadid=3884

Applied it on 3 problem servers, and so far fixed them all, no more nightly crashes of apache in several months :)

[torp]

Originally posted by ClayRabbit
You can try to solve that promlem by modifying 'service apache restart' command to wait until all apache processes exit before starting server again.

Edit /etc/init.d/httpd and add following function to script:

wait_after_stop(){
count=${2:-30}
while [ 0$count -gt 0 ]
do
PIDS=`ps -C$prog --no-heading e | grep $httpd` || break
PIDS=`echo "$PIDS" | awk '{print $1}' | tr '\n' ' '`
echo Remaining processes: $PIDS
stop
sleep 2
count=`expr $count - 1`
done
if [ 0$count -eq 0 ];
then
echo Remaining processes: $PIDS
return 1
fi
return 0
}

Replace
with

With that modifications 10 days ago we have solved "daily apache crash problem" on 2 our servers. Seems it's works without problems.
(I have found that solution at http://forum.plesk.com/showthread.php?s=&threadid=2409 and modified it a little.)

Is this done by default now in the /etc/init.d/httpd file?

I have had quite a few server crash problems, even after updating my customapache to the most recent DA files.

[DirectAdmin Support]

Hello,

Yes:

http://files.directadmin.com/services/customapache/httpd
http://files.directadmin.com/services/customapache/httpd_2
http://files.directadmin.com/services/customapache/httpd_freebsd
http://files.directadmin.com/services/customapache/httpd_2_freebsd
http://files.directadmin.com/services/customapache/httpd_debian

John