check the pidfile (might be empty). If so, just kill the beam.smp processes. There's a known issue with pidfile management on first startup on some OS's.
B. On 9 August 2013 10:45, Andrey Kuprianov <[email protected]> wrote: > Hi guys, > > Im having trouble stopping couchdb service using the 'service couchdb > stop'. I've just installed fresh couhdb-1.3.1 with couchdb-lucene 0.10.0 on > Ubuntu 12.04 LTS and saw that couchdb log is full of eaddrinuse error again. > > netstat -anlp | grep 5984 was showing this: > > tcp 0 0 0.0.0.0:5984 0.0.0.0:* LISTEN > 30992/beam.smp > tcp 0 0 10.248.7.104:34314 10.248.14.201:5984 > ESTABLISHED 30992/beam.smp > tcp 0 0 10.248.7.104:41687 10.248.14.201:5984 > TIME_WAIT - > tcp 0 0 10.248.7.104:39102 10.248.14.201:5984 > ESTABLISHED 30992/beam.smp > > The service script also doesnt print out any status about whether couch is > running or not, so it seems like it's a dangling process. Any ideas? > > Andrey
