Closed xpkoala closed 2 months ago
This appears to have been caused by some database manipulation I had done during testing. The fix was to run DELETE from mdm_config_assets;
on the database and restart the server.
Closing for now.
Panic fixed, all's calm, Code runs like a soothing balm, Fleet sails on, no qualm.
Fleet version:
minor-fleet-v4.56.0
Web browser and operating system: N/A
💥 Actual behavior
After building, preparing, and starting the fleet server I encounter a panic.
🧑💻 Steps to reproduce
./build/fleet serve --dev --dev_license --vulnerabilities_databases_path=/tmp/vulndb --debug --logging_debug
🕯️ More info (optional)
The server had been running off the same branch for the past several days.