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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: couchdb (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024924
Title:
`s
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
sudo /etc/init.d/couchdb stop
--
You r
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024924
Title:
`sudo /etc/init.d/couchdb stop` fails, doesn't kill couchdb
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
