- From: Cyril Scetbon <
>
- To:
- Subject: [chef] Re: Issue on EC2
- Date: Tue, 14 Jan 2014 21:39:24 +0100
Thanks, that was exactly the root cause !
Regards
--
Cyril SCETBON
On 13 Jan 2014, at 19:20, Seth Falcon
<
>
wrote:
>
Hi there,
>
>
>
writes:
>
> I have difficulties to make chef-server works on an EC2 instance. I
>
> always get an issue which seems to cause processes to restart in an
>
> infinite loop. Processes always fall down and a lot of CPU is consumed
>
> by always restarting them. You can find an extract of logs at
>
> http://pastebin.com/BAzP11t9
>
>
The logs suggest that the rabbitmq service is unable to start because
>
there is already an Erlang vm with the same name:
>
>
==> /var/log/chef-server/rabbitmq/current <==
>
2014-01-13_15:59:18.08077 0 plugins activated:
>
2014-01-13_15:59:18.08081
>
2014-01-13_15:59:18.12693 node with name "rabbit" already running on
>
"localhost"
>
2014-01-13_15:59:18.13304 diagnostics:
>
2014-01-13_15:59:18.13335 - nodes and their ports on localhost:
>
[{rabbit,47989},
>
2014-01-13_15:59:18.13337
>
{bookshelf,57685},
>
2014-01-13_15:59:18.13338
>
{erchef,44117},
>
2014-01-13_15:59:18.13338
>
{rabbitmqprelaunch12288,54518}]
>
2014-01-13_15:59:18.13343 - current node:
>
>
'
'
>
>
So investigating that might be useful. Are you running any other Erlang
>
projects on your node?
>
>
When you run `chef-server-ctl stop`, look for Erlang vms via
>
>
`ps -ef|grep [b]eam`
>
>
Are there any running?
>
>
+ seth
>
>
--
>
Seth Falcon | Development Lead | CHEF | http://www.getchef.com/ | @sfalcon
Archive powered by MHonArc 2.6.16.