CouchDB Dies Once a Week


#1

We have been using chef for a few months now and we had noticed that every once
in awhile chef-server will not respond and the chef-server-webui will not load.

We found this was because couchDB was dead with no errors in its logs at
/var/log/couchdb/couch.log.

Since the server is a VM and our company sometimes needs to restart them for
maintenance we thought it might be that couch wasn’t starting on startup but
chkconfig shows it is ‘on’ for 2-5.

Restarting couchDB and if necessary chef-server fixed the issue, but I was
wondering if anyone else had come across this issue?

OS: RHEL 5.5 x64
Chef: 0.10.4

Chef-Server was installed using the packages here (http://rbel.frameos.org/)


#2

After upgrade to latest version of couchdb (1.0.1), add more memory to the server (4GB), compact the db very day, make sure that there is always
free disk space for db and log, then the problem was gone. I have couchdb with database of 30 GB up for nearly half year

-----Mensaje original-----
De: bjbq4d@gmail.com [mailto:bjbq4d@gmail.com]
Enviado el: miércoles, 04 de enero de 2012 17:48
Para: chef@lists.opscode.com
Asunto: [chef] CouchDB Dies Once a Week

We have been using chef for a few months now and we had noticed that every once in awhile chef-server will not respond and the chef-server-webui will not load.

We found this was because couchDB was dead with no errors in its logs at /var/log/couchdb/couch.log.

Since the server is a VM and our company sometimes needs to restart them for maintenance we thought it might be that couch wasn’t starting on startup but chkconfig shows it is ‘on’ for 2-5.

Restarting couchDB and if necessary chef-server fixed the issue, but I was wondering if anyone else had come across this issue?

OS: RHEL 5.5 x64
Chef: 0.10.4

Chef-Server was installed using the packages here (http://rbel.frameos.org/)

ADVERTENCIA LEGAL
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información confidencial y/o sujeta al secreto profesional, cuya
divulgación no está permitida por la ley. Si no es vd. el destinatario de
este mensaje o lo ha recibido por error, queda informado de que la lectura,
utilización, divulgación y/o copia de este mensaje, cualquiera que fuera su
finalidad, está prohibida por la ley. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción. El correo electrónico y las comunicaciones por
medio de Internet no permiten asegurar la confidencialidad de los mensajes
que se transmiten ni su integridad o correcta recepción. Si no consintiese
la utilización del correo electrónico, le rogamos nos lo comunique de forma
inmediata. ING DIRECT no asume ninguna responsabilidad por estas
circunstancias.

LEGAL WARNING
This message is intended exclusively for its addressee and may contain
information that is CONFIDENTIAL and/or protected by a professional
privilege, protected from disclosure by law. If you are not the intended
recipient or you have received it in error, you are hereby notified that
any read, dissemination, disclosure and/or copy of this message, for any
purpose, is strictly prohibited by law. If this message has been received
in error, please immediately notify us vía e-mail and delete it. E-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent. Should you not agree to the use of
e-mail, you are kindly requested to notify us immediately. ING DIRECT does
not assume any liability for those circumstances.


#3

Did you check other system logs (e.g. dmesg) for OOM killer messages?
I saw that when running a test chef server a month or so ago.

-Peter

On Wed, Jan 4, 2012 at 11:48 AM, bjbq4d@gmail.com wrote:

We have been using chef for a few months now and we had noticed that every once
in awhile chef-server will not respond and the chef-server-webui will not load.

We found this was because couchDB was dead with no errors in its logs at
/var/log/couchdb/couch.log.

Since the server is a VM and our company sometimes needs to restart them for
maintenance we thought it might be that couch wasn’t starting on startup but
chkconfig shows it is ‘on’ for 2-5.

Restarting couchDB and if necessary chef-server fixed the issue, but I was
wondering if anyone else had come across this issue?

OS: RHEL 5.5 x64
Chef: 0.10.4

Chef-Server was installed using the packages here (http://rbel.frameos.org/)


#4

I did not. But I don’t see anything that stands out.

On Wed, Jan 4, 2012 at 1:01 PM, Peter Norton pn+chef-list@knewton.comwrote:

Did you check other system logs (e.g. dmesg) for OOM killer messages?
I saw that when running a test chef server a month or so ago.

-Peter

On Wed, Jan 4, 2012 at 11:48 AM, bjbq4d@gmail.com wrote:

We have been using chef for a few months now and we had noticed that
every once
in awhile chef-server will not respond and the chef-server-webui will
not load.

We found this was because couchDB was dead with no errors in its logs at
/var/log/couchdb/couch.log.

Since the server is a VM and our company sometimes needs to restart them
for
maintenance we thought it might be that couch wasn’t starting on startup
but
chkconfig shows it is ‘on’ for 2-5.

Restarting couchDB and if necessary chef-server fixed the issue, but I
was
wondering if anyone else had come across this issue?

OS: RHEL 5.5 x64
Chef: 0.10.4

Chef-Server was installed using the packages here (
http://rbel.frameos.org/)


-Bryan