Closed ksatter closed 1 day ago
Linked to Unthread ticket:
@xpkoala, this seems hard to reproduce. Perhaps we should allocate time for an engineer to look at the log. TMWYT
Based on the Unthread conversation, the issue appears resolved by the reinstall. We'll keep an eye on any future reoccurances, but for now, closing this issue.
In the glass city's glow, Fleet finds a steady rhythm, Windows hosts now flow.
Fleet version: <!-- Copy this from the "My account" page in the Fleet UI, or run
fleetctl --version
--> fleetd version: Began on v 1.41.0, persists on v1.43.0 Host OS: Windows 10 and 11 ProWeb browser and operating system:
💥 Actual behavior
In Fleet, it was observed that certain Windows hosts were 'online', but had not fetched for an extended period.
The customer attempted to restart the fleet-osquery service. After this, hosts remained offline in Fleet.
The customer next rebooted the machine. After this, communication was re-established for a period, but eventually the host reverted to being 'online', but not refetching. This may coincide with the test host going into a sleep state and then waking again, but it is uncertain.
Observations from the orbit-osquery logs on these hosts:
Full orbit-osquery logs, as well as Windows Event logs are available in Unthread.
I have not been able to reproduce this behavior, and do not currently see any patterns of behavior that explain why some hosts are unable to reach Fleet.
🧑💻 Steps to reproduce
🕯️ More info (optional)
N/A