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.
I've deployed a couple of server programs using RPC in a Fedora 6 server.
These server programs are being accessed by more than 40 simultaneous users. The server gets rebooted now and then. I do not know what the problem is?.. I don't know how to track the bug if it is in the server programs?
Yes. I think you are correct. It is a hard reboot at any random time without even the OS switching off properly. How to identify the problem?
I get some messages from syslod often in the virtual consoles saying that something like "avc=...permission denied ... pid=... "postmaster"...device=sda2..."
Could you give some idea to rectify the problem....
Yes. I think you are correct. It is a hard reboot at any random time without even the OS switching off properly. How to identify the problem?
I get some messages from syslod often in the virtual consoles saying that something like "avc=...permission denied ... pid=... "postmaster"...device=sda2..."
Could you give some idea to rectify the problem....
Thanks
Well, frequent candidates for random reboots are bad memory sticks or overheated cpu. So, I think that a good place to start is to use a livecd with memtest86 or to try to replace the ram sticks if you have some sane ones available.
You can also check the temperature of your cpu with any monitoring program. mbmon -A should tell you in command line, there are lot of graphical monitors as well. You should monitor it *while* you are doing heavy work (try compiling the kernel or launching some modern game or whatever, and see if the temperature raises too much while doing so.
I or someone else here could take a look at your dmesg output just in case, so if you can, post it to pastebin.com and put a link here so we can review it.
The last time I ran into a similar constant rebooting phenomenon it was caused by a new Kingston RAM module on a completely new PC hardware. Kingston is famous for being good, but obviously not free from failing occasionally.
The problem can also be caused by problems with the motherboard (that would be much more severe) or, as already mentioned, by overheating. You should check for the RAM modules first, because that's rather easy to do and verify.
Well, frequent candidates for random reboots are bad memory sticks or overheated cpu. So, I think that a good place to start is to use a livecd with memtest86 or to try to replace the ram sticks if you have some sane ones available.
You can also check the temperature of your cpu with any monitoring program. mbmon -A should tell you in command line, there are lot of graphical monitors as well. You should monitor it *while* you are doing heavy work (try compiling the kernel or launching some modern game or whatever, and see if the temperature raises too much while doing so.
I or someone else here could take a look at your dmesg output just in case, so if you can, post it to pastebin.com and put a link here so we can review it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.