-
Notifications
You must be signed in to change notification settings - Fork 109
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
Generic question on Wine crashes and how to limit downtime #51
Comments
karunkrishna
changed the title
Generic question of Wine Crashes and how to limit downtime
Generic question on Wine crashes and how to limit downtime
Mar 10, 2021
I don’t run pyiqfeed inside a container. Don’t really have any advice to offer on the monitoring front, though I would love to hear what you find.
Frankly, in my usage, I don’t have many crashes. I do restart iqfeed.exe every 24 hours. I would want to look to see why crashes are happening. I literally don’t remember the last time I had a crash other than something that took a whole machine down or something like that.
… On Mar 10, 2021, at 2:44 PM, karunkrishna ***@***.***> wrote:
Currently running this on docker
If the autoheal detects that pyqfeed container is down it restarts. This usually takes about 15 minutes from last tick update
As a result, I had implemented a heartbeat in my strategy itself to restart pyiqfeed-docker if update has not occurred for more than 3 heartbeats (3 minutes)
Is there a recommended way of monitoring wine crashes, or pyiqfeed becoming unresponsive as restarting the docker-container is quite expensive in terms of downtime
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#51>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGJAVDHHMQIUF7AMUCNBALTC64XVANCNFSM4Y6X3UMQ>.
|
Sure, will investigate I'll keep this ticket open for a few days to see if anyone else responds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently running this on docker
The text was updated successfully, but these errors were encountered: