[00:38] ducktype: my guess is that upstart thinks mysql is started before it's actually listening [00:41] oh good [00:41] checking that one [00:42] at least, that could explain things ;) [00:42] a simple pre-start sleep should do the trick [00:44] nothing :( [00:44] mm wait [00:45] you can try to log something before it starts mydns [00:45] to make sure it actually tries to start it [00:48] mm why: post-start script sleep 3 end script [00:49] in the mysql job make start mysql wait forever, like when i specified "task" before to try [00:55] JanC: i've logged from mysql pre/post start and mydns pre/post start i nto a file [00:56] i only see one line mysql pre-start end [00:56] seems thath the mysql job is't considered finished [00:56] so basically upstart doesn't detect when mysql is finished starting [00:56] hangs on exec /usr/sbin/mysqld [00:57] you might need an "expect" stanza [00:58] or cheat and start mysqld from pre-start instead ;) [00:59] hm, it seems like Ubuntu starts mysqld without such tricks... [01:01] ducktype: this is the default mysql.conf in Maverick: http://paste.ubuntu.com/552322/ [01:02] thamk you, checking.. [01:02] things like the AppArmor profile you probably don't need [01:15] i'm using mariadb not mysql but they are really the same [01:15] seems to be: exec /usr/sbin/mysqld & [01:15] the & [01:15] now doesn't hang on exec