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.
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.
Occasionally I my Mandrake 9 machine will lockup from seti at home. this sometimes happens within a day or two, other times it may happen in a month. I wrote down what I thought were the important parts of the error message it printed out before it locked:
Unable to handle kernel NULL pointer dereference at virtual address 00000000
*pde = 00000000
Oops = 0000
... some omitted stuff ...
process setiathome (pid: 1728, stackpage=db8e7000)
Any ideas? besides not running setiathome. When this happens and I view the screen the error message starts right from the Login: prompt. I tried to go to another console and tried ctrl-alt-del and nothing worked. End up having to hit the power button
Thanks. How do you have it run? I made a shell script to start seti with all the right settings and stuff (I have a local queue program, so have to point it to that). I then put it in my RC.Local so it will start when the machine boots. I also have what they suggested in the readme in that I have a cron job setup so it trys to run it again once an hour. After another lockup about 3 days after the initial post, I removed that cron entry and see if that caused it. So far I haven't had any problems.
What this does is, sets up a scheduled job to run setiathome every hour, on the 20th minute. I'll probably change this to once every 12 hours in the future. the '-nice 19' option sets the priority level for this process. Processes can run at a priority of 20 to -20, 20 being the lowest priority. So, as you can see 19 is pretty low. If I want something to run lower than SETI, I still can do it by running it at 20, but generally anything else will come first.
Last edited by etherdeath; 02-07-2003 at 05:11 PM.
Well, my setup is a bit different.
I've got a sparc5 running a http server (for local intranet), firewall, print serv, and seti.
Generally, since all the other proceses don't require that much power or extreme timing factors, I can pretty much run seti with a higher priority. Ofcourse I've got mega boxs around so I can designate a whole computer to nothing but seti if I choose to do so.
I don't use any cron jobs. Since sparc5 is always on, I didn't bother with any scripts or anything.
I do have a script idling that monitors running processes and reports back accordingly:
time started, time active, priority, etc. etc.
If a process should crash, it will log as much as possible, mark when process ended, and, if set to do so, will automatically restart the process.
I know that there are other tools built that can do this same thing, and cron basically is supposed to manage such things, but I find that mine is a bit more simplistic for what I need to do.
I'm still relatively new to linux, and I've been trying to find a way to do just what you are doing; logging errors and restarting. Only problem I'm having is when seti crashes, it locks up the whole computer. That's the way I first know about it, when I try to access the web server of files stored on it, and I can't. I removed the cron entry and I just checked the processes and there is no seti process running on it (meaning it crashed). Computer is still up and running, though, which is the important thing. next thing i'll have to try and do and redirect the errors to a log file instead of /dev/null see if that shows anything.
Yep. Start with an output to an actual log file to see what seti will tell you.
Bare in mind that seti isn't the most perfect coded proggie, and it's verbose output isn't the best in the world. But none-the-less it should give you a little bit better understanding of what happend prior to the crash.
Not sure if I saw this before but:
Why type of internet access do you have?
What type of NIC?
And what else do you do on the seti box?
Just trying to get an understanding of what all the box is doing.
Also, a brief hardware run down might help me narrow your problem a bit as well.
But most likely it's a software glitch somewhere.
ok, Don't know the exact model of the motherboard, but it's an AMD 1.333 ghz with 512 mb SDRAM. It has onboard everything (audio, video, LAN). I have a cable connection. it connects to a Linksys cable router along with all the other computers to share internet access. It's main pupose is as a local fileserver. It also has apache and MySQL on it. It's mainly used locally, but it can be accessed from the internet as well.