Ewig laufender mySQL Process

Ich habe einen einzelnen mySQL Process der ewig läuft. Starte ich Server neu, ist er sofort da, kille ich den Process, dann taucht er auch gleich wieder mit einer neuen PID auf. Er verbraucht 10-200% CPU. Wenn ich den Process kill, dann erhalte ich in mysql-error.log diesen Eintrag:

Zitat:

150321 16:14:38 mysqld_safe Number of processes running now: 0 150321 16:14:38 mysqld_safe mysqld restarted 2015-03-21 16:14:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-03-21 16:14:39 14153 [Note] Plugin 'FEDERATED' is disabled. 2015-03-21 16:14:39 14153 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-03-21 16:14:39 14153 [Note] InnoDB: The InnoDB memory heap is disabled 2015-03-21 16:14:39 14153 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-03-21 16:14:39 14153 [Note] InnoDB: Memory barrier is not used 2015-03-21 16:14:39 14153 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-03-21 16:14:39 14153 [Note] InnoDB: Using Linux native AIO 2015-03-21 16:14:39 14153 [Note] InnoDB: Using CPU crc32 instructions 2015-03-21 16:14:39 14153 [Note] InnoDB: Initializing buffer pool, size = 256.0M 2015-03-21 16:14:39 14153 [Note] InnoDB: Completed initialization of buffer pool 2015-03-21 16:14:39 14153 [Note] InnoDB: Highest supported file format is Barracuda. 2015-03-21 16:14:39 14153 [Note] InnoDB: Log scan progressed past the checkpoint lsn 545863896626 2015-03-21 16:14:39 14153 [Note] InnoDB: Database was not shutdown normally! 2015-03-21 16:14:39 14153 [Note] InnoDB: Starting crash recovery. 2015-03-21 16:14:39 14153 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-03-21 16:14:39 14153 [Note] InnoDB: Restoring possible half-written data pages 2015-03-21 16:14:39 14153 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 545869139456 InnoDB: Doing recovery: scanned up to log sequence number 545872788955 2015-03-21 16:14:39 14153 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 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 2015-03-21 16:14:40 14153 [Note] InnoDB: 128 rollback segment(s) are active. 2015-03-21 16:14:40 14153 [Note] InnoDB: Waiting for purge to start 2015-03-21 16:14:40 14153 [Note] InnoDB: 5.6.23 started; log sequence number 545872788955 2015-03-21 16:14:40 14153 [Note] Event Scheduler: Loaded 0 events 2015-03-21 16:14:40 14153 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.23-log' socket: '/var/lib/mysql/mysql.sock' port: 0 MySQL Community Server (GPL)

Kann mir dazu irgend jemand was sagen? Wieso läuft ein einzelner mySQL Process ewig? Witzigerweise steht dieser nicht in der Processlist. Da wird mir nichts (ungewöhnliches) angezeigt.



CentOS 6.6 (Final) mit mySQL Server Version: 5.6.23