After Upgrade 1.34.20 mysql server has error

Forum for questions and support relating to the 1.34.x releases only.
Post Reply
factor200x
Posts: 18
Joined: Fri Apr 06, 2018 6:35 am

After Upgrade 1.34.20 mysql server has error

Post by factor200x »

Good morning,

after installing version 1.34.20 on Friday, the mySQL server can no longer be started.

I have no idea what happened there and how to get it running again. Can anyone help me?

Thanks
Olaf

Code: Select all

DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
06.09.2020 10:54:04.612568 zmupdate[1857].ERR [ZoneMinder::Database:113] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
06.09.2020 10:54:04.612841 zmupdate[1857].ERR [ZoneMinder::Database:113] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
06.09.2020 10:54:04.613357 zmupdate[1857].ERR [ZoneMinder::Database:113] [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96.
BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 147.
Compilation failed in require at /usr/bin/zmupdate.pl line 73.
BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 73.
root@S2018Z620N001:~# systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.23 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-09-06 10:52:36 CEST; 1min 39s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 1627 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
  Process: 1629 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 1631 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=
  Process: 1745 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
 Main PID: 1745 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"

Sep 06 10:52:27 S2018Z620N001 systemd[1]: Starting MariaDB 10.3.23 database server...
Sep 06 10:52:28 S2018Z620N001 mysqld[1745]: 2020-09-06 10:52:28 0 [Note] /usr/sbin/mysqld (mysqld 10.3.23-MariaDB-0+deb10u1) starting as process 1745 ...
Sep 06 10:52:36 S2018Z620N001 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Sep 06 10:52:36 S2018Z620N001 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Sep 06 10:52:36 S2018Z620N001 systemd[1]: Failed to start MariaDB 10.3.23 database server.
Magic919
Posts: 1381
Joined: Wed Sep 18, 2013 6:56 am

Re: After Upgrade 1.34.20 mysql server has error

Post by Magic919 »

Start the db by hand and look for errors. This may help https://mariadb.com/kb/en/what-to-do-if ... snt-start/
-
factor200x
Posts: 18
Joined: Fri Apr 06, 2018 6:35 am

Re: After Upgrade 1.34.20 mysql server has error

Post by factor200x »

I have already tried but with the same success or failure.

Unfortunately the URL is incorrect. Could you correct it? Thanks a lot!
factor200x
Posts: 18
Joined: Fri Apr 06, 2018 6:35 am

[solved] Re: After Upgrade 1.34.20 mysql server has error

Post by factor200x »

OK, I found the problem! The system partition is full and for this reason the DB could not be started.

But thanks for the support!!!!

Have a nice Sunday
Olaf
Post Reply