** Changed in: couchdb (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage notifica
This bug was fixed in the package couchdb - 1.6.0-0ubuntu5.1
---
couchdb (1.6.0-0ubuntu5.1) vivid; urgency=medium
* Add debian/couchdb.service to start system-wide CouchDB instance via
systemd (LP: #1457464)
* debian/rules: call dh --with systemd
* debian/control: Add `dh-sy
Everything checks out for me. Testing I did:
1) Installed couchdb 1.6.0-0ubuntu5, enabled proposed, made sure there
were no issue upgrading to 1.6.0-0ubuntu5.1 and that couchdb was
actually running after the upgrade
2) Made sure `apt-get remove/purge couchdb` works without issue, stops
couchdb pr
** Branch linked: lp:ubuntu/vivid-proposed/couchdb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage notifications about this
Hello Christian, or anyone else affected,
Accepted couchdb into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/couchdb/1.6.0-0ubuntu5.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Branch linked: lp:ubuntu/couchdb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage notifications about this bug go to:
htt
This bug was fixed in the package couchdb - 1.6.0-0ubuntu6
---
couchdb (1.6.0-0ubuntu6) wily; urgency=medium
* Add debian/couchdb.service to start system-wide CouchDB instance via
systemd (LP: #1457464)
* debian/rules: call dh --with systemd
* debian/control: Add `dh-systemd
Sponsored vivid update to SRU review queue.
** Changed in: couchdb (Ubuntu Vivid)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to s
** Changed in: couchdb (Ubuntu Wily)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manag
Now that things have been sorted out for Wily (pending sponsorship
still), I'd like to get this fixed in Vivid also, assuming this is an
SRU-able change.
Here's my merge proposal for Vivid:
https://code.launchpad.net/~jderose/ubuntu/vivid/couchdb/fix-1457464/+merge/264437
** Branch linked: lp:~jd
** Changed in: couchdb (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage notifications
Replied on the MP. After this lands, please forward the debdiff to the
Debian bug as well. Thanks!
** Bug watch added: Debian Bug tracker #723726
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723726
** Also affects: couchdb (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=72
Martin, thanks for explaining Wants=/After=network-online.target.
I couldn't seem to get couchdb to *not* start based on what I was doing
with network-manager. I tried unchecking "Enable Networking" in the
indicator and rebooting, couchdb still started. I also tried rebooting
when networking was e
It's ok to have Wants=/After=network-online.target, just that couchdb
might start very late in the boot. In some cases, like you *only* use
NetworkManager and aren't online, it will *never* happen though, and
couchdb won't run at all. That's presumably not a big use case for
servers with remotely a
Martin,
Thanks for your recommendations! Much cleaner now.
So do you think I just totally drop Wants=/After=network-online.target?
My rational for this is if (for whatever reason) someone wanted to bind
CouchDB to a specific IP, say on a server with multiple NICs for
internal and external traff
Of course, if you have a proper systemd unit that's always better. But
some suggestions:
> [Unit]
> Description=the system-wide CouchDB instance
Please drop the "the" and start with a capital letter for some
consistency.
> After=network-online.target
Is that really necessary? I. e. couchdb does
Sticking this into /lib/systemd/system/couchdb.service and "sudo
systemctl enable couchdb" seems to work:
$ systemctl status -l couchdb
● couchdb.service - System-wide CouchDB instance
Loaded: loaded (/lib/systemd/system/couchdb.service; enabled; vendor preset:
enabled)
Active: active (run
Martin, do you have any thoughts on this? I got the impression you added
the upstream SysV init script back as a quick stop-gap... but do you see
any reason we shouldn't start CouchDB via debian/couchdb.service
instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Branch linked: lp:~jderose/ubuntu/wily/couchdb/fix-1457464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage notifications
Making decent progress, this is my current debian/couchdb.service:
[Unit]
Description=the system-wide CouchDB instance
After=network-online.target
[Service]
Type=simple
ExecStartPre=/bin/mkdir -p /run/couchdb
ExecStartPre=/bin/chown couchdb:couchdb /run/couchdb
ExecStart=/bin/su couchdb -c /usr/b
I didn't have a chance to keep up with the systemd transition for
CouchDB in Vivid, but I'm working on getting this fixed properly for
Wily.
I've long had subtle problems with the upstream SysV init script
(especially when it comes to getting `apt-get purge couchdb` to work
correctly), and this wa
Er, I meant "and X, of course"... obviously we want couchdb in good
shape for the next LTS :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade t
The hint of Tobias worked for me, but I had to reown the database files
in /var/lib/couchdb to "couchdb" that I have created running CouchDB as
root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14574
Reowning was not the problem since /etc/init.d/couchdb does this by default if
any user variable is set.
note that there is no default config file /etc/default/couchdb
in this case neither stdout nor user variables are given and couchdb assumes
stdout = /couchdb.log and
stderr = /couchdb.err
I ad
Removing the inclusion of /lib/lsb/init-functions in /etc/init.d/couchdb
solved the problem for me.
But make sure that everything is owned by couchdb:
chown -R couchdb /var/log/couchdb
chown -R couchdb /var/run/couchdb
chown -R couchdb /var/lib/couchdb
chown -R couchdb /etc/couchdb
--
You recei
I see that the package creates a couchdb system user, and it appears the
init script is correctly running Couch as that user.
So, when I do `sudo -u couchdb couchdb`, I can see /var/run/couchdb is
incorrectly owned by root:
$ sudo -u couchdb couchdb
Apache CouchDB 1.6.0 (LogLevel=info) is
** Changed in: couchdb (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457464
Title:
Init fails to start CouchDB after upgrade to Vivid
To manage notifica
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/1457464
Title:
In
28 matches
Mail list logo
