It seems when I just build from source and do make install, it works fine: hingo@mermaid:~/hacking/drizzle/builds/2012.01.30-src$ sbin/drizzled InnoDB: The log sequence number in ibdata files does not match the log sequence number in the ib_logfiles! 120124 9:58:10 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... "/tmp/mysql.socket" exists already. Do you have another Drizzle or MySQL running? Or perhaps the file is stale and should be removed? 120124 10:01:11 InnoDB: Starting shutdown... hingo@mermaid:~/hacking/drizzle/builds/2012.01.30-src$
So it only happens with debs and/or in relation to upstart. Clint, did you actually reproduce this yet? Or is it purely an issue with my build? ** Changed in: drizzle Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920175 Title: shutdown from within Drizzle panics on assertion - upstart respawn consequences To manage notifications about this bug go to: https://bugs.launchpad.net/drizzle/+bug/920175/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
