Scott, good call. That was definitely a red herring.
So this appears to be a circular dependency problem with dpkg... because
zookeeperd -> zookeeper -> default-jre-headless -> openjdk-7-jre-
headless
This should always guarantee that openjdk-7-jre-headless is configured
before zookeeperd. Instead it is somehow being configured *after*
default-jre-headless and thus, the alternatives are not set up.
There is a workaround.. if you install with --no-install-recommends
The order is correct.
This also exposes two other bugs to me:
1) /var/lib/zookeeper should belong to zookeeper
2) the upstart job should be reporting the failure, not 'start/running'
** Changed in: zookeeper (Ubuntu)
Status: In Progress => Triaged
** Changed in: zookeeper (Ubuntu)
Assignee: Clint Byrum (clint-fewbar) => (unassigned)
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- zookeeperd not running after installation of zookeeperd
+ circular dependency causes zookeeperd to not be running after installation of
zookeeperd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1007433
Title:
circular dependency causes zookeeperd to not be running after
installation of zookeeperd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1007433/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
