When using EBS snashots on EC2, debian-sys-maint is different on new servers, so it stuck forever.
Also init/mysql.conf use:
exec /usr/sbin/mysqld
and I see error when running it like that:
100528 11:00:25 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
100528 11:00:25 [ERROR] Aborting
100528 11:00:25 [Note] /usr/sbin/mysqld: Shutdown complete
should'n it use mysqld_safe instead ?
This works for me:
....
exec /usr/bin/mysqld_safe
post-start script
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14; do /usr/bin/mysqladmin --defaults-file=$HOME/debian.cnf ping && exec $HOME/debian-start
sleep 1
done
end script
When using EBS snashots on EC2, debian-sys-maint is different on new servers, so it stuck forever.
Also init/mysql.conf use:
exec /usr/sbin/mysqld
and I see error when running it like that:
100528 11:00:25 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
100528 11:00:25 [ERROR] Aborting
100528 11:00:25 [Note] /usr/sbin/mysqld: Shutdown complete
should'n it use mysqld_safe instead ?
This works for me:
.... mysqld_ safe
exec /usr/bin/
post-start script
/usr/bin/ mysqladmin --defaults- file=$HOME/ debian. cnf ping && exec $HOME/debian-start
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14; do
sleep 1
done
end script