Failed to start apache : Apache does not appear to be running :
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Originally posted by trickykid How are you trying to start apache? Is this the default packages that come with Slackware or your own compiled packages? Is apache already running?
When I start apache or restart it my server says it is already running. I am using webmin so when I start it there I get the error message above. The packages are Slackware packages I upgraded my system and now apache doesn't work.
After upgrading to 10.1 apache was working fine until somewhere around lastnight it seemingly has flipped.. d: It isnt running, ps aux cannot find it, and if I restart & start & stop it via rc.d&*rc.httpd get some weird results>
start: appears to start as before and normally
stop: not running
Also a manual start via apachectl and httpd seem to go ok, but nothing is actually started..
Apache was working fine before the update, I was riding the current till the end, but the last updates killed it, or so I assume..
Ill try downgrading later, but also inetd is behaving oddly after the final update.. glibc not so nicely installed?
Now at home, so back to some more tests.. Tried starting it while monitoring acctail, the httpd process exits rightaway with code 25 ... Why doesnt this get reported in any way? And what is 25? And what could cause it?
okies, this is getting interesting.. Ill do a full post incase someone has a similar problem. I googled for exitcode 25, and ended up in some dspam mailinlist post. There the same code was caused by a too large errorlog.. Soo, out of interest, I checked, and for some oddball reason my apache error_log had bloated to a tad over 2 gigs.. I catted some /dev/zero over it, and voila, apachge starts and stays online..