Hi.
Logan, David (SST - Adelaide) wrote:
Do you have any sample of error output? This would be useful.
I think the problem started where I have inserted the lines.
Thanks.
/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
=============================================
050914 04:44:49 mysqld restarted
050914 4:44:53 InnoDB: Started
/myProgs/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20-log' socket: '/tmp/mysql.sock' port: 3306
050918 0:27:35 Aborted connection 30 to db: 'unconnected' user: 'luke'
host: `loc
alhost' (Got timeout reading communication packets)
050923 9:01:48 Aborted connection 5931 to db: 'unconnected' user:
'luke' host: `l
ocalhost' (Got an error reading communication packets)
050923 9:01:48 Aborted connection 5934 to db: 'unconnected' user:
'luke' host: `l
ocalhost' (Got an error reading communication packets)
050923 9:01:48 Aborted connection 5937 to db: 'unconnected' user:
'luke' host: `l
ocalhost' (Got an error reading communication packets)
050923 9:01:48 Aborted connection 5940 to db: 'unconnected' user:
'luke' host: `l
ocalhost' (Got an error reading communication packets)
050923 9:01:48 Aborted connection 5943 to db: 'unconnected' user:
'luke' host: `l
ocalhost' (Got an error reading communication packets)
050923 9:01:48 Aborted connection 5946 to db: 'unconnected' user:
'luke' host: `l
ocalhost' (Got an error reading communication packets)
051015 14:53:20 Aborted connection 14332 to db: 'comstechIntDB' user:
'luke' host:
/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
=========================================================
`localhost' (Got an error writing communication packets)
051019 11:36:44 mysqld started
051019 11:36:44 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6648179
InnoDB: Doing recovery: scanned up to log sequence number 0 6648179
InnoDB: Last MySQL binlog file position 0 5263271, file name ./bench-bin.015
051019 11:36:44 InnoDB: Flushing modified pages from the buffer pool...
051019 11:36:44 InnoDB: Started
/myProgs/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20-log' socket: '/tmp/mysql.sock' port: 3306
051019 14:04:27 mysqld started
051019 14:04:27 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 6648179
InnoDB: Doing recovery: scanned up to log sequence number 0 6648179
InnoDB: Last MySQL binlog file position 0 5263271, file name ./bench-bin.015
051019 14:04:27 InnoDB: Flushing modified pages from the buffer pool...
051019 14:04:27 InnoDB: Started
/myProgs/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20-log' socket: '/tmp/mysql.sock' port: 3306
051019 18:55:31 /myProgs/mysql/libexec/mysqld: Normal shutdown
051019 18:55:31 InnoDB: Starting shutdown...
051019 18:55:33 InnoDB: Shutdown completed
051019 18:55:33 /myProgs/mysql/libexec/mysqld: Shutdown Complete
051019 18:55:33 mysqld ended
051019 19:39:17 mysqld started
051019 19:39:18 InnoDB: Started
/myProgs/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20-log' socket: '/tmp/mysql.sock' port: 3306
051019 19:46:11 /myProgs/mysql/libexec/mysqld: Normal shutdown
051019 19:46:11 InnoDB: Starting shutdown...
051019 19:46:14 InnoDB: Shutdown completed
051019 19:46:14 /myProgs/mysql/libexec/mysqld: Shutdown Complete
051019 19:46:14 mysqld ended
051019 19:46:20 mysqld started
051019 19:46:20 InnoDB: Started
/myProgs/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20-log' socket: '/tmp/mysql.sock' port: 3306
Thanks
David Logan
Database Administrator
HP Managed Services
148 Frome Street,
Adelaide 5000
Australia
+61 8 8408 4273 - Work
+61 417 268 665 - Mobile
+61 8 8408 4259 - Fax
-----Original Message-----
From: Luke Vanderfluit [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 October 2005 11:22 AM
To: mysql@lists.mysql.com
Subject: Re: database won't load after machine reboot
Hi.
For clarity, I'm running mysql 4.0.20
And I did start the mysql daemon.
Luke Vanderfluit wrote:
Hi.
I have a database that is used with wordpress blogging software.
Yesterday the server that it's running on reset itself.
Since then I can't access the database.
What could be going on here?
Any ideas?
Thanks.
Kind regards.
--
Luke
