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
Here is me running couchdb -b three times w/ps -A | grep couchdb:
r...@default:~# couchdb -b
Apache CouchDB has started, time to relax.
r...@default:~# couchdb -b
Apache CouchDB has started, time to relax.
r...@default:~# ps -A | grep couchdb
4389 ?00:00:00 couchdb
4419 ?
Also it could be useful to add -p /path/to/pid_file in each case.
r...@default:~# couchdb -b -p /var/run/couchdb
Apache CouchDB needs a regular PID file: /var/run/couchdb
Just to clarify, I'm running Ubuntu 9.10 on Slicehost. I ran apt-get
install couchdb when I first got the slice, and the
On Wed, Nov 11, 2009 at 1:54 PM, Robert Campbell rrc...@gmail.com wrote:
Here is me running couchdb -b three times w/ps -A | grep couchdb:
r...@default:~# couchdb -b
Apache CouchDB has started, time to relax.
r...@default:~# couchdb -b
Apache CouchDB has started, time to relax.
_-d_ is the
Sorry, I screwed that up. I saw the d as b for some reason. Here's the
results from -d:
r...@default:~# ps -A | grep couchdb
4389 ?00:00:00 couchdb
4419 ?00:00:00 couchdb
6399 ?00:00:05 couchdb
r...@default:~# couchdb -d
r...@default:~# ps -A | grep couchdb
4389 ?
On Wed, Nov 11, 2009 at 2:54 PM, Robert Campbell rrc...@gmail.com wrote:
Sorry, I screwed that up. I saw the d as b for some reason. Here's the
results from -d:
r...@default:~# ps -A | grep couchdb
4389 ? 00:00:00 couchdb
4419 ? 00:00:00 couchdb
6399 ? 00:00:05
@Mikhail - but when I tried to specify the PID file I found in
/var/run, it didn't work:
r...@default:~# couchdb -b -p /var/run/couchdb
Apache CouchDB needs a regular PID file: /var/run/couchdb
I just want the init.d scripts to work as they're supposed to. Is
there some special trick you have to
On Wed, Nov 11, 2009 at 4:53 PM, Robert Campbell rrc...@gmail.com wrote:
@Mikhail - but when I tried to specify the PID file I found in
/var/run, it didn't work:
r...@default:~# couchdb -b -p /var/run/couchdb
Apache CouchDB needs a regular PID file: /var/run/couchdb
Look inside that file -
I can verify same issues on both 32 and 64 bit 9.10 installs.
Also... try /etc/init.d/couchdb restart... watch what happens to the log
file.
My log file filled up to over a gig, overnight. All with errors because
couchdb never stopped - but it kept trying to restart and getting a port in
use
On 11 Nov 2009, at 11:54, Robert Campbell wrote:
Sorry, I screwed that up. I saw the d as b for some reason. Here's the
results from -d:
r...@default:~# ps -A | grep couchdb
4389 ?00:00:00 couchdb
4419 ?00:00:00 couchdb
6399 ?00:00:05 couchdb
r...@default:~# couchdb -d
On 11 Nov 2009, at 13:53, Robert Campbell wrote:
@Mikhail - but when I tried to specify the PID file I found in
/var/run, it didn't work:
r...@default:~# couchdb -b -p /var/run/couchdb
Apache CouchDB needs a regular PID file: /var/run/couchdb
You likely don't have permissions to do this.
Hi Noah, here is the result of running couchdb -d after the change:
r...@default:/usr/bin$ ps -A | grep couchdb
4389 ?00:00:00 couchdb
4419 ?00:00:00 couchdb
6399 ?00:00:07 couchdb
r...@default:/usr/bin$ couchdb -d
+ BACKGROUND=false
+
Noah, here is the result of the PID run as the couchdb user:
r...@default:/usr/bin$ sudo -u couchdb couchdb -b -p /var/run/couchdb
+ BACKGROUND=false
+ DEFAULT_CONFIG_DIR=/etc/couchdb/default.d
+ DEFAULT_CONFIG_FILE=/etc/couchdb/default.ini
+ HEART_BEAT_TIMEOUT=11
+ HEART_COMMAND=/usr/bin/couchdb
On Wed, Nov 11, 2009 at 6:33 PM, Noah Slater nsla...@tumbolia.org wrote:
On 11 Nov 2009, at 14:15, Mikhail A. Pokidko wrote:
To build package for ALTLinux i had to rewrite init-script completely.
Why? Is there a patch you could send up-stream? Thanks.
Well, i guess it is kinda ALT-specific.
Can you make sure and kill the existing beam processes and rerunning this?
On Wed, Nov 11, 2009 at 10:37 AM, Robert Campbell rrc...@gmail.com wrote:
Hi Noah, here is the result of running couchdb -d after the change:
r...@default:/usr/bin$ ps -A | grep couchdb
4389 ? 00:00:00 couchdb
On 11 Nov 2009, at 15:37, Robert Campbell wrote:
/usr/bin/couchdb: 1: cannot create /var/run/couchdb/couchdb.pid:
Permission denied
This looks key.
Check the ownership of that file.
Check the user you are running CouchDB as.
You probably need to run all CouchDB commands with this
On 11 Nov 2009, at 15:39, Robert Campbell wrote:
Apache CouchDB needs write permission on the STDOUT file:
couchdb.stdout
If you don't specify a PID file on the command line, it tries to write
it to the current directory.
If the couchdb user doesn't have the permissions to do that, it
On 11 Nov 2009, at 16:11, Mikhail A. Pokidko wrote:
Well, i guess it is kinda ALT-specific.
http://git.altlinux.org/people/pma/packages/couchdb.git?p=couchdb.git;f=couch.init;hb=0.10.x-alt
So nothing we should pull upstream?
On Wed, Nov 11, 2009 at 7:24 PM, Noah Slater nsla...@tumbolia.org wrote:
On 11 Nov 2009, at 16:11, Mikhail A. Pokidko wrote:
Well, i guess it is kinda ALT-specific.
http://git.altlinux.org/people/pma/packages/couchdb.git?p=couchdb.git;f=couch.init;hb=0.10.x-alt
So nothing we should pull
On 10 Nov 2009, at 19:41, 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
r...@default:/etc/init.d# ./couchdb stop
+ SCRIPT_OK=0
+ SCRIPT_ERROR=1
+ DESCRIPTION=database server
+ NAME=couchdb
+ basename ./couchdb
+ SCRIPT_NAME=couchdb
+ COUCHDB=/usr/bin/couchdb
+ CONFIGURATION_FILE=/etc/default/couchdb
+ RUN_DIR=/var/run/couchdb
+ LSB_LIBRARY=/lib/lsb/init-functions
+
On Wed, Nov 11, 2009 at 2:31 AM, Noah Slater nsla...@tumbolia.org wrote:
Great, what happens when you do:
couchdb -b
Is CouchDB running?
What happens when you do this next:
couchdb -d
Has CouchDB stopped?
Also it could be useful to add -p /path/to/pid_file in each case.
22 matches
Mail list logo
