Answer the question
In order to leave comments, you need to log in
The server, as scheduled at 10 Moscow time and 22 Moscow time, crashes with LA>50. Where to dig?
No ideas, no traffic during these periods, crontab looked. The rest of the time it works perfect. I just don't understand what's going on, can someone tell me what?
Answer the question
In order to leave comments, you need to log in
50+ LA is the average temperature in the hospital. I have one of the carcasses under combat load worth 1300 la and joyfully answers everyone.
But if your wa is more than 5-10%, dig in the direction of slowing down disks or networks. Well, another IO, if it is there.
/var/spool/cron/crontabs/* also look if you are sinning on cron.
And what's in the logs? Clean reboot or something really crashed?
If it's still not clear, then you can try to put all the processes manually right before the X hour and see if the clean system reboots by itself.
And it looks like some kind of maintenance script.
With these 50+, the web server does not respond at all and the console even slows down. This is how many processors you have, then 1300 is ok?
I'm guessing it has something to do with backup. Purely theoretical.
Start with /etc/cron.d
or where do you have crons?
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question