Apache still crashes out.

P

Peter

Verified User
Joined
Jan 15, 2004
Messages
94
[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).
 
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
 
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
 
Hello,

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

John
 
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??
 
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
 
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...
 
Have you tried rebuilding apache and rebooting the system since its occured... is there anything in your log files?

Chris
 
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
 
John, nothing happens, it just starts ok, but when it runs for about 12/13 hours, it crashes out.
 
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
 
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.
 
Interesting...But I'm not using Zend, so that's not the cause of my problem...

John
 
You haven't even installed it?
What error message does your log file give you?
 
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
Click to expand...

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

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

John
 
You must log in or register to reply here.
Back
Top