Description of problem: zookeeper-server on fc20 silently fails to start after a fresh install due to unit file precondition on missing file . Version-Release number of selected component (if applicable): zookeeper-server-3.4.5-12.fc20.noarch Steps to Reproduce: 1. Fresh install of fc20 2. install zookeeper-server (and zookeeper?) 3. sudo cp /etc/zoo-sample.cfg /etc/zoo.cfg 4. sudo systemctl start zookeeper 5. journalctl -f shows: ``` Dec 14 14:18:32 localhost.localdomain systemd[1]: Started Apache ZooKeeper. ``` Actual results: The service has aborted when trying to start, the errors it reported are not logged to the journal nor /var/log/zookeeper/* Expected results: the service should be running, or log an error to the journal. Additional info: ``` % cat /usr/lib/systemd/system/zookeeper.service ... ConditionPathExists=/var/lib/zookeeper/data/myid ``` Creating /var/lib/zookeeper/data/myid and chowning it over to zookeeper makes the next restart "stick" and zookeeper then logs to the journal (too verbosely, btw). I've found nothing on setting up zookeeper-server on fedora on google, but I'm new here, I may have missed it. So no docs on what is myid or what's it for, zookeeper runs fine without it if it's launched manually.
I think myid is a typo ``` ConditionPathExists=/var/lib/zookeeper/data ```
myid is used with clustered setup. http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_zkMulitServerSetup
The RPM claims to include both /etc/zookeeper/zoo.cfg and /var/lib/zookeeper/data/myid, neither of which is actually installed by it.
I've been impacted by this same issue when attempting to use zookeeper with the openstack-ceilometer RDO packages for Juno. Can we get some traction on a fix from the package maintainer? [1] https://openstack.redhat.com/RDO_test_day_Juno_milestone_3
My plan is to update to 3.4.6, work has already been in-progress.
zookeeper-3.4.6-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/zookeeper-3.4.6-1.fc21
I revamped the entire package and updated to use ivy-local resolver, which is only available in f22. F21 currently has issues around objectweb-asm which are a result of the fedora-java modifications. It is possible to rebuild the zookeeper-3.4.6-package on f20 but you need to install the fedora 21 - javapackages-tools. Updated builds have been tested, using the following instructions: https://cwiki.apache.org/confluence/display/solr/Setting+Up+an+External+ZooKeeper+Ensemble
revised: ivy-local resolver, which is only available in f21.
Package zookeeper-3.4.6-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing zookeeper-3.4.6-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13460/zookeeper-3.4.6-1.fc21 then log in and leave karma (feedback).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.