Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Excon NoMethodError #324

Closed
kleinmatic opened this Issue Jun 7, 2012 · 0 comments

Comments

Projects
None yet
1 participant

New install of 3.0.24, with fog 1.1.2 and excon 0.9.6. Regular old backup with s3 storage breaks with this error. There's an issue in fog for this but they say they fixed in 1.2. When I try to use 1.2 Backup has a broken dependency for fog :(

Here's the fog issue: fog/fog#789

I tried going back to 3.0.23 to no avail. Hope you can help. Below is the stack trace (identical to the 3.0.24 stack trace)

[2012/06/07 17:59:25][message] [ backup 3.0.23 : ruby 1.8.7 (2010-04-19 patchlevel 253) [i686-linux], MBARI 0x8770, Ruby Enterprise Edition 2010.02 ]
[2012/06/07 17:59:25][message] Database::MySQL started dumping and archiving 'test'.
[2012/06/07 17:59:26][message] Packaging the backup files...
[2012/06/07 17:59:26][message] Splitter configured with a chunk size of 250MB.
[2012/06/07 17:59:26][message] Packaging Complete!
[2012/06/07 17:59:26][message] Cleaning up the temporary files...
[2012/06/07 17:59:26][error] ModelError: Backup for Description for test (test) Failed!
[2012/06/07 17:59:26][error] An Error occured which has caused this Backup to abort before completion.
[2012/06/07 17:59:26][error] Reason: NoMethodError
[2012/06/07 17:59:26][error] undefined method response' for #<Excon::Errors::SocketError:0x9158d90> [2012/06/07 17:59:26][error] [2012/06/07 17:59:26][error] Backtrace: [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/fog-1.1.2/lib/fog/aws/requests/storage/sync_clock.rb:12:insync_clock'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/storage/s3.rb:61:in transfer!' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/storage/base.rb:33:inperform!'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/1.8/fileutils.rb:1201:in to_proc' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/model.rb:245:ineach'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/model.rb:245:in perform!' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/model.rb:243:ineach'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/model.rb:243:in perform!' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/cli/utility.rb:74:inperform'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/cli/utility.rb:65:in each' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/lib/backup/cli/utility.rb:65:inperform'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/thor-0.14.6/lib/thor/task.rb:22:in send' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/thor-0.14.6/lib/thor/task.rb:22:inrun'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/thor-0.14.6/lib/thor/invocation.rb:118:in invoke_task' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/thor-0.14.6/lib/thor.rb:263:indispatch'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/thor-0.14.6/lib/thor/base.rb:389:in start' [2012/06/07 17:59:26][error] /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/backup-3.0.23/bin/backup:11 [2012/06/07 17:59:26][error] /opt/ruby-enterprise/bin/backup:19:inload'
[2012/06/07 17:59:26][error] /opt/ruby-enterprise/bin/backup:19

@ghost ghost closed this Jun 9, 2013

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment