-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems supervisor did not restart the cfjsonlog.pl script! #10
Comments
Have a look at the Not sure what to do as am not familar with the stop signals for perl.. Also shall I create the supervisor log in |
Hi Pete, Thanks for the hints, but...
No, this is about when As stated, if there is a tiny glitch in the json http BUT, if SV waits 2-5 secs before restarting the Is there a way to say to SV - take it easy kid! The If there is a temporary problem, do not try to I do not know how quickly SV detects a process down! But is SV is very attentive... maybe too attentive... As you know, the json string in crossfeed is only At some point, I will get around to moving this Yes, I have created a /home/geoff/log folder you can And I too As stated, I will get around to adding this All it seems I want at the moment is for Regards, |
Supervisor probably does not do what we want.. It designed to keep processes running, ie zero downtime |
Why is the script crashing anyway.. ? |
Another quick hack would be to launch from a bash.script and make is sleep for X seconds before kicking off the pl script |
Hi Pete, Ok, understand Yes, I too thought of the quick hack to But as stated I am waiting for this to See lines - That service I could add some checks here, and if not a But, as usual, it has been running several I guess it may go back to a Maybe at that moment cf forms some bad See service This service establishes the next json string As stated it seems quite a rare event... but And as I now feel Mr Thanks, |
Ok, it broke again in RPI2. exactly where predicted... BUT, not in Maybe the auto restart 1, 2, ... were already in the next crossfeed 1 second cycle... Made a kludge fix in the pl script, and that is to wait 5 seconds before doing the first fetch... there really is no big rush here... on start up... Added some more precise timing... just debug stuff... This is a quick fix, while I look deeper into avoiding it totally ;=)) Also decided to cycle the log to TODO: Get the CSV files synced... On to the next steps... |
had a quick look at script... and seems strange to be that
|
@geoffmcl adding issues on crossfeed-logger, re analysis.. Issue #1 is your TODO ie CSV files synced freeflightsim/crossfeed-logger#1 |
WHAW... |
@pedromorgan yes, I certainly could add some error return to This did start out just as a WIP test to get an updated MODEL use, but has grown since then... And as mentioned still a TODO to sync the raw CSV files... presently missing 22 and 23, and 24 is truncated... will get to this, hopefully soon ;=)) And I had not forgotten your |
Hi Pete,
The cflog script was running good, under supervisor,
for a few days, so I stopped monitoring it for a few
days... and BANG ;=))
It stopped on 2016-08-21, and for some reason
supervisor
did not restart the script ????????When I entered
$ sudo supervisorctl
it showed anerror line -
Anyway, I restarted
cflog
, and it is now outputtingflights-2016-08-24.csv
... over the coming days I willfill in the missing logs from my RPI2 collection, so
no problem...
But just a question! Why did
supervisor
notrestart the
cflog
job?The super config
$ /etc/supervisor/conf.d/cflog.conf
already contains -
Is there anything else we need to do to make
supervisor
restart the script if it fails,for any reason...
I note the
startretries=3
. If super restarts thescript too quickly, maybe the json fetch problem,
the only known reason it stops, has not yet
recovered...
Is there are way to config super to wait say
20 to 25 seconds before the restart... then 3
retries over the next minute or so might make
sense...
But am concerned that if super restarts the script
virtually immediately, then it may be easy to get 3
similar fetch errors within the first few seconds...
Will keep monitoring the situation...
Regards,
Geoff.
The text was updated successfully, but these errors were encountered: