** Attachment added: output of 'apt-get install zookeeperd'
https://bugs.launchpad.net/bugs/1007433/+attachment/3171456/+files/apt-get-install.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zookeeper (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
This is reproducible if you purge everything that was installed, and then try
again.
$ addl=ca-certificates-java default-jre-headless fontconfig-config
icedtea-7-jre-cacao icedtea-7-jre-jamvm java-common libavahi-client3
libavahi-common-data libavahi-common3 libcups2 libfontconfig1
I encounter the same issue while trying to use the same image for juju.
If I use a precise image, cloud-init-output.log ends with:
Installed /usr/lib/juju/juju
Processing dependencies for juju==0.5
Finished processing dependencies for juju==0.5
% Total% Received % Xferd Average Speed
** Changed in: zookeeper (Ubuntu)
Importance: Undecided = Medium
--
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:
zookeeperd not running after installation of
I think the problem lies here:
adduser: Warning: The home directory `/var/lib/zookeeper' does not
belong to the user you are currently creating.
But in the packaging:
debian/zookeeper.dirs:/var/lib/zookeeper
Since the package owns the dir, it will be owned by root, which is
wrong.
So the fix
** Branch linked: lp:~clint-fewbar/ubuntu/quantal/zookeeper/fix-
zookeeper-postinst-failure
--
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:
zookeeperd not running
@Clint,
I'm pretty sure the issue is that java is not ready for use when zookeeperd
attempts to start.
Evidence to that fact is that if you install 'default-jre-headless' before
installing zookeeperd, you get functional zookeeper, and you still get the
warning.
I think the issue is that
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
