Ausfälle des Datenbank-Servers

frobi

Neuer Benutzer
Beiträge
3
Hallo zusammen,

ich habe das Problem, das mein DatenbankServer immer wieder sporadisch kurz ausfällt.
Mein Hoster sagt mir nun das es am Speicher liegt und ich ein höheres Paket benötige.
Es kommt mir etwas seltsam vor und deshalb würde ich mich freuen, wenn jemand auf folgenden Log-Auszug einen kurzen Blick werfen könnte.
Vielen Dank im vorraus.

2016-11-28 15:49:57 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:49:57 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:49:57 0 [Note] /usr/iports/libexec/mysqld (mysqld 5.6.27) starting as process 72275 ...
2016-11-28 15:49:58 72275 [Note] Plugin 'FEDERATED' is disabled.
2016-11-28 15:49:58 72275 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-11-28 15:49:58 72275 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-28 15:49:58 72275 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-28 15:49:58 72275 [Note] InnoDB: Memory barrier is not used
2016-11-28 15:49:58 72275 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-11-28 15:49:58 72275 [Note] InnoDB: Using CPU crc32 instructions
2016-11-28 15:49:58 72275 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-28 15:49:58 72275 [Note] InnoDB: Completed initialization of buffer pool
2016-11-28 15:49:58 72275 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-28 15:49:58 72275 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438096660
2016-11-28 15:49:58 72275 [Note] InnoDB: Database was not shutdown normally!
2016-11-28 15:49:58 72275 [Note] InnoDB: Starting crash recovery.
2016-11-28 15:49:58 72275 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-11-28 15:49:58 72275 [Note] InnoDB: Restoring possible half-written data pages
2016-11-28 15:49:58 72275 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 438096915
2016-11-28 15:49:58 72275 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2016-11-28 15:49:59 72275 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-28 15:49:59 72275 [Note] InnoDB: Waiting for purge to start
2016-11-28 15:49:59 72275 [Note] InnoDB: 5.6.27 started; log sequence number 438096915
2016-11-28 15:49:59 72275 [Note] Server hostname (bind-address): '*'; port: 3306
2016-11-28 15:49:59 72275 [Note] IPv6 is not available.
2016-11-28 15:49:59 72275 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2016-11-28 15:49:59 72275 [Note] Server socket created on IP: '0.0.0.0'.
2016-11-28 15:49:59 72275 [Note] Event Scheduler: Loaded 0 events
2016-11-28 15:49:59 72275 [Note] /usr/iports/libexec/mysqld: ready for connections.
Version: '5.6.27' socket: '/tmp/mysql.sock' port: 3306 Source distribution
161128 15:51:08 mysqld_safe mysqld restarted
2016-11-28 15:51:09 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:51:09 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:51:09 0 [Note] /usr/iports/libexec/mysqld (mysqld 5.6.27) starting as process 72497 ...
2016-11-28 15:51:09 72497 [Note] Plugin 'FEDERATED' is disabled.
2016-11-28 15:51:09 72497 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-11-28 15:51:09 72497 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-28 15:51:09 72497 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-28 15:51:09 72497 [Note] InnoDB: Memory barrier is not used
2016-11-28 15:51:09 72497 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-11-28 15:51:09 72497 [Note] InnoDB: Using CPU crc32 instructions
2016-11-28 15:51:09 72497 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-28 15:51:09 72497 [Note] InnoDB: Completed initialization of buffer pool
2016-11-28 15:51:09 72497 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-28 15:51:09 72497 [Note] InnoDB: The log sequence numbers 424187534 and 424187534 in ibdata files do not match the log sequence number 438097620 in the ib_logfiles!
2016-11-28 15:51:09 72497 [Note] InnoDB: Database was not shutdown normally!
2016-11-28 15:51:09 72497 [Note] InnoDB: Starting crash recovery.
2016-11-28 15:51:09 72497 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-11-28 15:51:10 72497 [Note] InnoDB: Restoring possible half-written data pages
2016-11-28 15:51:10 72497 [Note] InnoDB: from the doublewrite buffer...
2016-11-28 15:51:10 72497 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-28 15:51:10 72497 [Note] InnoDB: Waiting for purge to start
2016-11-28 15:51:10 72497 [Note] InnoDB: 5.6.27 started; log sequence number 438097620
2016-11-28 15:51:10 72497 [Note] Server hostname (bind-address): '*'; port: 3306
2016-11-28 15:51:10 72497 [Note] IPv6 is not available.
2016-11-28 15:51:10 72497 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2016-11-28 15:51:10 72497 [Note] Server socket created on IP: '0.0.0.0'.
2016-11-28 15:51:10 72497 [Note] Event Scheduler: Loaded 0 events
2016-11-28 15:51:10 72497 [Note] /usr/iports/libexec/mysqld: ready for connections.
Version: '5.6.27' socket: '/tmp/mysql.sock' port: 3306 Source distribution
161128 15:51:12 mysqld_safe mysqld restarted
2016-11-28 15:51:13 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:51:13 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:51:13 0 [Note] /usr/iports/libexec/mysqld (mysqld 5.6.27) starting as process 72567 ...
2016-11-28 15:51:13 72567 [Note] Plugin 'FEDERATED' is disabled.
2016-11-28 15:51:13 72567 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-11-28 15:51:13 72567 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-28 15:51:13 72567 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-28 15:51:13 72567 [Note] InnoDB: Memory barrier is not used
2016-11-28 15:51:13 72567 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-11-28 15:51:13 72567 [Note] InnoDB: Using CPU crc32 instructions
2016-11-28 15:51:13 72567 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-28 15:51:14 72567 [Note] InnoDB: Completed initialization of buffer pool
2016-11-28 15:51:14 72567 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-28 15:51:14 72567 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438097620
2016-11-28 15:51:14 72567 [Note] InnoDB: Database was not shutdown normally!
2016-11-28 15:51:14 72567 [Note] InnoDB: Starting crash recovery.
2016-11-28 15:51:14 72567 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-11-28 15:51:14 72567 [Note] InnoDB: Restoring possible half-written data pages
2016-11-28 15:51:14 72567 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 438097630
2016-11-28 15:51:15 72567 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-28 15:51:15 72567 [Note] InnoDB: Waiting for purge to start
161128 15:51:16 mysqld_safe mysqld from pid file /var/db/mysql/nakovi.pid ended
161128 15:54:12 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2016-11-28 15:54:12 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:54:12 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-11-28 15:54:12 0 [Note] /usr/iports/libexec/mysqld (mysqld 5.6.27) starting as process 73843 ...
2016-11-28 15:54:12 73843 [Note] Plugin 'FEDERATED' is disabled.
2016-11-28 15:54:12 73843 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-11-28 15:54:12 73843 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-28 15:54:12 73843 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-28 15:54:13 73843 [Note] InnoDB: Memory barrier is not used
2016-11-28 15:54:13 73843 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-11-28 15:54:13 73843 [Note] InnoDB: Using CPU crc32 instructions
2016-11-28 15:54:13 73843 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-28 15:54:13 73843 [Note] InnoDB: Completed initialization of buffer pool
2016-11-28 15:54:13 73843 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-28 15:54:13 73843 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438097620
2016-11-28 15:54:13 73843 [Note] InnoDB: Database was not shutdown normally!
2016-11-28 15:54:13 73843 [Note] InnoDB: Starting crash recovery.
2016-11-28 15:54:13 73843 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-11-28 15:54:13 73843 [Note] InnoDB: Restoring possible half-written data pages
2016-11-28 15:54:13 73843 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 438097630
2016-11-28 15:54:13 73843 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-28 15:54:13 73843 [Note] InnoDB: Waiting for purge to start
2016-11-28 15:54:13 73843 [Note] InnoDB: 5.6.27 started; log sequence number 438097630
2016-11-28 15:54:13 73843 [Note] Server hostname (bind-address): '*'; port: 3306
2016-11-28 15:54:13 73843 [Note] IPv6 is not available.
2016-11-28 15:54:13 73843 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2016-11-28 15:54:13 73843 [Note] Server socket created on IP: '0.0.0.0'.
2016-11-28 15:54:13 73843 [Note] Event Scheduler: Loaded 0 events
2016-11-28 15:54:13 73843 [Note] /usr/iports/libexec/mysqld: ready for connections.
Version: '5.6.27' socket: '/tmp/mysql.sock' port: 3306 Source distribution


Gruß,
frobi
 
Werbung:
Mein Hoster sagt mir nun das es am Speicher liegt und ich ein höheres Paket benötige.

Hihi, verkaufsfreudige Jungs da, gell?

MySQL fällt halt ab und an auf die Nase und zerbröselt dabei. Deine InnoDB-Dateien scheinen defekt zu sein, das ist mehr oder weniger irreparabel. Versuche einen kompletten Dump zu ziehen (falls das noch geht), lösche dann MySQL, installier es neu und spiel den Dump ein. Ziehe regelmäßig Dumps und hebe diese auf, denn das wird sicher wieder passieren. Falls Dir das zu blöde ist, migriere zu PostgreSQL ;-)
 
Das habe ich mir auch eher gedacht.
PostgreSQL steht leider nicht zur Verfügung, ich muss also mit dem Leben was ich habe.
Gibt es ggf. ein Script/Tool welches ich per Cronjaob die Funktionalität prüfen lassen kann und ggf. reparieren kann?

Ich danke Dir für deine Info.
 
es gibt mysqlrepair. Davon abgesehen, daß es schon bezeichnend ist, daß es solch ein Tool gibt - das geht IIRC nicht bei InnoDB. Es gibt wohl auch ein mysqlcheck - Tool. Ich weiß aber nicht, wie das im laufenden Betrieb wirkt, also ob das z.B. Tabellen sperrt oder so.

Wenn ein Dump fehlerfrei durchläuft ist das aber schon mal ein recht sicheres Indiz, daß die DB ok ist. Bei MYISAM sperrt dies aber fröhlich Deine Tabellen ;-)
 
Werbung:
Zurück
Oben