First you need to find where your sessions are stored. Solution: is rather straightforward (and relatively painless, if you can afford it). Symptoms: 'find' and 'fuser' processes are consuming a lot of CPU time and/or memory.

Therefore if you've just upgraded from a lower Plesk version you might notice at times a significant CPU and memory load (provided your sessions directory is clogged up).

This was fixed in Plesk 11 (a proper periodic cleanup task was added). On some systems (I believe, rpm-based only) in Plesk 10 PHP sessions cleanup was not working properly. Restarting the affected services alone, however, will not fix the problem. # /etc/init.d/ntpd stop date -s '`date`' /etc/init.d/ntpd restartĪlternatively you could just restart the machine. Running this should suffice (you don't need to restart other services after that): You just need to remove leap second flag from the system. Symptoms: CPU usage of your Java applications or MySQL server (other applications might be susceptible as well) have grown significantly lately.

Other applications started to misbehave, e.g.

disturbance on a number of Linux systems. Therefore think first and use at your own risk later.Ī day or so ago a leap second was introduced. I decided to post a couple of common reasons and solutions here (this was written with Plesk 11 for Linux in mind, but may be applicable to other versions and products as well, YMMV however).ĭISCLAIMER: this information is provided as is and without warranty of any kind (including promise of usefulness or not being harmful). Naturally, this can be caused by a multitude of reasons and usually requires investigation. OK, lately I saw a couple of threads on this forum reporting problems with high CPU and/or memory usage.

Cpu and memory utilization in linux