• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Services stop and start every once in a while - MySQL Crash

B

BiznetAdmin

Guest
I constantly keep getting emails that some services are being stopped and about five minutes later are started. These services include MySQL, Plesk Web Server (not the Apache Web Server), Spamassasin and IMAP/POP3. I haven't noticed anything strange in the log files, so I cannot figure out why these services restart by themselves.

I know that I am not providing any usefull information, but since I am new to Plesk I do not know what information might be of use. If you can point me to the right direction, I can provide any necessary information.

Furthermore, sometimes when MySQL stops it fails to start again thus making all my websites inaccessible. Besides that, starting MySQL manually seems to have no effect as it never gets started. A part of the log when MySQL crashes can be seen below:
Number of processes running now: 0
110611 04:56:06 mysqld restarted
110611 4:56:07 [Warning] option 'innodb_additional_mem_pool_size': signed value 512000 adjusted to 524288
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110611 4:56:10 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
110611 4:56:18 InnoDB: Started; log sequence number 1 1276663755
110611 4:56:19 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.90' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution

Number of processes running now: 0
110611 05:00:17 mysqld restarted
110611 5:00:18 [Warning] option 'innodb_additional_mem_pool_size': signed value 512000 adjusted to 524288
InnoDB: Log scan progressed past the checkpoint lsn 1 1282927565
110611 5:00:19 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
[*** MySQL crashed - All my websites were not accessible after this time ***]
110611 5:00:32InnoDB: Warning: difficult to find free blocks from
InnoDB: the buffer pool (31 search iterations)! Consider
InnoDB: increasing the buffer pool size.
InnoDB: It is also possible that in your Unix version
InnoDB: fsync is very slow, or completely frozen inside
InnoDB: the OS kernel. Then upgrading to a newer version
InnoDB: of your operating system may help. Look at the
InnoDB: number of fsyncs in diagnostic info below.
InnoDB: Pending flushes (fsync) log: 0; buffer pool: 0
InnoDB: 129 OS file reads, 0 OS file writes, 0 OS fsyncs
InnoDB: Starting InnoDB Monitor to print further
InnoDB: diagnostics to the standard output.

I am using Plesk 9.5.2 installed on CentOS 5.5.

Thanks in advance.
 
Thank you for the link. I will take a look at it and hope to help me solve my server's problems.

The server seems to have a high CPU usage (not sure how high it is) during the daily backup process. That would partially explain why services fail, but there are times when these failures happen when no other intense process (such as backup) runs. A server upgrade would solve these problems? I would also like to mention that Plesk is hosted on a virtual server and not an actual one.
 
It is hard to know now, but yes, a backup could be an issue, if raise the load of the server.
You can try to run the backup with a low priority.
 
Back
Top