- From: Mason Turner <
>
- To:
- Subject: [chef] Re: RabbitMQ upgraded, lost configuration
- Date: Fri, 12 Nov 2010 09:47:57 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=DyvJ1qjHuPJFh51mjFeJddMjGv/P7j6pKRk6qHNQ1xiSWkWvBffR8YcGqOpfhULQjs W95LZRC3nAPBYEj/hR5mtUzxrALCSpur6fqLc1CgzBXscbts7YNc3nnbgTj/kWzrFfoJ AVhcNe3SGcfSULSElqcCmFhWmn6MqFTu90GjA=
I moved my rabbitmq (and solr, and all the other chef component
configs) into the chef::server recipe. If they are overwritten by EPEL
, or whatever, the recipe will replace them with the right thing. If
things too badm hopefully a run of chef-solo will repair the server.
On Fri, Nov 12, 2010 at 9:29 AM, Vladimir Girnet
<
>
wrote:
>
Hi,
>
>
I'm using Chef 0.9.8 on CentOS 5 i386.
>
It looks like EPEL released today a new version of rabbitmq. I've
>
applied the upgrade, but after this Chef Server stopped working.
>
I've fixed this based on: http://wiki.opscode.com/display/chef/Chef+Indexer
>
>
However, this happened second time for me - when upgrading rabbitmq,
>
configuration is lost.
>
Is it possible somehow to retain rabbitmq configuration?
>
>
Are there any steps required to be done after rabbitmq re-configuration?
>
Like services restart/manual indexing?
>
>
Thanks,
>
>
--
>
Vladimir Girnet
>
Infrastructure Engineer
>
Tacit Knowledge
>
http://www.tacitknowledge.com
>
>
>
Archive powered by MHonArc 2.6.16.