Today we discovered a particularly subtle way of fucking up a
server restart. After a routine configuration change and RPM
upgrade, a colleague tried to restart an important master. That
failed. The message:
CODE:root@master ~]# /etc/init.d/mysql start
Starting MySQLCouldn't find MySQL manager (//bin/mysqlmanag[FAILED]erver (//bin/mysqld_safe)
The colleague tried multiple times, and finally resorted to manually typing a CODE:nohup mysqld_safe ... into a screen console, which he detached.
That took care of production for now and left us with an investigation. Why is the …