‘Error!’ MariaDB is not running on your system - database list could not be retrieved.
MariaDB error messageThe full MariaDB error message was : DBI connect failed : Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111) ?
Failed to start database : Redirecting to /bin/systemctl start mariadb.service Job for mariadb.service failed because the control process exited with error code. See “systemctl status mariadb.service” and “journalctl -xe” for details.
there are no systems details, no one can really help until you supply them
That image is not worth a thousand words. What is the output for this command journalctl -xe?
Don’t you watch the IT Crowd? Try a reboot, systems been running 3 days and you haven’t tried a reboot when somethings not working.
my problem start when webmin give me update about week ago and i reboot my system and nothing happen
my MariaDB Database Server is not running and i try hard and give that error
Error! MariaDB is not running on your system - database list could not be retrieved.
MariaDB error message
The full MariaDB error message was : DBI connect failed : Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111) ?
and when i start MariaDB server
give me this error
Fatal Error!
SQL show index from wp_postmeta failed : Lost connection to MySQL server during query
root@xxx ~]# journalctl -xe
Oct 12 13:05:16 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘4.100.70.109.in-addr.arpa/PTR/IN’: 2607:f740:e00a:deec::2#53
Oct 12 13:05:18 xxxx.contaboserver.net sshd[32600]: Failed password for invalid user user from 1.14.47.218 port 36176 ssh2
Oct 12 13:05:18 xxxx.contaboserver.net sshd[32600]: Received disconnect from 1.14.47.218 port 36176:11: Bye Bye [preauth]
Oct 12 13:05:18 xxxx.contaboserver.net sshd[32600]: Disconnected from 1.14.47.218 port 36176 [preauth]
Oct 12 13:05:24 xxxx.contaboserver.net sshd[32631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.88.240
Oct 12 13:05:24 xxxx.contaboserver.net sshd[32631]: pam_succeed_if(sshd:auth): requirement “uid >= 1000” not met by user “root”
Oct 12 13:05:26 xxxx.contaboserver.net sshd[32631]: Failed password for root from 180.101.88.240 port 15834 ssh2
Oct 12 13:05:26 xxxx.contaboserver.net sshd[32631]: pam_succeed_if(sshd:auth): requirement “uid >= 1000” not met by user “root”
Oct 12 13:05:28 xxxx.contaboserver.net sshd[32631]: Failed password for root from 180.101.88.240 port 15834 ssh2
Oct 12 13:05:29 xxxx.contaboserver.net sshd[32631]: pam_succeed_if(sshd:auth): requirement “uid >= 1000” not met by user “root”
Oct 12 13:05:30 xxxx.contaboserver.net sshd[32631]: Failed password for root from 180.101.88.240 port 15834 ssh2
Oct 12 13:05:31 xxxx.contaboserver.net sshd[32631]: Received disconnect from 180.101.88.240 port 15834:11: [preauth]
Oct 12 13:05:31 xxxx.contaboserver.net sshd[32631]: Disconnected from 180.101.88.240 port 15834 [preauth]
Oct 12 13:05:31 xxxx.contaboserver.net sshd[32631]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.88.240 user=ro
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: validating in-addr.arpa/SOA: got insecure response; parent indicates it should be secure
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns1-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5306:8600::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns3-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5306:8600::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns1-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5306:8600::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns3-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5306:8600::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns1-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns1-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns4-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns4-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns3-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns3-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns2-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5306:8600::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns2-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns4-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns3-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns2-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5303:c700::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns3-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns2-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns1-ec2-rdns.amazonaws.com/A/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:32 xxxx.contaboserver.net named[1492]: network unreachable resolving ‘ns1-ec2-rdns.amazonaws.com/AAAA/IN’: 2600:9000:5305:2900::1#53
Oct 12 13:05:34 xxxx.contaboserver.net sshd[32740]: Invalid user public from 143.110.180.164 port 37076
Oct 12 13:05:34 xxxx.contaboserver.net sshd[32740]: input_userauth_request: invalid user public [preauth]
Oct 12 13:05:34 xxxx.contaboserver.net sshd[32740]: pam_unix(sshd:auth): check pass; user unknown
Oct 12 13:05:34 xxxx.contaboserver.net sshd[32740]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=143.110.180.16
Oct 12 13:05:37 xxxx.contaboserver.net sshd[32740]: Failed password for invalid user public from 143.110.180.164 port 37076 ssh2
lines 1288-1326/1326 (END)
I think that is your clue. Some website plugin (wp_ WordPress 
again?) is attempting to re-index or initiate a new index - possibly on a table that doesn’t exist or it doesn’t have permission to) Is this another mod-php issue?
i already i put all sites plugins folder to old plugins and nothing happen
so what’s you mean exactly ?
and how can i fix this problem plz
and what about this
# journalctl -xe
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/AAAA/IN': 2001:7fd::1#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:7fd::1#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/A/IN': 2001:500:9f::42#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:500:9f::42#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/AAAA/IN': 2001:500:9f::42#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:500:9f::42#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/A/IN': 2001:500:a8::e#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:500:a8::e#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/AAAA/IN': 2001:500:a8::e#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/A/IN': 2001:503:c27::2:30#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/AAAA/IN': 2001:503:c27::2:30#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/A/IN': 2001:dc3::35#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/AAAA/IN': 2001:dc3::35#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:500:a8::e#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:503:c27::2:30#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:503:c27::2:30#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:dc3::35#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:dc3::35#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:500:200::b#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:500:200::b#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:503:ba3e::2:30#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:500:12::d0d#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/A/IN': 2001:500:200::b#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/AAAA/IN': 2001:500:12::d0d#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns2.s-host.com.ua/AAAA/IN': 2001:500:200::b#53
Oct 12 15:29:30 xxxx.contaboserver.net named[1492]: network unreachable resolving 'ns3.s-host.com.ua/A/IN': 2001:500:1::53#53
Oct 12 15:30:01 xxxx.contaboserver.net systemd[1]: Started Session 1329 of user root.
-- Subject: Unit session-1329.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-1329.scope has finished starting up.
--
-- The start-up result is done.
Oct 12 15:30:01 xxxx.contaboserver.net CROND[18006]: (root) CMD (/etc/webmin/status/monitor.pl)
Oct 12 15:30:05 xxxx.contaboserver.net postfix/anvil[17590]: statistics: max connection rate 1/60s for (submission:162.240.51.185) at Oct 12 15:26:41
Oct 12 15:30:05 xxxx.contaboserver.net postfix/anvil[17590]: statistics: max connection count 1 for (submission:162.240.51.185) at Oct 12 15:26:41
Oct 12 15:30:05 xxxx.contaboserver.net postfix/anvil[17590]: statistics: max cache size 1 at Oct 12 15:26:41
lines 1174-1212/1212 (END)
It seems to me there are two separate problems here:
A DNS problem - the network is not reachable
and
which could be the failure of some php access to MariaDB that is shutting down MariaDB
is there any solution ?
I have never had a use for Amazon AWS, and I may be just up the wrong tree here,
but that does not seem correct.
I don’t know where it is coming from
‘ns1-ec2-rdns.amazonaws.com/AAAA/IN: 2600:9000:5305:2900::1#53’
makes more sense to me.
systemctl status mariadb
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2023-10-12 15:42:02 CEST; 3h 39min ago
Process: 27101 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 27100 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 27058 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 27100 (code=exited, status=0/SUCCESS)
Oct 12 15:42:00 xxxx.contaboserver.net systemd[1]: Starting MariaDB database server…
Oct 12 15:42:00 xxxx.contaboserver.net mariadb-prepare-db-dir[27058]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Oct 12 15:42:00 xxxx.contaboserver.net mariadb-prepare-db-dir[27058]: If this is not the case, make sure the /var/lib/mysql is empty before runni…b-dir.
Oct 12 15:42:00 xxxx.contaboserver.net mysqld_safe[27100]: 231012 15:42:00 mysqld_safe Logging to ‘/var/log/mariadb/mariadb.log’.
Oct 12 15:42:00 xxxx.contaboserver.net mysqld_safe[27100]: 231012 15:42:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Oct 12 15:42:02 xxxx.contaboserver.net systemd[1]: mariadb.service: control process exited, code=exited status=1
Oct 12 15:42:02 xxxx.contaboserver.net systemd[1]: Failed to start MariaDB database server.
Oct 12 15:42:02 xxxx.contaboserver.net systemd[1]: Unit mariadb.service entered failed state.
Oct 12 15:42:02 xxxx.contaboserver.net systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@vmi490701 ~]#
systemctl enable mariadb
systemctl start mariadb
You may want to poke around in /var/log/mariadb to see what’s there. The logs should provide more clues.
nothing happened
this of some
201231 12:59:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
201231 12:59:34 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 17740 …
201231 12:59:34 InnoDB: The InnoDB memory heap is disabled
201231 12:59:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
201231 12:59:34 InnoDB: Compressed tables use zlib 1.2.7
201231 12:59:34 InnoDB: Using Linux native AIO
201231 12:59:34 InnoDB: Initializing buffer pool, size = 128.0M
201231 12:59:34 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
201231 12:59:34 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait…
201231 12:59:34 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait…
201231 12:59:34 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait…
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
201231 12:59:34 InnoDB: Waiting for the background threads to start
201231 13:03:39 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
201231 13:03:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
201231 13:03:39 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 20204 …
201231 13:03:39 InnoDB: The InnoDB memory heap is disabled
201231 13:03:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
201231 13:03:39 InnoDB: Compressed tables use zlib 1.2.7
201231 13:03:39 InnoDB: Using Linux native AIO
201231 13:03:39 InnoDB: Initializing buffer pool, size = 128.0M
201231 13:03:39 InnoDB: Completed initialization of buffer pool
201231 13:03:39 InnoDB: highest supported file format is Barracuda.
201231 13:03:39 InnoDB: Waiting for the background threads to start
201231 13:03:40 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 1597945
201231 13:03:40 [Note] Plugin ‘FEEDBACK’ is disabled.
201231 13:03:40 [Note] Server socket created on IP: ‘0.0.0.0’.
201231 13:03:40 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MariaDB Server
201231 13:03:44 [Note] /usr/libexec/mysqld: Normal shutdown
201231 13:03:44 InnoDB: Starting shutdown…
201231 13:03:45 InnoDB: Shutdown completed; log sequence number 1597945
201231 13:03:45 [Note] /usr/libexec/mysqld: Shutdown complete