Yes, I meant MySQL was running before the OS upgrade. Actually there is a log entry in VarLogDistupgradeApttermlog.gz which shows that it had been running for about a month. I had the feeling that MySQL was stopped by the upgrade script before the bacula upgrade, and indeed I saw a few lines *after* the failed bacula upgrade (and after submitting this issue, so this is not in the logs) on the console that was related to MySQL. Maybe MySQL was started at that time. Following that, the second Bacula reconfiguration succeeded. In the log file above I also see two strange lines:
(Reading database ... 55366 files and directories currently installed.) Preparing to replace mysql-server-5.1 5.1.37-1ubuntu5.1 (using .../mysql-server-5.1_5.1.41-3ubuntu12.1_i386.deb) ... * Stopping MySQL database server mysqld [132G [126G[ OK ] * Stopping MySQL database server mysqld [132G [126G[ OK ] Unpacking replacement mysql-server-5.1 ... Preparing to replace ubuntu-serverguide 9.10.11 (using .../ubuntu-serverguide_10.04.3_all.deb) ... I.e. it stops MySQL two times. On the other hand I do not find any line in this log file, which would indicate that MySQL daemon was started later during the upgrade (and before this issue report). -- package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) https://bugs.launchpad.net/bugs/588104 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
