`sudo /etc/init.d/couchdb stop` fails, doesn't kill couchdb

Bug #1024924 reported by Jason Gerard DeRose
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
couchdb (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Easy to reproduce:

jderose@jgd-ws:~$ sudo apt-get install couchdb
.
.
jderose@jgd-ws:~$ sudo /etc/init.d/couchdb stop
 * Stopping database server couchdb [fail]
jderose@jgd-ws:~$ ps -ef | grep couchdb
couchdb 28779 1 0 04:49 ? 00:00:00 /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/couchdb.pid -o /dev/null -e /dev/null -R
couchdb 28794 28779 0 04:49 ? 00:00:00 /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/couchdb.pid -o /dev/null -e /dev/null -R
couchdb 28795 28794 0 04:49 ? 00:00:00 /usr/lib/erlang/erts-5.8.5/bin/beam.smp -Bd -K true -A 4 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/couchdb -- -noshell -noinput -sasl errlog_type error -couch_ini /etc/couchdb/default.ini /etc/couchdb/local.ini /etc/couchdb/default.ini /etc/couchdb/local.ini -s couch -pidfile /var/run/couchdb/couchdb.pid -heart
couchdb 28811 28795 0 04:49 ? 00:00:00 heart -pid 28795 -ht 11
jderose 28893 14345 0 04:51 pts/1 00:00:00 grep --color=auto couchdb

It would be great to SRU a fix for this because if `/etc/init.d/couchdb stop` doesn't work, it's sort of impossible to gracefully upgrade to a newer CouchDB, which I'm trying to finally make happen for Quantal:

https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1022515

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: couchdb 1.0.1-0ubuntu18
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Sun Jul 15 04:42:25 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120122)
PackageArchitecture: all
SourcePackage: couchdb
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jason Gerard DeRose (jderose) wrote :
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

Hmm, after digging into this further, this bug is very weird. "stop" is only broken immediately after the install. For example, this doesn't work:

sudo apt-get install couchdb
sudo /etc/init.d/couchdb stop

But this does work:

sudo apt-get install couchdb
<reboot>
sudo /etc/init.d/couchdb stop

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in couchdb (Ubuntu):
status: New → Confirmed
Revision history for this message
Bas Grolleman (bgrolleman) wrote :

Got the same issue, killing the couchdb entries and restarting makes it work fine from there.

This does however break my puppet run, because I get a failed to restart couchdb when new configuration is loaded.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.