Bug #10030

rake RAILS_ENV=production jobs:work --trace fails on Mysql::ProtocolError: invalid packet: sequence number mismatch(116 != 1(expected)):

Added by Dominick Rivard over 1 year ago. Updated 6 months ago.

Status:RejectedStart date:10/11/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Keywords:puppet dashboard Mysql ProtocolError Affected URL:
Branch: Affected Dashboard version:

Description

Hi,

I was trying to install puppet-dashboard today using the git repository. I was previously using an old version and we wanted to try the latest version. I get an error trying to run the job

rake RAILS_ENV=production jobs:work --trace

The error:

root@puppet /opt/puppet-dashboard:rake RAILS_ENV=production jobs:work (in /opt/puppet-dashboard) [Worker(host:puppet pid:8876)] Starting job worker [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.6975 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.1423 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.1729 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.4653 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 1.3063 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 2.6208 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.2781 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 1.0079 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 1.0200 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.1553 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.3401 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 1.6646 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.5881 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.2290 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.3102 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.3572 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 1.7408 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 0.2603 [Worker(host:puppet pid:8876)] Report.create_from_yaml_file completed after 1.2202 rake aborted! Mysql::ProtocolError: invalid packet: sequence number mismatch(116 != 1(expected)): UPDATE delayed_jobs SET locked_by = null, locked_at = null WHERE (locked_by = ‘host:puppet pid:8876’)

(See full trace by running task with —trace)

The log from production.log

` Processing DelayedJobFailuresController#index (for 10.255.60.143 at 2011-10-11 16:54:15) [GET] Parameters: {“action”=>“index”, “controller”=>“delayed_job_failures”}

ActiveRecord::StatementInvalid (Mysql::ProtocolError: invalid packet: sequence number mismatch(114 != 12(expected)): SELECT * FROM delayed_job_failures WHERE (delayed_job_failures.read = 0) ORDER BY created_at DESC): app/controllers/delayed_job_failures_controller.rb:29:in get_failures' app/controllers/delayed_job_failures_controller.rb:27:inget_failures' app/controllers/delayed_job_failures_controller.rb:4:in index' sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:incall' /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:92:in process_request' /usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:inmain_loop' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:418:in start_request_handler' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:358:inhandle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:in safe_fork' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:354:inhandle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in __send__' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:inmain_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in start_synchronously' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:163:instart' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:213:in start' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:262:inspawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:126:in lookup_or_add' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:256:inspawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:80:in synchronize' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:79:insynchronize' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:255:in spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:154:inspawn_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:in handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:insend‘ /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in main_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:instart_synchronously’ /usr/lib/phusion_passenger/passenger-spawn-server:61

Rendering /opt/puppet-dashboard/public/500.html (500 Internal Server Error)`

I am on version:

commit c332602b878e28d837b32df3f664905d4a7d6d2f Merge: 484b323 0f0967f Author: Michael Stahnke stahnma@puppetlabs.com Date: Mon Oct 10 10:41:21 2011 -0700

Merge branch ‘1.2rc’

Puppet dashboard is installed on a debian 6.0.2 server with mysql 5.0 backend on a seperate server.

Thank you!

History

#1 Updated by Dominick Rivard over 1 year ago

there is one thing I forgot to mention I also get the error message about the MySQL::ProtocolError when I go to http://localhost/delayed_job_failures that is generating a HTTP 500 error.

thank you

#2 Updated by Daniel Sauble over 1 year ago

  • Status changed from Unreviewed to Accepted
  • Affected Dashboard version deleted (1.2.2rc2)

#3 Updated by Daniel Pittman about 1 year ago

  • Target version deleted (173)

#4 Updated by Aaron Stone 6 months ago

  • Status changed from Accepted to Rejected

This affects ruby-mysql 2.9.4 only: https://github.com/tmtm/ruby-mysql/issues/8

Puppet Dashboard still vendors version 2.9.0, which does not have the issue.

Also available in: Atom PDF