mysql upstart post-start should suppress spurious error messages

[dino99]

Get that error logged inside /var/log/upstart/mysql.log

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: mysql-server 5.5.28-0ubuntu0.12.10.1
ProcVersionSignature: Ubuntu 3.7.0-0.5-generic 3.7.0-rc4
Uname: Linux 3.7.0-0-generic i686
ApportVersion: 2.6.2-0ubuntu3
Architecture: i386
Date: Sun Nov 11 08:36:11 2012
KernLog:

Logs.var.log.daemon.log:

Logs.var.log.mysql.error.log:
MarkForUpload: True
MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: False
PackageArchitecture: all
SourcePackage: mysql-5.5
UpgradeStatus: No upgrade log present (probably fresh install)

[dino99 (9d9)]

This is on a genuine mysql installation (no tweak)

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I can reproduce this, but it doesn't appear that this is a bug to me. The mysql job retries the connection until the daemon is ready, and then runs any database upgrades that are necessary. So the first one or two attempts are expected to fail, and so these logged connection errors are nothing to be concerned about.

Apart from the log messages, is there any behaviour of mysql that you are expecting that is not working?

Marking this bug as Invalid, as I don't think this error message represents a bug. If I've missed something or if I am just flat out wrong, please explain and set the bug status back to New.

[Clint Byrum (clint-fewbar)]

Seems like we could do some work to explain the errors or even suppress them if they are what is expected.

[Robie Basak (racb)]

Good point.