Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm pretty well versed in using apache, so this is really bugging me. I've googled and searched here. Can't find anything.
Using Suse 9.1, and have installed as typical web server (apache2 2.0.49, php4 4.3.4, mysql 4.0.18). Everything seemed to install fine.
However, when I do a /etc/init.d/apache2 start, it fails.
Further, /var/log/apache2 has 3 files, error and access files are 0 length. rcapache2.out only contains "Syntax OK".
Even if I manually enter:
/usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf
(which is the cmdline that is executed from /etc/init.d/apache2), exits with error code 0 and no httpd daemon. Same with apache2ctl.
How can I get some diagnostics to see what is wrong? I can't even get an exit code to debug.
I had a similar situation when my error_log had bloated to over 3 gigs in size. If the logs are of 0 size, id say theres definately something wrong with them. Perhaps try deleting them, and let apache re-create?
a possible method to take a closer look to what might fail, would be to monitor 'acctail' while attempting to start apache. Its not standar software, but a helluve nice tool. It monitors all exiting processes and their exit status.
Nothing telling there, I just compared the trace output to one of my suse box's (default apache install) and got identical output with a fully running process resulting....Appears as thought it's starting, then dying after sucessful start...
Have you made any changes to the default config's? if so, what?
I'll think on it some more and post back if anything comes to me .....
OK WTF Happened I dont know but im guessing there was an update the wiped the apache2 exec file and renamed it apache2.1 I removed apache2 and renamed apache2.1 to apache2 and its up again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.