Hi, I just upgraded fleet to version 4.38.0 by put...
# fleet
i
Hi, I just upgraded fleet to version 4.38.0 by putting the option image: fleetdm/fleet:latest in the docker-compose file instead of image: fleetdm/fleet:v4.17.0, as doing [root@itl-cslapp-67 ~]# docker exec fleet fleet prepare db Migrations already completed. There is nothing to do. [root@itl-cslapp-67 ~]# docker exec Fleet fleet serve I get this error: {"component":"redis","level":"info","mode":"standalone","ts":"2023-09-29T151436.605465057Z"} {"instanceID":"CLi0vOe12VKwXH/6MIKHR6zOdMTeQF4YOkvMuUbq6KSxoln+bWK3buspZ1p1E+knyLY/RbKEJNNVBkxMfU8++w==","level":"info","ts":"2023-09-29T151436.686383454Z"} {"level": "info", "msg": "initiate cron schedules: automations, clean_poi_aggregation, integrations, use_statistics, vulnerabilities", "ts": "2023-09-29T151436.72953031Z"}}. {"level": "info", "msg": "metrics endpoint disabled (basic http authentication credentials not set)", "ts": "2023-09-29T151436.810172381Z"} {"address":"0.0.0.0:8080","msg":"listening","transport":"https","ts":"2023-09-29T151436.810703009Z"} {"terminated": "listen tcp 0.0.0.08080 bind: address already in use", "ts": "2023-09-29T151436.81110094Z"} I have proceeded to regenerate the package to be redistributed to the hosts using "fleetctl package --type msi --fleet-url=https://it-asset.company.it --enroll-secret=zdfjzyfUkczdmdfefefefeqCdkvcwPuKf --fleet-desktop" but I want to make sure that the orbit agent is automatically updated every time fleet is updated without having to regenerate the package, how can I proceed? below are the agent options: config: options: pack_delimiter: / logger_tls_period: 10 distributed_plugin: tls disable_distributed: false logger_tls_endpoint: /api/osquery/log distributed_interval: 10 distributed_tls_max_attempts: 3 decorators: load: - SELECT uuid AS host_uuid FROM system_info; - SELECT hostname AS hostname FROM system_info; # Requires Fleet's osquery installer. # command_line_flags: {}
g
Greetings, guide for upgrade can be found on release page https://github.com/fleetdm/fleet/releases When upgrading, be sure to take the server offline before doing
prepare db
as for Orbit, it is honestly pretty "aggressive" with how it updates and its purpose is to keep Osquerey/agent up to date on the hosts
i
@Grant Bilstad so how do I avoid that every time fleet is updated I have to connect to 100 hosts to update it manually?
g
Maybe I am not understanding- You have Fleetdm Server running; shouldn't need to update agents as Orbit handles keeping Osquerey updated on your end-points (unless using own tuf for things such as dev, production etc) https://fleetdm.com/docs/using-fleet/fleetd. Some other clients have used Puppet, Chef, or Ansible for deployments
k
Just to add a little additional info here, there are some flags you can set when generating a package to control updates. If you don't set those, the default behavior is for all of the
fleetd
components to automatically update any time a new stable version is released.