Redmine

We recently updated from redmine 1.0.1 to 2.0.3. This was all done using the Bitnami stack. I have asked for support over there, and this seems to be a common issue, but no actual fixes. You can see more discussion at http://answers.bitnami.org/questions/5255/redmine-intermittent-503-service-temporarily-unavailable-errorthin-services?sort=votes&page=5

We just had another crash, where Redmine then presented with a 503 error, and resulted in having to restart the services.

This is what I saw in my production.log

Started PUT "/redmine/issues/6461" for 127.0.0.1 at Mon Jul 02 15:31:32 -0400 2012
Processing by IssuesController#update as HTML
  Parameters: REMOVED BY ME
Completed 500 Internal Server Error in 16ms

ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query: SELECT  `issues`.* FROM `issues`  WHERE `issues`.`id` = ? LIMIT 1):
  app/controllers/issues_controller.rb:319:in `find_issue'

Then this:

ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query: INSERT INTO `journals` (`created_on`, `journalized_id`, `journalized_type`, `notes`, `user_id`) VALUES (?, ?, ?, ?, ?)):
  app/models/journal.rb:47:in `save'
  app/models/issue.rb:1073:in `create_journal'
  app/models/issue.rb:731:in `save_issue_with_child_records'
  app/models/issue.rb:718:in `save_issue_with_child_records'
  app/controllers/issues_controller.rb:182:in `update'

What causes this, and how can we resolve it? Looking at the Bitnami change log (http://bitnami.org/files/stacks/redmine/2.0.3-1/changelog.txt), this should be using rails 2.3.6, thin, and mysql 5.0.83.