- From: Hedge Hog <
>
- To:
- Subject: [chef] Chef server bootstrap via chef-solo and startup
- Date: Sun, 26 Jun 2011 22:24:48 +1000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=EfiJPbP9NoBNx9N1IgWYRSV1Z0sggEmdm33TwwmJnF4FcgQt5ZApt1lBL1eC3Z5aej YINccJGlciK2UKMInkB9PxJssgHRSKeyKA9bQ2D+txDtvDFXM8nuSOLBRgFbVQ9M5LIM /ZXsH8itS7X6ZNBB5DWL3rFC4/IT6IDjKBJRo=
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:
https://gist.github.com/1047284
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:
https://gist.github.com/1047565
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
- [chef] Chef server bootstrap via chef-solo and startup, Hedge Hog, 06/26/2011
Archive powered by MHonArc 2.6.16.