Jesus Santos
01/16/2023, 6:26 PMflags updates failed error="error getting flags from fleet: enroll endpoint does not exist"
, and I think this is the culprit of most of my hosts not being able to generate logs from the process_events
and socket_events
tables, even tho the file_events
work
Fleet version: 4.26.0
, but had the same problem on 4.22.1
Orbit version: 1.5.0
(Also, is there anything on your side that is pending? I’m getting the error below when trying to generate an orbit package from fleetctl after upgrading to 4.26.0: Error: initialize updates: failed to update metadata: update metadata: tuf: failed to decode timestamp.json: unexpected end of JSON input
)zwass
01/16/2023, 7:09 PMfleetctl package
again? There was an issue with the CDN provider we use for the updates repository that they say has just been resolved.Jesus Santos
01/16/2023, 7:10 PMzwass
01/16/2023, 7:13 PMJesus Santos
01/16/2023, 7:16 PMzwass
01/16/2023, 7:19 PM/api/orbit/enroll
. Maybe you need to configure a load balancer or firewall to allow that?
Doing so allows you to use some of the newer features like managing osquery startup flags from the Fleet server.Jesus Santos
01/16/2023, 7:23 PM/api/osquery/enroll
, which was allowed previously, and since I could setup File Integrity Monitoring directly through the web UI, I though I had all in place to make these “hot” changes, but that makes sense
I didn’t see a few flags I’ve tried on the UI while troubleshooting the event tables, probably because of this endpoint
Will enable this in the deploy window tomorrow and keep the tests, but I’m pretty confident it is the one
Again, thank you very much sir! 😒aluting_face:zwass
01/16/2023, 7:25 PM