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 a dedicated server to help me learn the ins and outs of Linux.
Just recently the web server went down returning 500 errors. I restarted the server but now the server doesn't respond to http.
I can ping the server fine but I can't access it at all via SSH. My provider allows me to boot to a recovery kernel. This post is concerned with the SSH issue. When I SSH to the recovery kernel I can mount the drives. All my data seems to be present. I've looked at the SSH and sshd config files but nothing seems a miss.
Could it be possible the boot is reaching run level that doesn't start SSH?
if it doesn't respond to ssh OR http then somethign bigger must be going on. Check /var/log/messages after a boot attempt. if it gets far enough through the boot process (i.e. mounts the actual disk) then all the boot up logs from the first few milliseconds should be in there to look through, and also /var/log/secure should show when ssh is coming up and down. I'd wonder if it's not the actual network config itself though.
That list of errors you had look like (I'm going to say IS) a blanket chmod gone wild (like a "chmod -R 755 *"). This would remove various privileges that are assigned to files to allow them to work properly. If you accidentally did this, the easiest solution is to reinstall - but do try to backup any data you want to keep first.
tail: cannot open `error.log' for reading: No such file or directory
root@rescue:~/d1/var/log/httpd# tail error_log
[Sun Mar 03 04:02:08 2013] [notice] Digest: done
[Sun Mar 03 04:02:09 2013] [warn] RSA server certificate wildcard CommonName (CN) `*.lxlabs.com' does NOT match server name!?
[Sun Mar 03 04:02:09 2013] [notice] Apache/2.2.22 (Unix) DAV/2 PHP/5.2.17 mod_ssl/2.2.22 OpenSSL/0.9.8e-fips-rhel5 configured -- resuming normal operations
[Mon Mar 04 03:59:41 2013] [notice] caught SIGTERM, shutting down
[Mon Mar 04 03:59:41 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 04 03:59:41 2013] [warn] RSA server certificate wildcard CommonName (CN) `*.lxlabs.com' does NOT match server name!?
[Mon Mar 04 03:59:41 2013] [notice] Digest: generating secret for digest authentication ...
[Mon Mar 04 03:59:41 2013] [notice] Digest: done
[Mon Mar 04 03:59:42 2013] [warn] RSA server certificate wildcard CommonName (CN) `*.lxlabs.com' does NOT match server name!?
[Mon Mar 04 03:59:42 2013] [notice] Apache/2.2.22 (Unix) DAV/2 PHP/5.2.17 mod_ssl/2.2.22 OpenS
SL/0.9.8e-fips-rhel5 configured -- resuming normal operations
It was on the 4th march that I started to get problems. I've not chmodded any files. Is it possible this is a hack gone wrong?
I feel if I can get SSH working I'll be able to repair the web server.