Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have inherited a debian server running apache. This server has been up for months withouth a proble/reboot. Today the web server is no longer responding to requests and using graceful restart or stop did not fix apache.
I went in to gracefully restart apachect1 but it would not recognize the command (a search revealed apachect1 in several different folders /usr/local/apache/bin and usr/sbin--neither recognized the command).
I then rebooted the box to see if this would correct the problem, and it notes
/usr/sbin/apachect1 could not be started
it also says "skipping 1 bad record, no valid reports found!"
I checked the error log, the only error in there for the last few days is a "cannot open mime type log", and these seem to have occured once I rebooted debian. Looking around online shutting down apache without graceful command may have been a bad idea. Hopefully this did not totally crash apache! Moving around in winscp and terminal window shows debian seems fine. This is probably the first time this server has rebooted in months, I have upgraded/updated debian on this server since being here, could this be the problem e.g. does apache config need to be updated?
which might clean up any .pid files left lying around
if you have apachectl in two places it may mean you have two installations of apache floating round your system. This is not necessarily a bad thing, however it would benifit you to know which one works and where its config files are kept. Do you only have one copy of http.conf?