How long ago was the issue with the database path ...
# fleet
k
How long ago was the issue with the database path resolved?
j
About 5 hours
k
Definitely more than an hour then :) What version of Fleet are you running?
j
4.18 and this is the log
Copy code
level=info ts=2022-09-07T10:47:48.237551302Z component=crons cron=vulnerabilities cron=vulnerabilities databases-
path=/tmp/vulndbs                                                                                                
level=info ts=2022-09-07T10:47:48.237796888Z component=crons cron=vulnerabilities cron=vulnerabilities periodicit
y=1h0m0s                                                                                                         
level=info ts=2022-09-07T10:47:48.528169531Z msg="metrics endpoint disabled (http basic auth credentials not set)
"
k
Just to be 100% sure the setup is all there, can you pull the Fleet config with ‘fleetctl get config —include-server-config’ and check the value for
vulnerabilities.databases_path
?
I know it's there in the logs and everything, but… weird things happen occasionally and I don't want to skip checking.
That's the culprit! That value is used when aggregating software inventory.
j
So I only need to apply a new configuration file and set it as
/tmp/vulndbs
?
k
That'll do it.
j
Thanks.
k
Glad I double checked. I need to dig in a little more on how it gets/sets that path for the host level checks without that setting just so I know, but setting that should get you up and running.
j
It's working after a day. (may be the pods restart)