From files/mysql.conf.d: # ----------------+----------------------------------------------------------- # startup_timeout : integer [seconds] default 15 # : time to wait for mysqld up and running, after this it's # : marked as failed # ----------------+----------------------------------------------------------- # but in files/mysql.rc6 default actually is: STARTUPTIMEOUT=5 Reproducible: Always Steps to Reproduce: 1. install mysql-init-scripts 2. look at /etc/init.d/mysql and /etc/conf.d/mysql Actual Results: STARTUPTIMEOUT=5 in /etc/init.d/mysql Expected Results: STARTUPTIMEOUT=15
Bump! I was having problems with mysql-5.0.54 not starting with my computer after a rebuild (so mysql-init-scripts-1.2 was rebuilt) and after editing /etc/init.d/mysql and going to the 15-sec startuptimeout, it starts correctly now. Thanks, cctsurf
Confirmed on amd64. On startup the mysql init script failed, but still brought up the mysql process. Further manual attempts to start up the init script obviously complained about the existing server process. This is a really annoying bug especially on dev boxes and other desktop systems (which are rebooted fairly often) running mysql.
Created attachment 145736 [details, diff] One-line patch to fix the default startuptimeout in the mysql init script
(In reply to comment #1) > Bump! I was having problems with mysql-5.0.54 not starting with my computer > after a rebuild (so mysql-init-scripts-1.2 was rebuilt) and after editing > /etc/init.d/mysql and going to the 15-sec startuptimeout, it starts correctly > now. just out of curiosity setting "startup_timeout" in /etc/conf.d/mysql does equals to change it in the /etc/init.d/mysql script ?
The current mysql init script has the following: startup_timeout=*) STARTUPTIMEOUT="${my_default#startup_timeout=}" ;; so this bug doesn't seem relevant anymore.
