Hello all, I am trying to understand the logs of t...
# fleet
s
Hello all, I am trying to understand the logs of the vulnerabilities part, what does
"cron":"vulnerabilities","leader":"Not the leader. Skipping..."
mean?
t
hi, this happens when you are running vulnerability processing on a dynamic host. How many instances of fleet are you running?
s
4 instances
My idea was to use one instance that is not that busy to handle the vuln part
t
ok, you can statically assign an instance to be the one doing vulnerability processing, see here for more details: https://github.com/fleetdm/fleet/blob/main/docs/2-Deploying/2-Configuration.md#vulnerabilities
s
Great, added the option. I was wondering regarding the instances if I want to use the software inventory, do I need to add
FLEET_BETA_SOFTWARE_INVENTORY=1
to all the instances?
t
correct, or you can set it as the config as well
s
with config you mean this?
Copy code
host_settings:enable_software_inventory: true
t
correct
s
Thanks, will do, hopefully that I will see it afer that in the UI
A quick check, below needs to be added in the fleet.yml file of each fleet instance on each server when started right? I tried adding it through apply of fleetctl but don't see it when I get the config.
Copy code
vulnerabilities:
	current_instance_checks: yes
t
that config cannot be applied through fleetctl, fleet server config needs to be applied "by hand" as it is used at the server startup. fleetctl apply is for config that can be changed at runtime. That config is something you need to add to each instance, however, you only want one with value
yes
and the rest with
no
s
Yes I understand it, it was a bit confusing which settings are for which part. I did the change and will see if it works OK now.