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!
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 was able to login using SSH but all my websites were down.
Perhaps it was a mysql issue and not a server issue?
I did a reboot and my websites went back up.
I have not talked with my host they provide very limited support as this is a self managed dedicated server.
Operating System: CentOS 5
Processor: Intel Pentium 4 - 3.0 GHz
RAM: 2 GB
Total Disk Space: 120 GB
RAID: None
Bandwidth Quota: 500 GB
So then the server itself was up, there was just some problem with Apache (which I will assume is your web server). Have you checked the Apache logs right before and during the downtime?
You don't need to post it all here, you just need to find the lines that tell you what the problem is/was.
Perhaps we need to step back a little here. What exactly is your skill level with Linux in general, and services like Apache? Figuring out what happened is not going to be as easy as running a command and it telling you exactly what is wrong, you will likely need to get your hands a little dirty.
Install Logwatch. It's good for weeding out the noise and showing you the "interesting" parts of logs efficiently as a report. Anyone who runs any (Internet-facing) services should run Logwatch or equivalent. (Maybe patch Logwatch with this and then) run logwatch as 'logwatch --numeric --detail High --archives --range All --save /var/log/logwatch.report && bzip2 /var/log/logwatch.txt'. Then if all went OK you can copy /var/log/logwatch.txt.bz2 to your local system, decompress it and attach it to this thread.
Forgive me my ignorance but what could it actually do to help him diagnose his problems?
I suppose it might give him an 'easy' way to perform certain admin. activities - such as seeing what services are running and restart services which have failed for some reason, if it happens again. However, as he is renting a dedicated server, he probably already has cPanel or Plesk - which will overlap with Webmin and cause problems. And ofcourse, if his webserver (or services it depends on) is failing, Webmin might not be there when he needs it most.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.