On 08/05/2011 02:59 AM, dave-stfu wrote:
Hello
Recently, I've upgraded the Dashboard from 1.2rc3 to 1.2rc5. Now, the
delayed workers are dying right after I start them. The production.log
says:
Delayed::Backend::ActiveRecord::Job Update (0.0ms) Mysql::Error:
MySQL server has gone away: UPDATE `delayed_jobs` SET locked_by =
null, locked_at = null WHERE (locked_by = 'delayed_job.1 host:puppet
pid:16839')
#<ActiveRecord::StatementInvalid: Mysql::Error: MySQL server has gone
away: UPDATE `delayed_jobs` SET locked_by = null, locked_at = null
WHERE (locked_by = 'delayed_job.1 host:puppet pid:16839')>
The Dashboard itself is running smoothly. Also, running "rake
jobs:work" runs without any problems - it does the delayed jobs. The
settings are the same as in rc3 (user, permissions, db config).
Could this be the result of updated gems in rc5?
Cheers!
Dave
This issued was fixed for me after I did a pull on the 1.2rc branch this
morning.
--
Russell A Jackson <r...@csub.edu>
Network Analyst
California State University, Bakersfield
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
