Chef won't start with Bunny 0.8.0

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Unknown Unknown
  • Resolution: Fixed
  • Affects Version/s: 10.14.0
  • Fix Version/s: 10.14.0
  • Component/s: None
  • Labels:
    None

Description

[2012-09-06T20:57:30+00:00] INFO: Creating validation key...
[2012-09-06T20:57:30+00:00] INFO: Creating new key pair for chef-validator
[2012-09-06T20:57:31+00:00] INFO: Sending client(0ea80a9b-d49e-401a-8279-b307a20160af) to the index queue for addition.
[2012-09-06T20:57:31+00:00] FATAL: Connection to rabbitmq refused. Check your rabbitmq configuration and chef's amqp* settings
/usr/lib/ruby/gems/1.8/gems/bunny-0.8.0/lib/bunny/client.rb:117:in `init_connection': Connection initiation failed (Bunny::ProtocolError)
	from /usr/lib/ruby/gems/1.8/gems/bunny-0.8.0/lib/bunny/client.rb:298:in `start'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/index_queue/amqp_client.rb:45:in `amqp_client'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/index_queue/amqp_client.rb:72:in `queue_for_object'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/index_queue/indexable.rb:95:in `publish_object'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/index_queue/indexable.rb:74:in `add_to_index'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/couchdb.rb:118:in `store'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/api_client.rb:231:in `cdb_save'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/certificate.rb:139:in `create_validation_key'
	from /usr/lib/ruby/gems/1.8/gems/chef-10.14.0.rc.3/lib/chef/certificate.rb:114:in `gen_validation_key'
	from /usr/lib/ruby/gems/1.8/gems/chef-server-api-10.14.0.rc.3/config/init.rb:84
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core/bootloader.rb:529:in `load'
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core/bootloader.rb:529:in `load_initfile'
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core/bootloader.rb:377:in `run'
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core/bootloader.rb:97:in `run'
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core/server.rb:172:in `bootup'
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core/server.rb:42:in `start'
	from /usr/lib/ruby/gems/1.8/gems/merb-core-1.1.3/lib/merb-core.rb:165:in `start'
	from /usr/lib/ruby/gems/1.8/gems/chef-server-api-10.14.0.rc.3/bin/chef-server:84
	from /usr/sbin/chef-server:19:in `load'
	from /usr/sbin/chef-server:19

Not sure if this is related to this error or bunny 0.8.0 not being compatible with rabbitmq 1.7.1ubuntu1.

~ Qrack::Queue#publish will be removed in Bunny 0.8. Use direct_exchange = bunny.exchange(''); direct_exchange.publish('message', key: queue.name) if you want to publish directly to one given queue. For more informations see https://github.com/ruby-amqp/bunny/issues/15 and for more theoretical explanation check http://bit.ly/nOF1CK

Activity

Hide
Permalink
Bryan McLellan [Opscode] added a comment -

Pegged bunny < 0.8.0 on the Chef gem, which is really used by the chef-server, meh.

In Chef 11 erchef won't be using bunny.

Dan says:

FWIW, only the expanderctl commands go through bunny
expander uses the EM-based amqp gem

Show
Bryan McLellan [Opscode] added a comment - Pegged bunny < 0.8.0 on the Chef gem, which is really used by the chef-server, meh. In Chef 11 erchef won't be using bunny. Dan says: FWIW, only the expanderctl commands go through bunny expander uses the EM-based amqp gem

People

  • Assignee:
    Unassigned
    Reporter:
    Bryan McLellan [Opscode]
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: