Yep, but its basically identical to the info in the logs when its
restarting itself. I have upgraded to MySQL 5.5 as of yesterday, so
the error info differs due to the version now. Here is the log output:
110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from
110909 17:27:35 InnoDB: The InnoDB memory heap is disabled
110909 17:27:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110909 17:27:35 InnoDB: Compressed tables use zlib 1.2.3
110909 17:27:35 InnoDB: Initializing buffer pool, size = 2.0G
110909 17:27:36 InnoDB: Completed initialization of buffer pool
110909 17:27:36 InnoDB: highest supported file format is Barracuda.
110909 17:27:36 InnoDB: Waiting for the background threads to start
110909 17:27:37 InnoDB: 1.1.8 started; log sequence number 1589339
110909 17:27:37 [Note] Slave SQL thread initialized, starting
replication in log 'mysql-bin.002830' at position 293541, relay log
'./tau-relay-bin.000920' position: 253
110909 17:27:37 [Note] Event Scheduler: Loaded 0 events
110909 17:27:37 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.5.15' socket: '/tmp/mysql.sock' port: 3306 Source distribution
110909 17:27:37 [Note] Slave I/O thread: connected to master
'slave@kappa:3306',replication started in log 'mysql-bin.002830' at
Just not giving any hit of a problem....
Quoting Suresh Kuna <sureshkumarilu@stripped>:
> can you remove it from service and start it normally using mysqld_safe with
> log warnings enabled in the cnf file.
> On Fri, Sep 9, 2011 at 4:16 PM, <a.smith@stripped> wrote:
>> that really is the complete error log, that exact same info gets repeated
>> over and over, there is zero in the syslog and I get this behaviour when
>> running with no my.cnf (I do obviously have one but I tried without and it I
>> still see the prob, so that probably makes things easier from a
>> troubleshooting perspective)...
>> The system has loads of free RAM (8GB total).
>> Really the system isn't giving me much to go in in terms of clues....