• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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