Appears to be offline when it's not

[Gregwolf3030]

Fresh install of all software (OS, Chia and all requirements for this program). After about 21 hours of it running, it suddenly started to report "Your harvester appears to be offline! No events for the past 417 seconds. (keep_alive_monitor.py:83)". It kept sending these reports every 5 minutes with the seconds reported climbing accordingly. The issue is that the harvester is not offline. The Chia software shows it is still farming and if I check the logs everything looks fine. I stopped chiadog and started it again and it is all fine now.

Environment:

• OS: Windows 10 Pro
• Python version: 3.9.5 (64-bit)
• PIP version: 21.1.1
• Chia version: 1.1.5

[Gregwolf3030]

And after creating this issue, about another hours and a half later, it did it again. Below is an image showing the first occurrence of the issue, then a restart of chiadog and then the second occurrence of the issue. Below that is a powershell script streaming the current harvester action to show that the system is not offline.

[jojoel]

Me too, got same error

[tydeno]

Same here.

[j3roen7]

same here on windows 10, even when I put the enable_remote_ping: false on false it gives me these 'harvester appears to be offline' errors

[Gregwolf3030]

A quick update a day later. It has pretty much become unusable. About every hour and a half (sometimes less, sometimes more) it will go into this state and start sending the notifications and I have to reset it. I rebooted the system last night thinking that maybe because it hadn't been rebooted since I installed all the requirements for this it may have helped. It did a little, it ran almost through the night. But at 7am this morning it started doing it again and went back into the pattern of lasting about an hour and a half.

[pieterhelsen]

Please checkout the windows-rotation branch.
https://github.com/martomi/chiadog/tree/windows-rotation

This should alleviate some if not most of these issues.
We will likely move to another implementation in the near-future, but this should at least get you going.

[pieterhelsen]

Duplicate of #72

[Gregwolf3030]

I apologize. I was not aware I was only looking at the open issues list. I actually went through all the issues I saw to make sure I wasn't duplicating an issue. Thank you for replying. I have switched to that version.