Which versions of CouchDB and Chef are you running? The Couch release
packaged for CentOS 5 (0.11.5, I think?) is quite ancient and known to have
such issues. If you’re having this problem in a post-1.0 release, that would
be more interesting.
That said – I’ve had a crashing CouchDB (pre-1.0), and no component other
than CouchDB itself has needed restart. (Further, if you use the
bootstrap-server recipe to deploy your server, Couch – like other
components – will be under process supervision and automatically
On Thu, Feb 24, 2011 at 2:43 AM, firstname.lastname@example.org wrote:
I have experienced multi crashes of couchdb on my chef-server. I dont know
why, there is no log, no trace no indication from couchdb.
My database is around 30 GB and the server is redhat 5.5 having 3 GB
I heard that erlang sometime kill processes dueto lack of resource or other
contention, and restart them automatically. But in my case
the couchdb process (mochiweb I think) that faciliates database access via
http simply dies and I have restart couchdb entirely.
But the problem from Chef side is that Chef server can not re-connect to
couchdb again and I have to restart chef-server-api then chef-server-webui
Anyone is facing similar problem?
**Tecnología **ING DIRECT
**Administrador de sistema
*Tel: +34 91 206 76 85
Por favor, no imprima este correo si no es necesario.
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.