[chef] Re: Re: Re: Chef Server Backup and Restore

[Vincent Jorgensen < >]

Hi all!

Here is the output of rabbitmq-server:

# rabbitmq-server 
Activating RabbitMQ plugins ...
0 plugins activated:

node with name "rabbit" already running on "laertes"
diagnostics:
- nodes and their ports on laertes: [{rabbit,34726},
                                     {rabbitmqprelaunch2047,42450}]
- current node: 

 
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: tCzpZ8Rs9Ql4DuU5bRpWyA==

Also, it's nearly identical for both servers, so it's definitely running.

How do I re-apply the configuration?

Best,

Vincent

On Mar 19, 2012, at 11:44 AM, KC Braunschweig wrote:

> Dan is probably right about Rabbit. IIRC its configuration is tied to
> its hostname so if you bring it up again with a new hostname, it will
> ignore the config. Re-applying the configuration should sort it out.
> 
> KC
> 
> On Mon, Mar 19, 2012 at 11:03 AM, Daniel DeLeo 
> <
 >
>  wrote:
>> 
>> 
>> On Monday, March 19, 2012 at 10:55 AM, Vincent Jorgensen wrote:
>> 
>>> Hi all!
>>> 
>>> I'm attempting to create a clone of the running chef server. Since it's 
>>> running in AWS, I created an EBS/AMI and re-launched it. Everything 
>>> almosts, but when I attempt to do "knife cookbook upload mycookbook -V" I 
>>> get the following error:
>>> 
>>> Uploading mycookbook [1.0.0]
>>> INFO: Saving mycookbook
>>> INFO: Validating ruby files
>>> INFO: Validating templates
>>> INFO: Syntax OK
>>> INFO: Uploading files
>>> INFO: HTTP Request Returned 500 Internal Server Error: Connection failed 
>>> - user: chef
>>> ERROR: Server returned error for 
>>> http://107.21.8.91:4000/cookbooks/mycookbook/1.0.0, retrying 1/5 in 4s
>>> INFO: HTTP Request Returned 500 Internal Server Error: Connection failed 
>>> - user: chef
>>> ERROR: Server returned error for 
>>> http://107.21.8.91:4000/cookbooks/mycookbook/1.0.0, retrying 2/5 in 7s
>>> INFO: HTTP Request Returned 500 Internal Server Error: Connection failed 
>>> - user: chef
>>> ERROR: Server returned error for 
>>> http://107.21.8.91:4000/cookbooks/mycookbook/1.0.0, retrying 3/5 in 9s
>>> INFO: HTTP Request Returned 500 Internal Server Error: Connection failed 
>>> - user: chef
>>> ERROR: Server returned error for 
>>> http://107.21.8.91:4000/cookbooks/mycookbook/1.0.0, retrying 4/5 in 18s
>>> INFO: HTTP Request Returned 500 Internal Server Error: Connection failed 
>>> - user: chef
>>> ERROR: Server returned error for 
>>> http://107.21.8.91:4000/cookbooks/mycookbook/1.0.0, retrying 5/5 in 52s
>>> INFO: HTTP Request Returned 500 Internal Server Error: Connection failed 
>>> - user: chef
>>> ERROR: internal server error
>>> Response: Connection failed - user: chef
>>> 
>>> I suspect that "chef-client" is going to fail as well. As near as my 
>>> rudimentary google search could ascertain, this appears related to 
>>> rabbitmq's DB. What's the safe way to change chef hosts without 
>>> regenerating all of my validation.pem and client.pem files? I have the 
>>> original instance still running, so I can copy any files from the 
>>> original if need be.
>>> 
>>> Thanks!
>>> Vincent
>> 
>> Logs from chef-server would be helpful.
>> 
>> Assuming the problem is RabbitMQ (seems likely), it looks like rabbitmq 
>> isn't running at all. Try running `rabbitmq-server` in the foreground and 
>> see if you get any hints. You can try blowing away the RabbitMQ database 
>> (usually in /var/lib/rabbitmq/mnesia/ ) and reconfiguring rabbit (see 
>> this: 
>> https://github.com/opscode/cookbooks/blob/master/chef-server/recipes/rabbitmq.rb
>>  ).
>> 
>> 
>> HTH,
>> --
>> Dan DeLeo
>> 
>> 
>>