Symptoms
ViPR SRM/Watch4Net: Alerting Backend service will not startIn the alerting backend log:
SEVERE [2017-08-22 17:04:47 MESZ] AlertingEngine::main(): Error
com.watch4net.alerting.AlertingException: The path EMC VMAX definitionsVMAX-ArrayXXX Custom Alert - Memory bank error xxxxx doesn't lead to a definition folder
In Alerting.xml Alert definitions were noted like the following:
1083-Register set failure XXXXX
1395609606487xxxx
1084-Memory Bank Disabled Host XXXX
1060668784381xxxx
1085-Environmental validity problem
14146191xxxx
1148-Power Supply B Fault XXXXXX
173790000426xxxx
Cause
Custom Alert Name definitions above conflicting and causing an issue with alerting-backend.
Resolution
Identify the Conflicting Alert Name Definitions in Alerting.xml on your Primary Backend Host in /opt/APG/Backends/Alerting-Backend/Default/conf.
