debug.log parsing issue on remote harvester rpi4 running linux

[marmila]

Discussed in #379

^{Originally posted by marmila July 8, 2023}

Hi there!
I am running chiadog from a windows 10 machine to monitor:

the full node running on windows 10 (chiadog is installed here)
a remote harvester running ubuntu
After the last chiadog update, I am no longer able to monitor the remote harvester , despite the settings in the file config-harvester-1.yaml appears ok:

chia_logs:
file_log_consumer:
enable: false
file_path:
network_log_consumer:
enable: true
remote_file_path: '/home/ubuntu/.chia/mainnet/log/debug.log'
remote_host: "192.xxx.x.xx"
remote_user: "ubuntu"
remote_port: xxx

Despite of my settings in config-harvester-1.yaml, when I start chiadog for remote harvester the application tries to parse the log in a windows format and then I receive a lot of false positives notifications for the harvester

(venv) PS C:\Users\milan\chiadog> python3 main.py --config config-harvester-1.yaml
[2023-07-09 16:55:45] [ INFO] --- Starting Chiadog (v0.7.5-12-g0df494f) (main.py:56)
[2023-07-09 16:55:45] [ INFO] --- Consuming logs remotely from [email protected]:22:C:\home\ubuntu.chia\mainnet\log\debug.log (log_consumer.py:246)
[2023-07-09 16:55:45] [ INFO] --- Connected (version 2.0, client OpenSSH_8.2p1) (transport.py:1874)
[2023-07-09 16:55:45] [ INFO] --- Authentication (publickey) successful! (transport.py:1874)
[2023-07-09 16:55:46] [ INFO] --- Enabled Posix network log consumer. (log_consumer.py:141)
[2023-07-09 16:55:47] [ INFO] --- Connected (version 2.0, client OpenSSH_8.2p1) (transport.py:1874)
[2023-07-09 16:55:47] [ INFO] --- Authentication (publickey) successful! (transport.py:1874)
[2023-07-09 16:55:47] [ INFO] --- Consuming remote log file C:/home/ubuntu/.chia/mainnet/log/debug.log from 192.xxx.x.xx:22 (OS.LINUX) (log_consumer.py:129)
[2023-07-09 16:55:47] [ INFO] --- Keepalive monitor started for HARVESTER with a threshold of 300s (keep_alive_monitor.py:126)
[2023-07-09 16:55:47] [ INFO] --- Keep-alive check period: 300 seconds (keep_alive_monitor.py:140)
[2023-07-09 16:55:47] [ INFO] --- Initializing Email notifier. (smtp_notifier.py:30)
[2023-07-09 16:55:47] [ INFO] --- Enabled stats for daily notifications (stats_manager.py:51)
[2023-07-09 16:55:47] [ INFO] --- Summary notifications will be sent out every 24 hours starting from 21:00 (stats_manager.py:64)
[2023-07-09 16:55:47] [ INFO] --- Enabled service monitoring: HARVESTER (log_handler.py:55)
[2023-07-09 16:55:47] [ INFO] --- Enabled service monitoring: FARMER (log_handler.py:55)
[2023-07-09 17:00:47] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 300 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)
[2023-07-09 17:05:47] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 600 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)
[2023-07-09 17:10:48] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 901 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)
[2023-07-09 17:15:49] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 1202 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)
[2023-07-09 17:20:50] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 1503 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)
[2023-07-09 17:25:50] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 1803 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)
[2023-07-09 17:30:51] [ WARNING] --- Your HARVESTER is unhealthy! No healthy events received for 2104 seconds.
(This check can be adjusted.) (keep_alive_monitor.py:83)

Any advice would be very appreciated :)
thanks in advance!

[martomi]

Hi @marmila,

thanks for the report!

Without having had the chance to dig into this, I can provide context that we have done some rework to the way configs are parsed and to the keep-alive logic. These changes have landed on the main branch but not part of the stable release yet. I see that you are on the latest main branch commit.

Could you try switching back to the stable release with git checkout v0.7.5 or downloading it from here: https://github.com/martomi/chiadog/releases/tag/v0.7.5

I suspect that might resolve your problem until someone offers a PR to fix this.

If this helps, could you please confirm? Worst-case I’ll revert the unstable commits.

[marmila]

Hello @martomi ,
thanks for the feedback!
I have switched back to the stable release with git checkout v0.7.5 , and this solved the issue!
Thanks again and have a great day.