couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Candler <B.Cand...@pobox.com>
Subject Re: CouchDB failing to open socket 5984 ?
Date Wed, 09 Sep 2009 13:44:38 GMT
This is turning out to be very odd.

I built a whole new VM using ubuntu jaunty server and couchdb from svn, and
it works fine.

Back to my hardy box (using erlang from jaunty), I've rebuilt again with the
latest couchdb, r812951, and it's the same problem as before.

I've added "set -x" to the top of /usr/local/bin/couchdb. This gives the
following:

$ sudo -i -u couchdb couchdb
+ BACKGROUND=false
+ DEFAULT_CONFIG_DIR=/usr/local/etc/couchdb/default.d
+ DEFAULT_CONFIG_FILE=/usr/local/etc/couchdb/default.ini
+ HEART_BEAT_TIMEOUT=11
+ HEART_COMMAND='/usr/local/bin/couchdb -k'
+ INTERACTIVE=false
+ KILL=false
+ LOCAL_CONFIG_DIR=/usr/local/etc/couchdb/local.d
+ LOCAL_CONFIG_FILE=/usr/local/etc/couchdb/local.ini
+ PID_FILE=/usr/local/var/run/couchdb/couchdb.pid
+ RECURSED=false
+ RESET_CONFIG=true
+ RESPAWN_TIMEOUT=0
+ SCRIPT_ERROR=1
+ SCRIPT_OK=0
+ SHUTDOWN=false
+ STDERR_FILE=couchdb.stderr
+ STDOUT_FILE=couchdb.stdout
+ print_arguments=
+ start_arguments=
+ background_start_arguments=
++ basename couchdb
+ basename=couchdb
+ parse_script_option_list
+ _load_config
+ _add_config_file /usr/local/etc/couchdb/default.ini
+ test -z ''
+ print_arguments=/usr/local/etc/couchdb/default.ini
+ start_arguments=' /usr/local/etc/couchdb/default.ini'
+ background_start_arguments=' -a /usr/local/etc/couchdb/default.ini'
+ _add_config_dir /usr/local/etc/couchdb/default.d
++ find /usr/local/etc/couchdb/default.d -mindepth 1 -maxdepth 1 -type f -name '*.ini'
+ _add_config_file /usr/local/etc/couchdb/local.ini
+ test -z /usr/local/etc/couchdb/default.ini
++ cat
+ print_arguments='/usr/local/etc/couchdb/default.ini
/usr/local/etc/couchdb/local.ini'
+ start_arguments=' /usr/local/etc/couchdb/default.ini /usr/local/etc/couchdb/local.ini'
+ background_start_arguments=' -a /usr/local/etc/couchdb/default.ini -a /usr/local/etc/couchdb/local.ini'
+ _add_config_dir /usr/local/etc/couchdb/local.d
++ find /usr/local/etc/couchdb/local.d -mindepth 1 -maxdepth 1 -type f -name '*.ini'
+ set +e
++ getopt hVa:A:ncibp:r:Ro:e:skd
+ options=' --'
+ test '!' 0 -eq 0
+ set -e
+ eval set -- --
++ set -- --
+ '[' 1 -gt 0 ']'
+ case "$1" in
+ shift
+ break
+ test false = true -o false = true
+ start_couchdb
+ test '!' false = true
+ check_status
+ check_environment
+ test false '!=' true
+ return
+ interactive_option='+Bd -noinput'
+ test false = true
+ test false = true
+ command='/usr/bin/erl +Bd -noinput -sasl errlog_type error +K true         -env ERL_LIBS
/usr/local/lib/couchdb/erlang/lib -couch_ini  /usr/local/etc/couchdb/default.ini /usr/local/etc/couchdb/local.ini
-s couch'
+ test false = true -a false = false
+ test false = true
+ eval exec /usr/bin/erl +Bd -noinput -sasl errlog_type error +K true -env ERL_LIBS /usr/local/lib/couchdb/erlang/lib
-couch_ini /usr/local/etc/couchdb/default.ini /usr/local/etc/couchdb/local.ini -s couch
++ exec /usr/bin/erl +Bd -noinput -sasl errlog_type error +K true -env ERL_LIBS /usr/local/lib/couchdb/erlang/lib
-couch_ini /usr/local/etc/couchdb/default.ini /usr/local/etc/couchdb/local.ini -s couch

At this point it just stops.

In another window:

$ ps auxwww | grep couch
couchdb  19955  0.1  0.9   9160  5060 pts/5    Sl+  14:32   0:00 /usr/lib/erlang/erts-5.6.5/bin/beam
-Bd -K true -- -root /usr/lib/erlang -progname erl -- -home /usr/local/var/lib/couchdb -noshell
-noinput -sasl errlog_type error -couch_ini /usr/local/etc/couchdb/default.ini /usr/local/etc/couchdb/local.ini
-s couch
candlerb 22345  0.0  0.1   3008   756 pts/4    R+   14:34   0:00 grep couch
$ telnet localhost 5984
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
$ 

Looking at the timestamps confirms that /usr/local/bin/couchdb and
/usr/local/etc/couchdb/default.ini have been updated by make install.

No couchdb.stdout or couchdb.stderr is created, even if I cd to a directory
owned by couchdb first.

I guess I could try rm -rf'ing everything couchdb-related on this box and
starting again, but I'll keep it like this for now in case anyone has any
ideas for things to try.

Regards,

Brian.

Mime
View raw message