On 10/27/05, Christian Hammers <[EMAIL PROTECTED]> wrote: > Hello Olaf > > On 2005-10-26 Olaf van der Spek wrote: > > > Can you see manually what could be the problem? > > > > The daemon appeared to be running fine directly after. I'm thinking > > about a race condition. > > Could it be the start process returns before the daemon is ready to > > accept connections? > > Do you have a unusual big database? Or maybe had a crashed innodb table > that needed to rollback? I never experienced it.
No, in fact, I think the database is empty. However, there is another process that's doing very much disk IO on a not-so-fast disk. Oct 24 17:51:29 c mysqld_safe[17394]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! Oct 24 17:51:31 c mysqld_safe[17536]: started Oct 24 17:51:31 c mysqld[17539]: InnoDB: The first specified data file ./ibdata1 did not exist: Oct 24 17:51:40 c mysqld[17539]: 051024 17:51:40 [Note] /usr/sbin/mysqld: ready for connections. I'm not sure when the init script returns, but you can see it takes at least 9 seconds from started to ready.
