It sounds to me, like the command to start nimbus in the supervisord configuration is launching it via another process. And the other process is what is getting it's PID tracked by supervisord. What is the supervisord configuration like for nimbus?
On Thu, 6 Jun 2019 at 15:36, Stig Rohde Døssing <stigdoess...@gmail.com> wrote: > Hi Nicole, > > No, this is the right place. > > Your question is a little unclear to me since it is hard to tell whether > you're talking about the supervisor Storm daemon, or the supervisord tool > for running services. I'm going to assume you are asking why storm-nimbus > is in the BACKOFF state, and whether it is still running. > > Going by the supervisord docs (http://supervisord.org/subprocess.html), > it sounds like supervisord tried to start Nimbus, decided it didn't > succeed, and placed it into the BACKOFF state. This is a temporary waiting > state where supervisord will wait a bit, before trying to start Nimbus > again. Nimbus may or may not be running when in this state. Supervisord may > have assumed wrong, and Nimbus actually managed to start. In your case, > Nimbus is clearly running since you can submit topologies. > > You can most likely figure out whether Nimbus crashed, and why, by reading > the Nimbus log. The default location is in your-storm-dir/logs/nimbus.log. > > Den tor. 6. jun. 2019 kl. 12.31 skrev <nicol...@uom.gr>: > >> Hello, >> >> I am Nicole and I am a researcher in University of Macedonia, Greece. I am >> new to Storm and I found this email in the "Getting Help" Section of >> Storm's site. >> >> I started using Storm a few days ago and I have a question on Nimbus. I >> tried to stop (using both ways i.e Ctrl-C and supervisor) the Nimbus, UI >> and Supervisor deamons and start them again and I had some issues. When I >> tried to restart Nimbus it seems to exit fast on its own (like pressing >> Ctrl-C). When I tried to do the same with supervisor I got the following >> results: >> >> # sudo supervisorctl status >> storm-nimbus BACKOFF Exited too quickly (process log may have >> details) >> storm-ui RUNNING pid 4024, uptime 15:43:28 >> >> Nevertheless, Nimbus seems to run normally as I can run a new topology and >> kill it with no problem at all. Why does this happen? Is my Nimbus still >> on? >> >> In case this is not the right place to ask such questions I am sorry for >> the inconvenience. Is there a community to ask questions? Thank you very >> much in advance. >> >> Regards, >> Nicole >> >> -- *Peter Chamberlain* | Senior Software Engineer | HTK T: +44(0)870 600 2311 Connect with me: Email <peter.chamberl...@htk.co.uk> [image: htk logo] <http://www.htk.co.uk/> Connect with HTK: htk.co.uk <http://www.htk.co.uk/> | LinkedIn <http://www.linkedin.com/company/htk/> | Twitter <http://www.twitter.com/htkhorizon> HTK Limited, Chapmans Warehouse, Wherry Quay, Ipswich, IP4 1AS, UK. Company Registered in England and Wales as 3191677, VAT Number 675 9467 71 PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. This email is only for the use of the intended recipients and may contain privileged information. If you’ve received this email in error, please let the sender know; then delete the message. The views expressed in this email represent those of the sender and not necessarily of HTK.
