I am not sure of what your problem actually is & how you determined it is what you say. If you are finding nothing in the logs what has led you to the conclusions you made in your first post ?
I would suggest looking in the messages log file, you can look at this is the server manager View Log files panel.
You would look around & before the time these issues occur.
Also something stopping in Linux is typically a sign of a busy (overloaded) system, & Linux will queue the tasks till later when system resources become available.
It can appear as if something has stopped or crashed (aka Windows) but Linux is just slowly processing all requests & queueing those it cannot action at the time eg due to not enough memory ( RAM) or whatever.
You should look at running processes & see what is using up system CPU & system memory & swap memory.
Use
top -i
&/or
htop
or try something like
ps -aux
at command prompt.
Also you can open a console comnand prompt & monitor activity using the tail command. I am not sure off the top of my head what to monitor but someone else here may jump in & suggest something. Search these forums on tail & you may get some clues.
Starting point is to run htop or similar in an instance of the console while the problem is occuring, note what processes are using CPU & how much percentage & note how much memory each process is using, & also check amount of available & swap memory.
You should always have a lot of swap memory available, if it is low you will have problems.
More feedback from you about your system specs is needed.
3 Replies
1460 Views