Apache fainted

C

charliez

Verified User
Joined
Sep 29, 2004
Messages
83
Woke up this morning with all sites gone. Apache had kicked the bucket and joined the bleeding choir invisible during the night.

Started it through DA, and all is OK. All I can find in the logs is:

[Wed Oct 20 00:31:02 2004] [warn] child process 80143 still did not exit, sending a SIGTERM
[Wed Oct 20 00:31:41 2004] [warn] NameVirtualHost 64.92.163.254:80 has no VirtualHosts
(... More virtual hosts ...)
[Wed Oct 20 00:31:41 2004] [crit] (48)Address already in use: make_sock: could not bind to port 8090
[Wed Oct 20 00:31:43 2004] [error] child process 80143 still did not exit, sending a SIGKILL
[Wed Oct 20 00:31:43 2004] [notice] caught SIGTERM, shutting down


No-one was working on the server, so it makes me a little jumpy.


Anybody can make any sense of the above extract from the logs?

No way of setting apache so that it will restart if it receives a sigkill and waves bye-bye?

Cheers,
C.
 
GXX said:
what's port 8090?
Click to expand...


I hope that was a question ment for the general audience, and not for me? I haven't a clue. Definately not something I have set up on the server.:confused:
 
jmstacey said:
8090 is frontpage.
This might help you:
http://help.directadmin.com/item.php?id=31

Directadmin also attempts to restart apache every minute if it goes down unless you have set it otherwise inthe services.list file.
Click to expand...

Thanks! From the link you gave and your info on restart attemts, I gather that the problem was not as much the crash, but the fact that DA could not restart apache.

I'll try to follow the istructions on the link you gave, and hope I don't f*** it up.

Cheers, and thanks again!
C.
 
Ok. Gave it a try. Got a fair amount of "file already exists", but at least I didn't crash the server.

Tried "restart" from DA and all seems ok, but who am I to say...

Thanks again!
C.
 
Most of the file already exists or module already loaded usually means that there are duplicate entries in the httpd.conf
They are usually added after recompiling apache accessories such as perl or php.
They shouldn't cause any problems but the duplicates can be removed from the configuration.
 
Last edited:
hi,

i am facing this problem after i run apachectl configtest:

# apachectl configtest
Warning: DocumentRoot [/usr/local/frontpage/version5.0/admin-exes] does not exist
Syntax error on line 30 of /usr/local/directadmin/data/users/admin/httpd.conf:
Invalid command 'php_admin_flag', perhaps mis-spelled or defined by a module not included in the server configuration
#


Please help.

right now what i did is i comment all the httpd.conf.

now my lines become like this

#php_admin_flag engine ON
#php_admin_flag safe_mode OFF
#php_admin_value sendmail_path '/usr/sbin/sendmail -t -i -f user
 
I get the "Warning: DocumentRoot [/usr/local/frontpage/version5.0/admin-exes] does not exist"
warning but I think its only because I do not use frontpage and none of my clients do either so until someone starts reporting problems I don't think there's a problem.

The second error your getting is being caused because the php modules are not being loaded correctly is my guess. Its probably not a good idea to comment out what you did since that is what determines whether an account has php and safe_mode enabled or disabled.

I modified my config file a bit from the default one since some of the modules were not loading in the correct order, and most applications add their own entries so I removed the <IF .... entries.
I attached it to this post. You can use it and compare it with yours to get it near error free. Thit configuration doesn't produce any errors except the one I mentioned above.
 

Attachments

Last edited:
jmstacey said:
Most of the file already exists or module already loaded usually means that there are duplicate entries in the httpd.conf
They are usually added after recompiling apache accessories such as perl or php.
They should cause any problems but the duplicates can be removed from the configuration.
Click to expand...


Just a quick check. Did you mean they "should cause any problems" or "they shouldn't cause any problems"?

Cheers,
C.
 
jmstacey said:
Shouldn't

Sorry about that. Fixed the typo.
Click to expand...


I thought so from the structure of your sentence and your overall tone of laisse faire. Thanks for all your help!

Cheers,
C.
 
You must log in or register to reply here.
Back
Top