Ran into this one setting up a MySQL proxy, turns out i cant type 3406 and typed 3046. It produced the following when trying to connect:

ERROR 2003 (HY000): Can’t connect to MySQL server on ” (111)

Fixed it by using the correct port…

A

Came across this message in /var/log/messages:

logrotate: ALERT exited abnormally with [1]

you can get some information on the problem by running:

logrotate /etc/logrotate.conf

for me it turned out to be a bad filename in /etc/logrotate.d/syslog

A

If you haven’t played World of Goo go get it, it’s awesome!

It’s a puzzle game similar to Lemmings in which you build a structure to rescue all the goo balls! It sports an awesome sound track and is quite addictive. Demo has quite a few levels to play through. Grab it at: http://2dboy.com/games.php

A

MySQL 5.1.26 and 5.1.28 (newer versions may also do this) seem to discontinue output during InnoDB recovery, you may see the following with no additional output for 30-40 minutes:

081105 20:06:29 mysqld_safe Starting mysqld daemon with databases from /mysecretdata/mysql

Followed by the usual warning:

InnoDB: Log scan progressed past the checkpoint lsn 57 793368317
081105 20:06:31  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.

Notice the timestamp is right after the first message but did not appear in the log until 30 minutes later. The output appears to be buffered somewhere and not written to the log. So if you are wondering why you arn’t seeing your InnoDB recovery progress, this could be the reason.

A