You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Paul Davis <pa...@gmail.com> on 2009/10/04 21:34:23 UTC
Re: Starting CouchDB on Ubuntu (trunk rev 821585)
What's the IP you listed for the bind_address? Did you perhaps specify
something like 192.168.10.1? If so that means CouchDB isn't listening
on 127.0.0.1.
To check if the port is open, try:
$ netstat -tap tcp | grep 5984
HTH,
Paul Davis
On Sun, Oct 4, 2009 at 3:29 PM, Andreas Wenk
<a....@netzmeister-st-pauli.de> wrote:
> Hi there,
>
> I have some trouble getting CouchDB to start.
>
> I have a local Ubuntu (Linux duke 2.6.28-15-generic #49-Ubuntu SMP Tue Aug
> 18 18:40:08 UTC 2009 i686 GNU/Linux) and CouchDB trunk (rev 821585). As
> usual, I followed the advice in the README (adduser, chmod, chown). Now
> starting CouchDB:
>
> $ sudo -i -u couchdb couchdb -b
> Apache CouchDB has started, time to relax.
>
> $ ps -ef
> couchdb 9203 1 0 21:21 pts/1 00:00:00 /bin/sh -e
> /usr/local/bin/couchdb -a /usr/local/etc/couchdb/default.ini -a /
> couchdb 9212 9203 0 21:21 pts/1 00:00:00 /bin/sh -e
> /usr/local/bin/couchdb -a /usr/local/etc/couchdb/default.ini -a /
> couchdb 9213 9212 4 21:21 pts/1 00:00:00
> /usr/local/lib/erlang/erts-5.7.3/bin/beam -Bd -K true -- -root /usr/local/li
> couchdb 9218 9213 0 21:21 ? 00:00:00 heart -pid 9213 -ht 11
>
> but:
>
> $ curl http://127.0.0.1:5984
> curl: (7) couldn't connect to host
>
> and
>
> $ sudo -i -u couchdb couchdb -d
> Apache CouchDB is not running.
>
> Any idea what's going wrong? I did the same in the office on a VM Debian
> Lenny without having any problems.
>
> Thanks a lot in advance
>
> Cheers
>
> Andy Wenk
>
>
>
>
Re: Starting CouchDB on Ubuntu (trunk rev 821585)
Posted by Andreas Wenk <a....@netzmeister-st-pauli.de>.
Hi Paul,
Paul Davis wrote:
> What's the IP you listed for the bind_address? Did you perhaps specify
> something like 192.168.10.1? If so that means CouchDB isn't listening
> on 127.0.0.1.
it's 127.0.0.1
> To check if the port is open, try:
>
> $ netstat -tap tcp | grep 5984
hm - but no output here
Thanks for the help
Cheers
Andy