[BUG] Debug logs 'Sending to keepalive to IP Address'
See original GitHub issueDescribe the bug Since the latest update (v4.4.7) there is a constant entry in my logs for debug, but I do not have debug enabled.
To Reproduce Steps to reproduce the behaviour: Install v4.4.7.
Expected behaviour
I do not have debug mode active, so I am unsure why I am getting debug logs, I even went into my config and made sure to set "debug": false
and it still appears in my logs.
Screenshots
[26/11/2021, 1:01:38 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
[26/11/2021, 1:03:08 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
[26/11/2021, 1:04:38 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
[26/11/2021, 1:06:08 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
[26/11/2021, 1:07:38 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
[26/11/2021, 1:09:08 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
[26/11/2021, 1:10:38 pm] [Broadlink RM] [DEBUG] Sending keepalive to 192.168.0.155 : 80
Desktop (please complete the following information):
- OS: [Windows 11]
- Browser [Firefox]
Smartphone (please complete the following information):
- Not relevant
Additional context The issue with the debug message seems to only be on v4.4.7 and if I revert to the previous version it goes away.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:8 (1 by maintainers)
Top Results From Across the Web
OpenSSH keepalives do not work correctly when using IPVS
It seems that it may only be occurring when the machine is accessed via the IPVS IP address and not directly at its...
Read more >Make debugging client keepalive misconfigurations easier
Mis-configured client keepalive so it is more aggressive than what was permitted on the server. This is an incredibly easy error to make....
Read more >VPC-2-PEER_KEEP_ALIVE_RECV_FAIL log message on ...
We recently (this year) started getting log messages for Keep alive failures. I enabled debug logging and they show the following:.
Read more >MQTT Keep Alive Interval Explained With Examples
MQTT uses a keepalive mechanism for checking the status of the TCP/IP connection.On a quiet TCP/IP connection an MQTT client will send a ......
Read more >Troubleshooting Tip:' FortiAnalyzer Queued logs du...
Description 'This article describes how to resolve Queued logs on ... diagnose debug application oftpd 8 10.109.52.211 -> FGT- IP Address.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the update. I’ll push a new version next week… assuming work starts to quieten down soon.
I also confirm the resolution of the problem after installing the 4.4.8-beta.1