incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Devon Weller <>
Subject Re: /etc/init.d/couchdb stop never really stops the db
Date Thu, 19 Nov 2009 19:23:23 GMT

I had a similar problem on Centos 5.4.

For me, it was a permissions issue on the log directory.  The  
directory of /usr/local/var/log/couchdb was owned by root and did not  
have write permissions for the couchdb user.  As a result couchdb  
never fully started and could only be killed with manually.

The solution for me was to:

chgrp couchdb /usr/local/var/log/couchdb && chmod g+w /usr/local/var/ 

This might need to be fixed in the Makefile.  It might need to know  
the name of the user that couchdb will run under and change  
permissions of the log directory on "make install".  Perhaps it needs  
an option like with-user=couchdb.

- Devon

On Nov 10, 2009, at 1:41 PM, Robert Campbell wrote:

> I've run 0.8.0 and now 0.10.0 on Ubuntu 9.04/9.10 server and in both
> cases calling stop never actually stopped the DB. The only way I've
> gotten around it in the past is manually killing the couchdb
> processes. Why doesn't stop work for me?
> I've installed it via "apt-get install couchdb" and the only thing
> I've modified is local.ini, BindAddress= to get remote access
> working. Nothing else was ever changed.

View raw message