Ubuntu 18.04 -> 20.04 Update Probleme mit MySQL

[hahni]

Hallo zusammen,

ich wollte (bzw. habe) einen Server von Ubuntu 18.04 auf 20.04 hoch gezogen. Der wurde damals seit 16.04 immer weiter gepflegt und hat noch immer MySQL installiert (anstelle der neuen Perfect-Server-Anleitungen mit MariaDB). Das lief ja auch alles wunderbar, bis zum heutigen Update.

Irgendetwas scheint da nicht zu stimmen, denn der Dienst will einfach nicht starten

--
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
--

Den Rest der Perfect-Server-Anleitung bin ich schon einmal durchgegangen. Es fehlen mir noch die Teile, die natürlich auf MySQL zugreifen wollen. ISPConfig 3.2 würde auch schon laufen, denn das hatte ich schon vorher installiert.

Woran könnte es liegen, dass mein MySQL-Server verrückt spielt? Zu der Fehlermeldung finde ich zwar vieles bei Google, aber nichts, was mir helfen würde. Ich bin mir nicht sicher, ob nicht doch noch ein Dienst oder die alte Version läuft:

--
ps ax | grep mysql
35439 ? Ssl 0:03 /usr/sbin/mysqld
35552 pts/1 S+ 0:00 grep --color=auto mysql
--

Da derzeit der Server sozusagen nicht läuft, wäre ich für jeden Tipp dankbar !

LG von

Hahni

 

[hahni]

Leider geht auch folgender Befehl nicht:

--
mysql_secure_installation

Securing the MySQL server deployment.

Enter password for user root:
Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
--

--
systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; generated)
Drop-In: /etc/systemd/system/mysql.service.d
└─limits.conf
Active: failed (Result: exit-code) since Sat 2020-10-24 09:54:12 CEST; 1min 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 3899 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

Okt 24 09:53:41 server systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Okt 24 09:53:42 server mysql[3899]: * Starting MySQL database server mysqld
Okt 24 09:53:42 server su[3936]: (to mysql) root on none
Okt 24 09:53:42 server su[3936]: pam_unix(su-l:session): session opened for user mysql by (uid=0)
Okt 24 09:53:42 server su[3936]: pam_unix(su-l:session): session closed for user mysql
Okt 24 09:54:12 server mysql[3899]: ...fail!
Okt 24 09:54:12 server systemd[1]: mysql.service: Control process exited, code=exited, status=1/FAILURE
Okt 24 09:54:12 server systemd[1]: mysql.service: Failed with result 'exit-code'.
Okt 24 09:54:12 server systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.

--

 

[hahni]

ps ax | grep mysql
3951 ? S 0:00 /bin/sh /usr/bin/mysqld_safe
4529 ? Sl 0:11 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --log-error=/var/log/mysql/error.log --open-files-limit=256 --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --log-syslog=1 --log-syslog-facility=daemon --log-syslog-tag=
5297 ? S 0:00 /bin/sh /usr/bin/mysqld_safe
5876 ? Sl 0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --log-error=/var/log/mysql/error.log --open-files-limit=256 --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --log-syslog=1 --log-syslog-facility=daemon --log-syslog-tag=
6259 pts/0 S+ 0:00 grep --color=auto mysql

 

[hahni]

Und im Error-Log kann ich folgendes finden:

--
tail -f /var/log/mysql/error.log
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2020-10-24T12:15:11.769167Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2020-10-24T12:15:11.769946Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 7203
2020-10-24T12:15:11.800783Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-24T12:17:22.229369Z 1 [Warning] [MY-012152] [InnoDB] Open files 1286 exceeds the limit 1280
2020-10-24T12:17:22.672799Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-24T12:17:23.532054Z 1 [Warning] [MY-012111] [InnoDB] Trying to access missing tablespace 713
2020-10-24T12:17:23.532591Z 1 [ERROR] [MY-011083] [Server] Error in updating version number in ratisbona/pages tablespace.
2020-10-24T12:17:23.533082Z 1 [Warning] [MY-012111] [InnoDB] Trying to access missing tablespace 713
2020-10-24T12:17:23.533588Z 1 [ERROR] [MY-011001] [Server] Error in storing SDI for ratisbona/pages tablespace.
2020-10-24T12:17:23.610103Z 1 [Warning] [MY-012111] [InnoDB] Trying to access missing tablespace 714
2020-10-24T12:17:23.610795Z 1 [ERROR] [MY-011083] [Server] Error in updating version number in ratisbona/pages_language_overlay tablespace.
2020-10-24T12:17:23.611424Z 1 [Warning] [MY-012111] [InnoDB] Trying to access missing tablespace 714
2020-10-24T12:17:23.612049Z 1 [ERROR] [MY-011001] [Server] Error in storing SDI for ratisbona/pages_language_overlay tablespace.
12:19:54 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x5605b7a3fbc0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f4f77f37d20 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5605b29b1261]
/usr/sbin/mysqld(handle_fatal_signal+0x31b) [0x5605b187305b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7f4f93e243c0]
/usr/sbin/mysqld(dd::sdi::store(THD*, dd::Table const*)+0xd0) [0x5605b2981180]
/usr/sbin/mysqld(dd::upgrade_57::add_sdi_info(THD*)+0xb00) [0x5605b2975d70]
/usr/sbin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0xe9a) [0x5605b297a3ea]
/usr/sbin/mysqld(+0x119aec8) [0x5605b1934ec8]
/usr/sbin/mysqld(+0x27b911a) [0x5605b2f5311a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7f4f93e18609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f4f93563293]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

--