This article addresses an issue where Kubernetes pods running the Flexera Kubernetes Inventory Agent crash immediately after startup, showing a CrashLoopBackOffError.
The following logs may appear in the Kubernetes monitor, depending on the agent version:
Agent version before 22.2:
krm 2025-04-14T17:11:49.543253048Z INFO -- start: version 1.4.0
krm 2025-04-14T17:11:49.690082481Z INFO -- main: stopped
exit status 1
Agent version 22.2 and later:
krm 2025-04-21T04:13:36.82071489Z INFO -- start: version 1.8.2
krm 2025-04-21T04:13:38.538676059Z ERROR -- main: config.UpdatePolicy() - returned error: exit status 1
krm 2025-04-21T04:13:38.538724164Z INFO -- main: stopped
exit status 1
The KRM is failing immediately upon startup, usually due to an issue downloading the policy from the beacon. This is often the first operation the agent performs during initialization.
To isolate and troubleshoot the issue, follow these steps to disable automatic policy download, trigger it manually, and retrieve the logs.
- Stop automatic policy download
Edit your deployment YAML to prevent the KRM from attempting to download the policy on startup:
apiVersion: agents.flexera.com/v1
kind: KRM
metadata:
name: flexera
spec:
monitor:
downloadFromBeacon: false
- Start the KRM
Deploy or restart the KRM after applying the above change.
- Manually trigger policy download and retrieve logs
For agent versions before 22.2:
/opt/managesoft/bin/mgspolicy -t machine
kubectl cp -n flexera krm-instance-monitor-0:/var/opt/managesoft/log/installation.log installation.log
For agent version 22.2 and later:
/opt/managesoft/bin/flxconfig
kubectl cp -n flexera krm-instance-monitor-0:/var/opt/managesoft/log/agent_configuration.log agent_configuration.log
- Review logs
Check the appropriate log file for errors related to policy download. Common issues may include:
-
- Network connectivity problems
- Invalid beacon URLs
- Authentication failures
- Misconfigured environment variables
Address the error indicated in the log and restart the KRM as needed.
Related Articles
Kubernetes image details gathered by the KRM agent not showing in All Containers view if the node.Status.Images details do… 1Number of Views Flexera Kubernetes agent (KRM) does not gather inventory details associated with settings in InventorySettings.xml as the … 1Number of Views Why the console shows “EC2 status: Healthy” and “Kubernetes status: Can’t determine” 4Number of Views Inventory received from the Lightweight Kubernetes agent (LWK) fails to import and is not shown on the "All Containers" page 6Number of Views Cluster doesn’t scale up because of a Kubernetes version parsing error 4Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago