Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Failed to start apache : Apache does not appear to be running :
Starting web server: Apache2apache2: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName.
The error 'Could not the server's fully qualified domain name, using 127.0.0.1 for ServerName.' is not fatal and pache should start aldow it reports that error.
Check your httpd.conf for this line 'Listen SOMETHING:80' edit it and change to 'Listen youripaddress:80' and restart apache.
Now try to connect to the web server.
Depending on your distro, the files are different names and can be in different locations..
Check your Webmin module config very carefully..
esp where apachectl and apachectl2 are present..
Standard names would have 2 added to the end..
The most frustrating part was guessing that "Path to httpd.conf" should be /etc/apache2/apache2.conf!!
Everybody talks about httpd.conf, but nobody says that there are two such files in a Debian system, one in /etc/apache/ and the other in /etc/apache2/.
The latter is empty, but the mere fact that there's both an apache and apache2 directories makes it very confusing, and I'm still not sure whether everything is properly setup.
My website is running fine, but given all these misunderstandings, it may show some surprises later. Cross fingers and wait for better documentation.
Originally posted by patitoconejita Ok guys, this morning I found the solution, and it took a lot of guess work, because the documentation on this is terrible.
It turns out that, for apache2, one needs to provide the following in the "Modules Config" section:
Apache server root directory: /etc/apache2
Path to httpd executable: /usr/sbin/apache2
Command to start apache: /etc/init.d/apache2 start
Command to stop apache: /etc/init.d/apache2 stop
Path to httpd.conf: /etc/apache2/apache2.conf
and leave the rest at the default values.
Thanks to all,
Ok, jumping in here
i did all that , but now when i click on the apache icon in webmin it takes me to the reconfigure panel..
seems i need to select some active modules.
I have no idea which ones are running and the "newbie, keep away just press reconfigure button"
keeps sending me back to the reconfigure panel...