MySQL fails to startup in a single-node deployment

[GoogleCodeExporter]

When running AppScale in a single-node deployment using the MySQL database
it fails to start. The generated stack trace is provided below:

/root/appscale/AppDB/mysql/mysql_helper.rb:63:in `initialize': No such file
or directory - /etc/mysql/ndb_mgmd.cnf (Errno::ENOENT)
        from /root/appscale/AppDB/mysql/mysql_helper.rb:63:in `open'
        from /root/appscale/AppDB/mysql/mysql_helper.rb:63:in
`setup_db_config_files'
        from /root/appscale/AppController/djinn.rb:755:in `setup_config_files'
        from /root/appscale/AppController/djinn.rb:506:in `change_job'
        from /root/appscale/AppController/djinn.rb:261:in `job_start'
        from /root/appscale/AppController/djinnServer.rb:131

It is attempting to write to "/etc/mysql/ndb_mgmd.cnf" but (at least on my
boxes) the folder /etc/mysql does not exist and as a result it fails. After
discussing this with Yoshi this may be because my boxes were installed
using the old scratch install which has since changed. He is going to
investigate to see if this is a real issue.

Original issue reported on code.google.com by jmkupfer...@gmail.com on 7 Apr 2010 at 10:56

[GoogleCodeExporter]

Changed priority to critical, since we definitely want to resolve this for the 
next
release.

Original comment by shattere...@gmail.com on 9 Apr 2010 at 3:32

• Added labels: Priority-Critical, Component-Persistence
• Removed labels: Priority-Medium

[GoogleCodeExporter]

/etc/mysql/ is created by mysql-server package, so could you verify that the
mysql-server-5.0 package is installed?

Original comment by yoshi...@gmail.com on 9 Apr 2010 at 5:46

[GoogleCodeExporter]

This was an issue caused by using an old AppScale install. Reinstalling with 
the new
build scripts fixes this.

Original comment by jmkupfer...@gmail.com on 14 Apr 2010 at 9:55

• Changed state: Fixed