• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

mysql restarts

D

denhams

Guest
Hi,

I'm running Plesk 7.5.4 (Linux). I've noticed that every now and again (3 or 4 times a day?) mysql restarts. The message in the mysqld.log file is below.

I can see no reason for this. I've run mysql on other (non-Plesk) servers and it has always run 24x7 without restarting.

I've already reinstalled the server once and have not changed my.cnf. Everything (including the databases) seems to work ok.

Any ideas what might be happening?

Regards,

Stephen.



Number of processes running now: 0
060313 07:17:59 mysqld restarted
060313 7:18:03 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
060313 7:18:14 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 638632
InnoDB: Doing recovery: scanned up to log sequence number 0 638632
060313 7:18:17 InnoDB: Flushing modified pages from the buffer pool...
060313 7:18:19 InnoDB: Started
/usr/libexec/mysqld: ready for connections
 
Are you running watchdog? If so then dump it, alot of other people have said it restarts services for no apparent reason.
 
Well, I wasn't running the watchdog but installed it later as I thought it might help!

In the end I upgraded mysql to version 4 (from 3) and the problem seems to have gone away (so far!).

I've still no idea what was causing version 3 to restart.

Regards,

Stephen.
 
Back
Top