mandrake 10.2 system crashing @4:10 am on Sundays.
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
mandrake 10.2 system crashing @4:10 am on Sundays.
My Linux 10.2 Mandrake system is crashing every Sunday around 4:05-4:10 am. Not sure why as the logs are not complaining about any issues that I can see. Here is my syslog where it dies. Not sure what the ^@ symbols are but...
This is all, I got. There are some scripts that run about the time it seems to crash. Here are the scripts that run around the time of the crash.
makewhatis.cron*
makewhatis-en.cron*
slocate.cron
I am running a full tape system backup as well at 03:00 am. System doesnt seem bogged down nor do I get any fatal errors. Note that I have to restart the server as nothing is responding. ANybody know of any issues with tar and these weekly cron jobs? I am getting a bit worried that my linux box may have picked up a worm or something? ANy ideas?
Thanks.. The backup is still running when the scheduled cron jobs are running. I don't know why all of a sudden the Tar
backup would cause this..Other then the possibility that the slocate.sh job is running. I think this deletes the entire LOCATE database and
recreates it. The tar backup job might not like the fact that other processes are running?
I did stop the tar backup to run so it will be a good test to see what happens. I also had a corrupted
filesystem. I fixed the errors so that may have had something to do with it. Its just that nothing is getting logged in the kernel logs or syslog that
would tell me whats going on? is there any utility I can run to trace the I/O and see what is going on during the 04:00 am timeframe this happens?
I shall wait and see..
The tar backup job might not like the fact that other processes are running?
Possibly - especially if its the slocate update process since that involves a lot of disk I/O at the same time your tar backup wants to pull through a lot of disk I/O. Still the system shouldn't crash - maybe just get really slow.
Quote:
I fixed the errors so that may have had something to do with 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.
