Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
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.
when trying to restart apache/2.0.52 after I had to hard reboot my redhat9 box. I had to do a manual fsck and just took the default option for whatever came up.
If you just did a hard reboot, why can't you do another one?
As the website suggests, the trick with the ipcs command is only to be used if you don't want to
reboot your machine.
If you hard reboot it, the shared memory should be de-allocated anyway, unless it was dumped to a file on disk.
I did a hard reboot which caused no end of problems. I had to repeatedly run fsck before eventually being able to log in.
Unfortunately, I still have the same problem i.e.
Hmmm. After a hard reboot, all shared memory should have been cleaned up anyway.
By the way, you shouldn't use a file on disk to store the scoreboard data. Shared memory is faster.
If ipcs (run as root) doesn't mention the shared memory, then your process doesn't have access to it, or, more likely, it simply doesn't exist. A hard reboot should have cleaned it up, so it can be normal that ipcs doesn't list it anymore.
However, even on systems that don't have Apache running (like my simple RH8 box), ipcs -m still lists a bunch of stuff from other programs. The fact that your ipcs doesn't indicate anything at all, may point to a different problem, not specific for Apache, but for all processes who use shared memory.
A few questions:
-Can you try an ls -l of /var/run and /var/run/apache?
-Did you recently change anything to your system configuration, such as updates of the C libraries, etc?
-Are you absolutely sure that you ran the ipcs command under the root user?
-Can you please look at the other system logs in /var/log. Maybe there's an indication of a larger problem.
-What did fsck report back to you? And what did it fix, in order for your login to succeed?
Finally, I've read on a site that you could take a look at some pseudo-files in /proc, such as /proc/self/maps, but they're probably hard to understand.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.