This looks like it started successfully.
And this looks like it was shutdown normally. i.e. somebody or something stopped it.
I don’t know! We’re still trying to figure it out.
I mean, it is stopped right now. We see the last message in the log is that is shut down. But, it appears is was told to shut down (by someone or something). Not that anything was wrong with it. So, when it is not running, we expect Webmin to show it as not running.
That’s what it looks like based on the log. I don’t know if that’s the whole story.
@MGC You are looking for errors in the log file.
grep -i ERROR /var/log/mariadb/mariadb.log
Is there a solution to this problem?
i check it and no luck
Back to the website again!
Something in php is messing with MariaDB (possibly during creation of those InnoDB indexes/tables) that is causing it to shutdown. has the website been built with an old version of php and the updates talked about at the start introduced a new php version
perhaps we should be trying to find what actually was updated/upgraded especially if it wasn’t Webmin/Virtualmin.
At this point,
grep -ir mariadb /var/log/*
might be worth a shot then? That should pick up other logs that might show something?
]# grep -ir mariadb /var/log/*
/var/log/anaconda/packaging.log:11:24:24,178 DEBUG yum.verbose.YumBase: TSINFO: Marking 1:mariadb-libs-5.5.68-1.el7.x86_64 as install for 2:postfix-2.10.1-9.el7.x86_64
/var/log/anaconda/packaging.log:11:24:27,205 DEBUG yum.verbose.YumBase: TSINFO: Marking 1:mariadb-libs-5.5.68-1.el7.x86_64 as install for 2:postfix-2.10.1-9.el7.x86_64
/var/log/anaconda/packaging.log:11:29:54,490 DEBUG yum.verbose.YumBase: TSINFO: Marking 1:mariadb-libs-5.5.68-1.el7.x86_64 as install for 2:postfix-2.10.1-9.el7.x86_64
/var/log/anaconda/packaging.log:11:35:18,854 INFO packaging: 1:mariadb-libs-5.5.68-1.el7.x86_64 (175/327)
/var/log/anaconda/journal.log:Dec 31 11:24:24 xxx.contaboserver.net yum[1547]: TSINFO: Marking 1:mariadb-libs-5.5.68-1.el7.x86_64 as install for 2:postfix-2.10.1-9.el7.x86_64
/var/log/anaconda/journal.log:Dec 31 11:24:27 xxx.contaboserver.net yum[1547]: TSINFO: Marking 1:mariadb-libs-5.5.68-1.el7.x86_64 as install for 2:postfix-2.10.1-9.el7.x86_64
/var/log/anaconda/journal.log:Dec 31 11:29:54 xxx.contaboserver.net yum[1547]: TSINFO: Marking 1:mariadb-libs-5.5.68-1.el7.x86_64 as install for 2:postfix-2.10.1-9.el7.x86_64
/var/log/anaconda/journal.log:Dec 31 11:29:56 xxx.contaboserver.net packaging[1547]: Member: mariadb-libs.x86_64 1:5.5.68-1.el7 - u
/var/log/anaconda/journal.log:Dec 31 11:29:56 xxx.contaboserver.net packaging[1547]: Adding Package 1:mariadb-libs-5.5.68-1.el7.x86_64 in mode u
/var/log/anaconda/journal.log:Dec 31 11:31:26 xxx.contaboserver.net packaging[1547]: Installing mariadb-libs (175/327)
/var/log/anaconda/journal.log:Dec 31 11:33:32 xxx.contaboserver.net dracut[16354]: -rw-r–r-- 1 root root 17 Oct 1 16:55 etc/ld.so.conf.d/mariadb-x86_64.conf
/var/log/anaconda/journal.log:Dec 31 11:34:22 xxx.contaboserver.net dracut[26769]: -rw-r–r-- 1 root root 17 Oct 1 16:55 etc/ld.so.conf.d/mariadb-x86_64.conf
/var/log/anaconda/journal.log:Dec 31 11:35:00 xxx.contaboserver.net dracut[8962]: -rw-r–r-- 1 root root 17 Oct 1 16:55 etc/ld.so.conf.d/mariadb-x86_64.conf
/var/log/anaconda/journal.log:Dec 31 11:35:18 xxx.contaboserver.net packaging[1547]: 1:mariadb-libs-5.5.68-1.el7.x86_64 (175/327)
/var/log/anaconda/journal.log:Dec 31 11:35:59 xxx dracut[19890]: -rw-r–r-- 1 root root 17 Oct 1 18:55 etc/ld.so.conf.d/mariadb-x86_64.conf
/var/log/audit/audit.log.2:type=SERVICE_START msg=audit(1697221077.332:357540): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
/var/log/audit/audit.log.2:type=SERVICE_STOP msg=audit(1697221084.532:357541): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
/var/log/audit/audit.log.2:type=SERVICE_START msg=audit(1697224707.815:359695): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
/var/log/audit/audit.log.2:type=SERVICE_START msg=audit(1697224720.777:359696): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
/var/log/audit/audit.log.2:type=SERVICE_START msg=audit(1697225090.126:359866): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
/var/log/audit/audit.log.2:type=SERVICE_START msg=audit(1697230829.550:363698): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
/var/log/audit/audit.log.3:type=SERVICE_START msg=audit(1697187842.529:334155): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
/var/log/audit/audit.log.3:type=SERVICE_STOP msg=audit(1697187853.358:334173): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
/var/log/audit/audit.log.3:type=SERVICE_START msg=audit(1697187884.578:334189): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=mariadb comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
/var/log/boot.log-20230811: Starting MariaDB database server…
/var/log/boot.log-20230821: Starting MariaDB database server…
/var/log/boot.log-20230825: Starting MariaDB database server…
/var/log/boot.log-20231004: Starting MariaDB database server…
/var/log/boot.log-20231006: Starting MariaDB database server…
/var/log/boot.log-20231006: Starting MariaDB database server…
/var/log/boot.log-20231008: Starting MariaDB database server…
/var/log/boot.log-20231009: Starting MariaDB database server…
/var/log/mariadb/mariadb.log:InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
/var/log/mariadb/mariadb.log:Server version: 5.5.68-MariaDB
/var/log/mariadb/mariadb.log:210201 22:57:56 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1263 ...
/var/log/mariadb/mariadb.log:210201 22:58:17 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 2250248552
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:210216 10:35:32 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
/var/log/mariadb/mariadb.log:210216 9:36:32 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1687 ...
/var/log/mariadb/mariadb.log:210216 10:36:36 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 15553045141
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:210216 10:39:00 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
/var/log/mariadb/mariadb.log:210216 9:39:35 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1437 ...
/var/log/mariadb/mariadb.log:210216 9:39:37 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 15553045253
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:210216 9:47:32 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1439 ...
/var/log/mariadb/mariadb.log:210216 9:47:33 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 15553045253
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:210216 16:53:12 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1313 ...
/var/log/mariadb/mariadb.log:210216 16:53:18 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 15553045253
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:210227 18:29:11 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1372 ...
/var/log/mariadb/mariadb.log:210227 18:29:52 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 25784862306
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:Last time write locked in file /builddir/build/BUILD/mariadb-5.5.68/storage/xtradb/dict/dict0dict.c line 314
/var/log/mariadb/mariadb.log:210324 17:53:49 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1502 ...
/var/log/mariadb/mariadb.log:210324 17:54:05 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 39229240570
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
/var/log/mariadb/mariadb.log:Server version: 5.5.68-MariaDB
/var/log/mariadb/mariadb.log:231003 20:18:01 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 4905 ...
/var/log/mariadb/mariadb.log:InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
/var/log/mariadb/mariadb.log:Server version: 5.5.68-MariaDB
/var/log/mariadb/mariadb.log:231003 20:18:04 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
/var/log/mariadb/mariadb.log:231003 18:28:18 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 1568 ...
/var/log/mariadb/mariadb.log:231003 18:28:21 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 945269379307
/var/log/mariadb/mariadb.log:InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
/var/log/mariadb/mariadb.log:Server version: 5.5.68-MariaDB
/var/log/mariadb/mariadb.log:Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
/var/log/mariadb/mariadb.log:231003 18:28:21 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 2467 ...
/var/log/mariadb/mariadb.log:InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
s:Oct 8 17:39:43 vmi490701 systemd: Starting MariaDB database server...
/var/log/messages:Oct 8 17:39:43 xxxx mariadb-prepare-db-dir: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
/var/log/messages:Oct 8 17:39:43 xxxx mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
/var/log/messages:Oct 8 17:39:43 xxxx mysqld_safe: 231008 17:39:43 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
/var/log/messages:Oct 8 17:39:50 xxxx systemd: Started MariaDB database server.
/var/log/messages:Oct 8 21:38:52 xxxx systemd: Starting MariaDB database server...
/var/log/messages:Oct 8 21:38:52 xxxx mariadb-prepare-db-dir: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
/var/log/messages:Oct 8 21:38:52 xxxx mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepa
/var/log/messages-20231008:Oct 3 18:28:18 xxxx mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
/var/log/messages-20231008:Oct 3 18:28:18 xxxx mysqld_safe: 231003 18:28:18 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
/var/log/messages-20231008:Oct 3 20:28:22 xxxx systemd: mariadb.service: control process exited, code=exited status=1
/var/log/messages-20231008:Oct 3 20:28:22 xxxx systemd: Failed to start MariaDB database server.
/var/log/messages-20231008:Oct 3 20:28:22 xxxx systemd: Unit mariadb.service entered failed state.
/var/log/messages-20231008:Oct 3 20:28:22 xxxx systemd: mariadb.service failed.
/var/log/messages-20231008:Oct 4 17:14:39 xxxx systemd: Starting MariaDB database server...
/var/log/messages-20231008:Oct 4 17:14:39 xxxx mariadb-prepare-db-dir: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
/var/log/messages-20231008:Oct 8 00:07:16 xxxx mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
/var/log/messages-20231008:Oct 8 00:07:16 xxxx mysqld_safe: 231008 00:07:16 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
/var/log/messages-20231008:Oct 8 00:07:17 xxxx systemd: mariadb.service: control process exited, code=exited status=1
/var/log/messages-20231008:Oct 8 00:07:17 xxxx systemd: Failed to start MariaDB database server.
/var/log/messages-20231008:Oct 8 00:07:17 xxxx systemd: Unit mariadb.service entered failed state.
/var/log/messages-20231008:Oct 8 00:07:17 xxxx systemd: mariadb.service failed.
/var/log/yum.log-20210101:Dec 31 12:57:30 Installed: 1:mariadb-5.5.68-1.el7.x86_64
/var/log/yum.log-20210101:Dec 31 12:58:08 Installed: 1:mariadb-devel-5.5.68-1.el7.x86_64
/var/log/yum.log-20210101:Dec 31 12:58:11 Installed: 1:mariadb-server-5.5.68-1.el7.x86_64
Nothing jumps out which is disturbing. Looks like mariadb was not updated recently though.
Go to the source?
EDIT: Disappointing. Looks like they don’t want to be bothered with this and pass it off to:
MariaDB version 5.5.68
i don’t any idea about this stuff
and what should i do ?
As you can see I’m currently running v10.3.38 so that gives you some idea of how out-of-date 5.5.68 is. A major version change usually means something serious is broken. So if the website code worked under 5.5.68 i would expect problems.
What about your PHP version is that old too? → I would expect at least v7 or v8.
I am still under the belief that the real fault lies in the website code not in the MariaDB. It is just being asked to do something it is no longer equipped to do.
You probably don’t know the answer to this question - but I’ll ask it anyway - as it is signalling InnoDB tables. The InnoDB design can use separate table files or one big file. the latter have a tendency to get very big and are easy to corrupt if locking is not carefully managed. Individual files can cause other problems and a bit like a shot gun. So the question is which is being used by the website?
hang on in there util the source of the problem is identified. don’t do anything rash.
1 Like
my PHP version 7
and MariaDB version 5.5.68
PHP 7 is fine though getting a little old not a problem as long as the website code has been written for at least PHP 7. → there is an amazing how much garbage remain on t’internet written in older code. let’s assume that the old server (the one on which the website was working) was also running PHP 7. Therefore it was not a PHP upgrade from an earlier version that broke the system.
I’m no longer a PHP programmer and even my MariaDB/MySQL knowledge has long gone the way of many of my brain cells. I’m more of a NodeJS und MongoDB these days. Perhaps someone else can help with the rather obvious “can MariaDB be easily downgraded to an earlier version.”? And probably just as important “can Virtualmin cope with that”?
My thinking here is to get back to the original server in every respect - then take each upgrade one step at a time.
The domain user doesn’t have permission to stop the database. It can’t be anything related to PHP code.
Virtualmin doesn’t care. Has nothing to do with any of this. It doesn’t store anything in Mariadb.
But, I still don’t think anything is wrong with Mariadb. I see logs showing it starts successfully, and then a couple/few minutes later, it shuts down.
You should try starting Mariadb in safe mode (probably covers in the link I provided earlier), just to make sure you can actually interact with data locally. I still think nothing is wrong with Mariadb. I think you have something else going on that’s shutting down the service. I don’t know why or what, but everything I see in the logs you’ve posted looks like a Mariadb server behaving normally.