Hi,
I have a chef server installed on an tiny EC2 instance which I am able
to run once, however on terminating/restarting I find that the
chef-expander process is in a die-restart loop.
The startup log suggests it is an issue around starting the database.
startup_log, startup_err, erl_crash.dump and rabbit.log are here:
I’m also seeing the following error periodically (about 50% of
occasions) when installing the Chef server via the chef-solo bootstrap
described on the opscode wiki/site:
Has anyone experienced this and have a solution, or can suggest what
might be the cause of this?
Best wishes.
–
πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC) http://hedgehogshiatus.com
On Sunday, June 26, 2011 at 5:24 AM, Hedge Hog wrote:
Hi,
I have a chef server installed on an tiny EC2 instance which I am able
to run once, however on terminating/restarting I find that the
chef-expander process is in a die-restart loop.
The startup log suggests it is an issue around starting the database.
startup_log, startup_err, erl_crash.dump and rabbit.log are here: Chef server 0.10.0 startup failure · GitHub
I'm also seeing the following error periodically (about 50% of
occasions) when installing the Chef server via the chef-solo bootstrap
described on the opscode wiki/site: Chef server install via Chef-solo · GitHub
Has anyone experienced this and have a solution, or can suggest what
might be the cause of this?
No idea what the cause is. You can try clearing out rabbitmq's database, I believe this will be in /var/lib/rabbitmq/mnesia/rabbit. You can simply rm the files/dirs in there.
--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC) http://hedgehogshiatus.com
Has anyone experienced this and have a solution, or can suggest what
might be the cause of this?
I experienced problems too with a Chef server installed via the
chef-server cookbook. What happens is that all the different services
needed for Chef to run should be started and running before Chef
itself, in the correct order. I was able to resolve it by changing the
boot order of the init.d processes. Have a look at my more elaborate
explanation in ticket CHEF-2318
Has anyone experienced this and have a solution, or can suggest what
might be the cause of this?
I experienced problems too with a Chef server installed via the
chef-server cookbook. What happens is that all the different services
needed for Chef to run should be started and running before Chef
itself, in the correct order. I was able to resolve it by changing the
boot order of the init.d processes. Have a look at my more elaborate
explanation in ticket CHEF-2318
--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC) http://hedgehogshiatus.com