Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Network heal times out too early
See original GitHub issueNetwork heal command fails with error: refreshing neighbor list failed: Timeout while waiting for a callback from the controller
Healing starts at 13:33:09.939 CNTRLR starting network heal...
Running Zwavejs 6.4.0. Please let me know if any further details are required to debug this. Thank you.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
How to Get to the Bottom of Network Timeout Issues
Based on the basic idea, first check the ECS instance and link for packet loss from the monitoring. The result shows that no...
Read more >detecting network drops and preventing idle socket timeout
Send TCP Keepalives successfully (within 15 minutes), before idle socket timeout (typically 60 or 30 minutes). Make sure TCP Keepalives retry at ...
Read more >WiFi Network Timeout/Recovery - Technical Questions
The word I got from Sense support was that the device tries to reconnect for up to 6 hours, after which point it...
Read more >Timeouts, retries and backoff with jitter
When failures are caused by overload or contention, backing off often doesn't help as much as it seems like it should. This is...
Read more >Load Balancer Timeout Connection Settings
Describes how to configure the timeout settings for your load balancer. ... it has been idle for 65 seconds, whichever limit occurs first....
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 Free
Top 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
It should, but doesn’t right now.
Okay, based on your network size it seems like we should be waiting around 3 minutes for the callback, rather than the fixed 65 seconds we currently wait.