-
Notifications
You must be signed in to change notification settings - Fork 4
Description
As a part of my deployment process of my project RED5000 (https://github.com/willjasen/ruby-on-rails-cloudformation and https://github.com/willjasen/red5000), I am using recurrent to read some values from a networked device (specifically, a device that monitors energy consumption on an electrical circuit) every 5 seconds. When I initially implemented it, having recurrent run in the background meant that it would run so long as the terminal session remained opened and any of recurrent's logging would be displayed to the terminal window. Using recurrent's quiet logging feature has made it so that the process can be put into the background and the terminal window closed, but I've noticed many times that the recurrent process eventually stops, so I have to check it regularly, kill processes if it's not working properly, and re-run - the bane of my automation existence!
Is there any sort of other debugging information that I can gather to determine why it stops randomly?