If it's not the host it might be that what you think is CouchDB running, is really heart trying to (re)start it.
The start script just calls another wrapper which in itself just tries to start CouchDB and reports that. It doesn't actually report if the launch procedure completes. I'd enable stderr and stdout logging – on Ubuntu, that is in /etc/default/couchdb – not sure where that is on Redhat. But these files usually give you a good idea on where it's stuck. I'm guessing a source install usually puts it in /usr/local/etc/default/couchdb. Till On Friday, June 22, 2012 at 11:10 AM, Daniel L wrote: > By default it binds to 127.0.0.1, can you go into terminal on that server and > try > > curl http://127.0.0.1:5984 > > > Thanks. > Daniel > > On 22/06/2012, at 8:49 AM, [email protected] (mailto:[email protected]) wrote: > > > Hi, > > I built couchdb1.2 from source on RHEL6 because the available couchDB > > version from RHEL6 is old (1.0.xx). > > > > I installed all the latest version of pre-requisites: erlang, curl, > > spidermonkey, icu > > > > ./configure, make and make install --> all passed > > service start couched --> NO error message, it shows "Starting database > > server couched" > > > > ps -ef shows couched is running, but it never binds to 5984. > > > > service stop couched never stops couchdb either. > > > > Banged my head against the wall whole day today. > > > > Help please. > > Peter > > > > -- > > View this message in context: > > http://couchdb-development.1959287.n2.nabble.com/RHEL6-couchdb1-2-startup-failed-tp7580473.html > > Sent from the CouchDB Development mailing list archive at Nabble.com > > (http://Nabble.com). > > > > >
