You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Had an issue were the velociraptor client was crashing seemingly randomly on a large number of our endpoints everyday. The endpoints were predominately laptops (>99% of them). Upon troubleshooting it appears the crash was happening after the endpoints were resumed from sleep. Further testing did show the crash could be replicated by having a device sleep longer than the nanny_max_connection_delay setting and then resuming the device from sleep.
Example logs:
[INFO] 2025-01-09T10:12:19-07:00 Sender: received 626 bytes in 149.2434ms
[INFO] 2025-01-09T10:19:46-07:00 File Ring Buffer: Enqueue {"header":"{\"ReadPointer\":50,\"WritePointer\":723,\"MaxSize\":1073741874,\"AvailableBytes\":665,\"LeasedBytes\":0}","leased_pointer":50}
[ERROR] 2025-01-09T10:19:46-07:00 NannyService: Last Read From Server too long ago 2025-01-09 10:12:18.710874 -0700 MST m=+21.548059401 (now is 2025-01-09 10:19:46.8276818 -0700 MST m=+469.664867501 MaxConnectionDelay is 2m0s)
[ERROR] 2025-01-09T10:19:47-07:00 Hard Exit called!
The text was updated successfully, but these errors were encountered:
Had an issue were the velociraptor client was crashing seemingly randomly on a large number of our endpoints everyday. The endpoints were predominately laptops (>99% of them). Upon troubleshooting it appears the crash was happening after the endpoints were resumed from sleep. Further testing did show the crash could be replicated by having a device sleep longer than the
nanny_max_connection_delay
setting and then resuming the device from sleep.Example logs:
The text was updated successfully, but these errors were encountered: