1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

No memory available / Mysql crash

Discussion in 'Plesk for Linux - 8.x and Older' started by j Zim, Aug 13, 2009.

  1. j Zim

    j Zim Guest

    Yesterday I got a problem (dozen of entries like wwwrun 30399 0.0 0.3 89720 8252 ? Sl Nov09 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL) on my server (Dell, Suse OES 10.2).

    At the same time and suddenly the memory usage + swap was very high and no memory was available anymore.

    I restarted the apache server (rcapache restart) to get everything working ok. Unfortunately for me I did not find the source of the problem.

    On Suse with Plesk (8.6), Mysql seems to be a very important component and as soon as mysql is not available everything is going down (monitoring http accesses, antispam, email, etc.). When memory level becomes very low, mysql was stopped and cannot be restarted.

    What is the most possible situation: the problem (httpd entries and memory) is be caused by the crash of mysql or mysql is crashing because of the memory problem? I tried with no success to isolate the problem.

    By the way, does someone know a method to log mysql activities in order to get info about its crash?

  2. Nataliya Zagr

    Nataliya Zagr Regular Pleskian

    Apr 14, 2009
    Likes Received:

    The mysqld.log file is located at the following directory:

    # less /var/log/mysqld.log

    It can be commented at the mysql configuration file, thus please, check, and enable it if necessary. Find the following string at the /etc/my.cnf:


    Also check the apache log file for error messages:

    # less /var/log/httpd/error_log

    Thank you