Hi, When I meet this one on a dev environment, I simply:
* shut down storm * delete the storm local state folder (/home/elsztok/storm_tmp/ in your configuration) * restart storm This basically resets all local state of nimbus and ui as I understand it. I'd be glad to hear if there was a cleaner approach. S On Fri, Jan 17, 2014 at 5:03 PM, Attila Tóth <[email protected]>wrote: > Dear Storm User Group! > > > > We are experimenting with Storm 0.9.0.1 and having an issue with deploying > the Storm-Starter demo cluster to our test environment (which consists of a > master server and – for now - a single server running one supervisor): > > > > We experience the following java exception from (in the supervisor log): > > > > 2014-01-17 10:25:13 b.s.d.worker [ERROR] Error on initialization of server > mk-worker > java.io.FileNotFoundException: File > '/home/elsztok/storm_tmp/supervisor/stormdist/mytopology-6-1389892683/stormconf.ser' > does not exist > > > > We have already tried the following: > > > > 1. Restart the topology (kill and restart) > > 2. Restart Nimbus and the supervisor, redeploy topology > > 3. Restart Zookeeper, restart Nimbus, restart supervisor, redeploy > topology > > > > We have used the info available on > https://github.com/nathanmarz/storm/wiki/Setting-up-a-Storm-cluster to > setup our simple cluster. > > > > Everything was working on LocalTopology correctly, it seems the problem is > with the deployment and-or Storm configuration. There are no other errors > apart from this one. Also, the UI does not show streams processing and bolt > operation. The stormconf.ser and its directory is accessible by the “user” > user. We are compiling and running with the same Storm library version. > > > > In some threads we have seen questions and answers about issues similar to > this, however they relate to a different (mostly earlier) storm version, > and states that the error was fixed on 0.9.0-rc3 > > > > Considering this, we would like to ask the following: > > > > 1. Can it be that we are using a wrong ZooKeeper version (3.4.5 > instead of 3.3.3)? (Right now we cannot switch the version because the > system is under use by others.) > > > > 2. Do you have any other suggestions apart that we have already > tried out to solve this problem? > > > > Thank you very much in advance! > > > > Attila Tóth > > >
