doesn't seem to auto start on centos/amazon linux about zookeeper-cookbook HOT 7 CLOSED

Hey @aarondodd, sincere apologies for never digging into this. CentOS support is hard to come by for us; we're a strictly Ubuntu shop. However, I'm working on a massive refactor of this cookbook and want to at least try to support CentOS as well. If you can hang on for a short bit, I think we'll get there.

from zookeeper-cookbook.

I can confirm OpsWorks has hard time working with this cookbook as well when running on Amazon Linux. Will be happy to see this resolved!

from zookeeper-cookbook.

Hey @synhershko, so this cookbook has changed quite a lot the past couple months. Do you mind if I ask what version of the cookbook you're on?

from zookeeper-cookbook.

Directly from the master branch...

from zookeeper-cookbook.

Okay, can you provide a stacktrace, test conditions, any debugging information, etc? My comment above has mostly been accomplished, so things which aren't working at this point are likely bugs and we'll probably have to go out of our way to fix 'em up. Thanks!

from zookeeper-cookbook.

Let me retract my comment - it seems to be working fine now. It probably required some more patience on my end.

from zookeeper-cookbook.

I'm still having issues with zookeeper starting when the zookeeper::service recipe is run under OpsWorks with the upstart provider set. The command which the recipe runs is /sbin/start zookeeper, and that fails. Running that manually returns a no such job found error.

Using the runit provider starts the service, but then I get issues with the leader election process because it doesn't seem to have listeners at 2888/3888 for the quorum stuff.

Looks like this recipe doesn't include functionality related to zookeeper clustering, in general. I had to do a supplemental recipe to lay down the myid file, for instance.

More info: Amazon linux uses upstart by default, but initially I kept getting errors when trying to use initctl to manage starting the service. Your recipe is writing zookeeper.conf into /etc/init, but /var/log/messages showed that upstart didn't like either your limit or console stanzas in the conf file.

Commenting out those stanzas made zookeeper show up in initctl list, but the service still failed to start properly, respawning several times and then stopping due to the default respawn limits on init.

Interestingly, rewriting the limit nofile 8192 8192 line in the conf file didn't throw the same stanza error. On the off chance that there was some issue in the file template (like a bad carriage return or some other invisible character), I went through the installed file line by line with vi and redid all the carriage returns.

The contents of the installed file no longer throws a stanza error, and initctl sees that the zookeeper job exists, but initctl start zookeeper still goes through a fast respawn process and then stops. So something is still not right.

from zookeeper-cookbook.