• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved MariaDB Update to 10.11.7 via Plesk 18.0.60 on Debian 10

TimReeves

Regular Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
18.0.60.0
I thought oh good, updated panel.ini and opened ssh and repair as instructed, and started the upgrade.
It went through OK, but now I have this situation:
I manually start MariaDB, works fine.
About a good two minutes later it gets shut down from outside - cause unknown.
Here are the journal log entries:

Apr 12 15:09:25 mail.reeves.one systemd[1]: Starting MariaDB 10.11.7 database server...
Apr 12 15:09:25 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:25 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~deb10 source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 28226
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Number of transaction pools: 1
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Using Linux native AIO
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Completed initialization of buffer pool
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: End of log at LSN=288450121100
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Resizing redo log from 128.000MiB to 96.000MiB; LSN=288450121100
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: 128 rollback segments are active.
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: log sequence number 288450121100; transaction id 247269759
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] Plugin 'FEEDBACK' is disabled.
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] Server socket created on IP: '127.0.0.1'.
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] /usr/sbin/mariadbd: ready for connections.
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: Version: '10.11.7-MariaDB-1:10.11.7+maria~deb10' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
Apr 12 15:09:26 mail.reeves.one systemd[1]: Started MariaDB 10.11.7 database server.
Apr 12 15:09:26 mail.reeves.one /etc/mysql/debian-start[28246]: /usr/bin/mariadb-upgrade: the '--basedir' option is always ignored
Apr 12 15:09:26 mail.reeves.one mariadbd[28226]: 2024-04-12 15:09:26 0 [Note] InnoDB: Buffer pool(s) load completed at 240412 15:09:26

Apr 12 15:11:47 mail.reeves.one systemd[1]: Stopping MariaDB 10.11.7 database server...
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: FTS optimize thread exiting.
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: Starting shutdown...
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: Restricted to 2016 pages due to innodb_buf_pool_dump_pct=25
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: Buffer pool(s) dump completed at 240412 15:11:47
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] InnoDB: Shutdown completed; log sequence number 288450219998; transaction id 247269855
Apr 12 15:11:47 mail.reeves.one mariadbd[28226]: 2024-04-12 15:11:47 0 [Note] /usr/sbin/mariadbd: Shutdown complete
Apr 12 15:11:47 mail.reeves.one systemd[1]: mariadb.service: Succeeded.
Apr 12 15:11:47 mail.reeves.one systemd[1]: Stopped MariaDB 10.11.7 database server.

During the approx. 2 minutes and 20 seconds of uptime I can work normally on my websites.

What can be signalling the DB to shut down?

My server is without DB effectively down - urgent help appreciated!

Tim
 
I've resolved the problem: An outdated monit script for mysql was looking for a file /etc/init.d/mysql
Just remove that test from the monit mysql config and all is well.
 
Back
Top