ChristianKnorr
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
Hallo zusammen, kann mir jemand sagen warum MySQL nicht mehr geht? Hier das /var/log/mysql/error.log nach dem Startversuch:
2019-04-03T19:56:43.339342Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2019-04-03T19:56:43.339421Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2019-04-03T19:56:43.506461Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-03T19:56:43.508428Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.25-0ubuntu0.16.04.2) starting as process 9996 ...
2019-04-03T19:56:43.514599Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-03T19:56:43.514672Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-03T19:56:43.514686Z 0 [Note] InnoDB: Uses event mutexes
2019-04-03T19:56:43.514697Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-03T19:56:43.514712Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-04-03T19:56:43.514722Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-03T19:56:43.515092Z 0 [Note] InnoDB: Number of pools: 1
2019-04-03T19:56:43.515504Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-03T19:56:43.517470Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-03T19:56:43.529648Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-03T19:56:43.532213Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-03T19:56:43.544636Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-04-03T19:56:43.544966Z 0 [ERROR] InnoDB: Invalid redo log header checksum.
2019-04-03T19:56:43.545254Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-04-03T19:56:44.146414Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-04-03T19:56:44.146500Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-04-03T19:56:44.146520Z 0 [ERROR] Failed to initialize builtin plugins.
2019-04-03T19:56:44.146533Z 0 [ERROR] Aborting
2019-04-03T19:56:44.146562Z 0 [Note] Binlog end
2019-04-03T19:56:44.147298Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
Oo, hier noch was in /var/log/syslog gefunden:
Apr 3 22:12:28 server systemd[1]: Failed to start MySQL Community Server.
Apr 3 22:12:28 server systemd[1]: mysql.service: Unit entered failed state.
Apr 3 22:12:28 server systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 3 22:12:29 server systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Apr 3 22:12:29 server systemd[1]: Stopped MySQL Community Server.
Apr 3 22:12:29 server systemd[1]: Starting MySQL Community Server...
Apr 3 22:12:29 server kernel: [ 2754.154854] audit: type=1400 audit(1554322349.077:300): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/13351/status" pid=13351 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=124 ouid=124
Apr 3 22:12:29 server kernel: [ 2754.155249] audit: type=1400 audit(1554322349.081:301): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=13351 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=124 ouid=0
Apr 3 22:12:29 server kernel: [ 2754.155320] audit: type=1400 audit(1554322349.081:302): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/13351/status" pid=13351 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=124 ouid=124
Apr 3 22:12:29 server systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
|
dajohb
Anmeldungsdatum: 29. Januar 2016
Beiträge: 166
|
filesystem voll?
mach mal
|
dajohb
Anmeldungsdatum: 29. Januar 2016
Beiträge: 166
|
Apr 3 22:12:29 server kernel: [ 2754.154854] audit: type=1400 audit(1554322349.077:300): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/13351/status" pid=13351 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=124 ouid=124
Apr 3 22:12:29 server kernel: [ 2754.155249] audit: type=1400 audit(1554322349.081:301): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=13351 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=124 ouid=0
Apr 3 22:12:29 server kernel: [ 2754.155320] audit: type=1400 audit(1554322349.081:302): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/13351/status" pid=13351 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=124 ouid=124
Apr 3 22:12:29 server systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Apparmor blockiert es.
Wenn kein Apparmor brauchst, dann stoppe es und disable es.
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
dajohb schrieb: filesystem voll?
mach mal
Nein:
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
udev 7,4G 0 7,4G 0% /dev
tmpfs 1,5G 9,6M 1,5G 1% /run
/dev/sda1 373G 93G 280G 25% /
tmpfs 7,4G 0 7,4G 0% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 7,4G 0 7,4G 0% /sys/fs/cgroup
bigdata/home 1,4T 165G 1,3T 12% /srv/home
bigdata/video 2,3T 1,1T 1,3T 45% /srv/video_old
bigdata/dvd 1,3T 40G 1,3T 4% /srv/dvd
bigdata/owncloud 2,1T 851G 1,3T 41% /srv/owncloud
bigdata/system 1,5T 227G 1,3T 16% /srv/system
bigdata/enigma2 1,3T 17G 1,3T 2% /srv/enigma2
/dev/sda1 373G 93G 280G 25% /home
//192.168.178.48/Multimedia 9,0T 5,2T 3,8T 59% /mnt/WohnzimmerNAS/Multimedia
//192.168.178.48/homes 9,0T 5,2T 3,8T 59% /mnt/WohnzimmerNAS/homes
//192.168.178.48/Web 9,0T 5,2T 3,8T 59% /mnt/WohnzimmerNAS/Web
tmpfs 1,5G 0 1,5G 0% /run/user/1000
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
dajohb schrieb: Apparmor blockiert es.
Wenn kein Apparmor brauchst, dann stoppe es und disable es.
Hab ich nach diesen Anleitungen bereits gefixt:
https://support.plesk.com/hc/en-us/articles/360004185293-Unable-to-start-MySQL-on-Ubuntu-AVC-apparmor-DENIED-operation-open-
https://askubuntu.com/questions/916009/mysql-wont-start-because-of-apparmor Deshalb kommt auch keine Fehlermeldung mehr bezüglich apparmor.
MySQL startet aber immer noch nicht.
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
/var/log/mysql/error.log
2019-04-03T21:09:20.713114Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2019-04-03T21:09:20.713183Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2019-04-03T21:09:20.887469Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-03T21:09:20.889473Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.25-0ubuntu0.16.04.2) starting as process 11771 ...
2019-04-03T21:09:20.895626Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-03T21:09:20.895692Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-03T21:09:20.895705Z 0 [Note] InnoDB: Uses event mutexes
2019-04-03T21:09:20.895716Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-04-03T21:09:20.895726Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-04-03T21:09:20.895737Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-03T21:09:20.896088Z 0 [Note] InnoDB: Number of pools: 1
2019-04-03T21:09:20.896228Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-03T21:09:20.898224Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-04-03T21:09:20.910424Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-03T21:09:20.913088Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-03T21:09:20.925993Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-04-03T21:09:20.926230Z 0 [ERROR] InnoDB: Invalid redo log header checksum.
2019-04-03T21:09:20.926266Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-04-03T21:09:21.527639Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-04-03T21:09:21.527724Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-04-03T21:09:21.527745Z 0 [ERROR] Failed to initialize builtin plugins.
2019-04-03T21:09:21.527759Z 0 [ERROR] Aborting
2019-04-03T21:09:21.527787Z 0 [Note] Binlog end
2019-04-03T21:09:21.528556Z 0 [Note] /usr/sbin/mysqld: Shutdown complete journalctl -xe -u mysql
Apr 03 23:09:50 server systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Apr 03 23:09:50 server systemd[1]: mysql.service: Unit entered failed state.
Apr 03 23:09:50 server systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 03 23:09:51 server systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Apr 03 23:09:51 server systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Apr 03 23:09:51 server systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Apr 03 23:09:52 server systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE /var/log/syslog|grep -i mysql
Apr 3 23:10:51 server systemd[1]: Failed to start MySQL Community Server.
Apr 3 23:10:51 server systemd[1]: mysql.service: Unit entered failed state.
Apr 3 23:10:51 server systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 3 23:10:52 server systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Apr 3 23:10:52 server systemd[1]: Stopped MySQL Community Server.
Apr 3 23:10:52 server systemd[1]: Starting MySQL Community Server...
Apr 3 23:10:53 server systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
|
dajohb
Anmeldungsdatum: 29. Januar 2016
Beiträge: 166
|
hast du schon mit innodb-recovery-modes=3 versucht?
Die redologs werden aber nicht mehr zurückgespielt.
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
dajohb schrieb: hast du schon mit innodb-recovery-modes=3 versucht?
Die redologs werden aber nicht mehr zurückgespielt.
Sagt mir nichts 😳 was wie wo wird das eingestellt?
|
dajohb
Anmeldungsdatum: 29. Januar 2016
Beiträge: 166
|
das setzt du im mysql config.
Zeigt mal
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15 | tree /etc/mysql
/etc/mysql
├── conf.d
│ ├── mysql.cnf
│ └── mysqldump.cnf
├── debian.cnf
├── debian-start
├── my.cnf -> /etc/alternatives/my.cnf
├── my.cnf.fallback
├── mysql.cnf
└── mysql.conf.d
├── mysqld.cnf
└── mysqld_safe_syslog.cnf
2 directories, 9 files
|
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
dajohb schrieb: hast du schon mit innodb-recovery-modes=3 versucht?
Die redologs werden aber nicht mehr zurückgespielt.
Habs temporär in /etc/mysql/conf.d/mysqldump.cnf eingespielt. Korrekt?
Kein Erfolg, hab ich wieder rausgenommen.
|
dajohb
Anmeldungsdatum: 29. Januar 2016
Beiträge: 166
|
hier rein:
mysqld.cnf und unter Sektion
[mysqld]
|
dajohb
Anmeldungsdatum: 29. Januar 2016
Beiträge: 166
|
hast du innodb_log_file_size auf 128M erhöht?
innodb_log_file_size=128M
und war es vorher kleiner?
Wenn ja, versuchst mal hiermit
| sudo mv /var/lib/mysql/ib_logfile* ~/
|
restarte dann mysql
|
ChristianKnorr
(Themenstarter)
Anmeldungsdatum: 15. Januar 2008
Beiträge: 100
|
dajohb schrieb: hier rein:
mysqld.cnf und unter Sektion
[mysqld]
Kein Erfolg
|