When installing Storm, we get an error that the supervisor did not run. What should we do?

 2013-04-04 14:02:39 b.s.d.supervisor [INFO] 07a06309-95f5-423b-999b-f5913388bb2e still hasn't started
 2013-04-04 14:02:39 b.s.d.supervisor [INFO] 07a06309-95f5-423b-999b-f5913388bb2e still hasn't started
 2013-04-04 14:02:40 b.s.d.supervisor [INFO] 07a06309-95f5-423b-999b-f5913388bb2e still hasn't started
 2013-04-04 14:02:40 b.s.d.supervisor [INFO] 07a06309-95f5-423b-999b-f5913388bb2e still hasn't started
 2013-04-04 14:02:41 b.s.d.supervisor [INFO] 07a06309-95f5-423b-999b-f5913388bb2e still hasn't started
 2013-04-04 14:02:41 b.s.d.supervisor [INFO] 07a06309-95f5-423b-999b-f5913388bb2e still hasn't started
+4
source share
1 answer

It's not a mistake. This message is logged when the supervisor starts, or the supervisor tries to spawn a worker to start the topology. Ultimately, your oversight process will begin. If it does not start, there should be additional log messages to describe the reason the process does not start.

+1
source

All Articles