Bug 844901

Description of problem:
SQLgrey is started at the same time as mysqld. When SQLgrey starts, mysqld is not ready to process queries so SQLGrey reports an error. Later SQLgrey reconnects and the system works.
Starting SQLGrey *after* mysqld has successfully started would fix that.


Version-Release number of selected component (if applicable):
sqlgrey-1.7.6-4.fc15.noarch

How reproducible:
Rebooting.. 

Steps to Reproduce:
1.
2.
3.
  
Actual results:

/var/log/maillog:
Jul 29 14:50:08 qube sqlgrey: Process Backgrounded
Jul 29 14:50:08 qube sqlgrey: 2012/07/29-14:50:08 sqlgrey (type Net::Server::Multiplex) starting! pid(1498)
Jul 29 14:50:08 qube sqlgrey: Binding to TCP port 2501 on host localhost#012
Jul 29 14:50:08 qube sqlgrey: Setting gid to "995 995"
Jul 29 14:50:08 qube sqlgrey: Setting uid to "996"
Jul 29 14:50:08 qube sqlgrey: dbaccess: can't connect to DB: Can't connect to local MySQL server through socket '/var/lib
/mysql/mysql.sock' (2)
Jul 29 14:50:08 qube sqlgrey: dbaccess: error: couldn't get now() from DB: Can't connect to local MySQL server through so
cket '/var/lib/mysql/mysql.sock' (2)
Jul 29 14:50:08 qube sqlgrey: dbaccess: can't connect to DB: Can't connect to local MySQL server through socket '/var/lib
/mysql/mysql.sock' (2)
Jul 29 14:50:08 qube sqlgrey: dbaccess: error: couldn't access config table: Can't connect to local MySQL server through 
socket '/var/lib/mysql/mysql.sock' (2)
..
..

/var/log/messages: 
Jul 29 14:50:08 qube mysqld_safe[1239]: 120729 14:50:08 mysqld_safe Logging to '/var/log/mysqld.log'.
Jul 29 14:50:08 qube sqlgrey[1244]: Starting SQLgrey: [  OK  ]#015[  OK  ]
Jul 29 14:50:08 qube mysqld_safe[1239]: 120729 14:50:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Jul 29 14:50:09 qube postfix[1500]: Starting postfix: [  OK  ]

==> see, MySQL is started at the same time as SQLgrey (14:50:08)

/var/log/mysqld.log:
120729 14:50:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120729 14:50:09 [Note] Plugin 'FEDERATED' is disabled.
120729 14:50:10 InnoDB: The InnoDB memory heap is disabled
120729 14:50:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120729 14:50:10 InnoDB: Compressed tables use zlib 1.2.5
120729 14:50:10 InnoDB: Using Linux native AIO
120729 14:50:10 InnoDB: Initializing buffer pool, size = 512.0M
120729 14:50:10 InnoDB: Completed initialization of buffer pool
120729 14:50:10 InnoDB: highest supported file format is Barracuda.
120729 14:50:12  InnoDB: Waiting for the background threads to start
120729 14:50:13 InnoDB: 1.1.8 started; log sequence number 3227038
120729 14:50:14 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
120729 14:50:14 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
120729 14:50:14 [Note] Server socket created on IP: '0.0.0.0'.
120729 14:50:15 [Note] Event Scheduler: Loaded 0 events
120729 14:50:15 [Note] /usr/libexec/mysqld: ready for connections.

Expected results:

MySQL is ready at 14:50:15 to process queries.. so SQLGrey should start then..  would be interesting to see how that can be solved by using Requires/After with systemd

I made a workaround for myself by adding a "sleep 10" at the start of the initscript .. but this is pretty ugly.

Additional info: