You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Martin Hewitt <ma...@thenoi.se> on 2011/03/11 13:53:50 UTC
CouchDB listening host & port
Hi all,
I can't get to Futon from the world-wide-web on one of my servers. I have two identical servers, configured exactly as each other, but, on one, if I run the command:
netstat --listen | grep 5984
tcp 0 0 *:5984 *:* LISTEN
And on the other, I get
tcp 0 0 localhost:5984 *:* LISTEN
Now, in both local.ini and default.ini I have
port = 5984
bind_address = 0.0.0.0
Is that the only setting I need to use/alter to get it to listen widely, or is there another option I'm missing? If not, is there a way to find out which files CouchDB used to configure itself?
The only thing I've noticed is that
cat /usr/local/var/run/couchdb/couch.uri
Shows
http://127.0.0.1:5984/
on the inaccessible server, and
http://0.0.0.0:5984/
on the other.
Is it safe to modify couch.uri? Should I delete this file and restart couch so it rebuilds it?
Any help would be greatly appreciated.
Many thanks,
Martin
Re: CouchDB listening host & port
Posted by Martin Hewitt <ma...@thenoi.se>.
Turns out i was editing:
/usr/local/etc/couchdb/local.ini
/usr/local/etc/couchdb/default.ini
when I should've been editing
/etc/couchdb/local.ini
/etc/couchdb/default.ini
Relics from a yum-based install, I think.
Martin
On 11 Mar 2011, at 12:53, Martin Hewitt wrote:
> Hi all,
>
> I can't get to Futon from the world-wide-web on one of my servers. I have two identical servers, configured exactly as each other, but, on one, if I run the command:
>
> netstat --listen | grep 5984
>
> tcp 0 0 *:5984 *:* LISTEN
>
> And on the other, I get
>
> tcp 0 0 localhost:5984 *:* LISTEN
>
> Now, in both local.ini and default.ini I have
>
> port = 5984
> bind_address = 0.0.0.0
>
> Is that the only setting I need to use/alter to get it to listen widely, or is there another option I'm missing? If not, is there a way to find out which files CouchDB used to configure itself?
>
> The only thing I've noticed is that
>
> cat /usr/local/var/run/couchdb/couch.uri
>
> Shows
>
> http://127.0.0.1:5984/
>
> on the inaccessible server, and
>
> http://0.0.0.0:5984/
>
> on the other.
>
> Is it safe to modify couch.uri? Should I delete this file and restart couch so it rebuilds it?
>
> Any help would be greatly appreciated.
>
> Many thanks,
>
> Martin