Hello Dmitry, KeeperException has to do with ZooKeeper. Why don't you check the following first:
1. Check if your ZooKeeper instance is running properly and on the machine:port you are expecting it to run. 2. Check that your Nimbus attempts to connect to the right ZooKeeper The ACL Exception you are getting might be because there is a mismatch between your Nimbus's previous state and the current one stored on ZooKeeper. If you verify that Steps 1 and 2 are correct and the problem persists, I would consider re-initializing Nimbus (erasing the nimbus directory in your storm-local directory) and restarting ZooKeeper. Keep in mind that re-initialization might cause the loss of data. Hence, do the previous only if you are ok with losing any data. Cheers, Nick On Tue, Nov 17, 2015 at 6:36 AM, Dmitry Sergeev <[email protected]> wrote: > First, I started Nimbus with > ${storm.home}/bin/storm nimbus > It starts successfully > When I'm trying to start supervisor with this command: > ${storm.home}/bin/storm supervisor > It prints JVM options and exit. > In supervisor.log I see next message: > >> 2015-11-17 11:28:56.111 b.s.d.supervisor [ERROR] Error on initialization >> of server mk-supervisor >> java.lang.RuntimeException: >> org.apache.storm.shade.org.apache.zookeeper.KeeperException$InvalidACLException: >> KeeperErrorCode = InvalidACL for >> /supervisors/62a290be-610d-4177-9702-58479ebc80d2 > > I guess it is problem with security configuration. > Storm 0.9.4 works fine. > Can you help me? > > Thanks > -- Nick R. Katsipoulakis, Department of Computer Science University of Pittsburgh
