IBM Support

Alertmanager pod in status CrashLoopBackOff

Troubleshooting


Problem

The pod

monitoring-prometheus-alertmanager
stays in status CrashLoopBackOff.

Symptom

The pod log shows an error message like:
level=error ts=<timestamp> caller=main.go:314 msg="Loading configuration file failed" file=/etc/config/alertmanager.yml 
err="yaml: line 5: did not find expected key"
or
level=error ts=<timestamp> caller=main.go:314 msg="Loading configuration file failed" file=/etc/config/alertmanager.yml 
err="yaml: unmarshal errors:\n  line 9: field <field_name> not found in type config.plain"

Document Location

Worldwide

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.1","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
08 March 2019

UID

ibm10875488