(BSM) Support Tip: BSM/APM Identify Invalid Downtimes
An invalid downtime can cause crashes in BSM_DT HAC service on DPS, which translates to problems processing status for CIs and even sample rejection on GW servers.
ERROR - Failed to handle configuration notification
WARN - Failed to start service BSM_DT for 1
com.hp.bsm.platform.dt.DTException: Model manager failed to start for customer 1.
If there is something wrong with one or more downtime, enable Debug logging for "com.hp.bsm.platform.dt.server" in <DPS>\conf\core\Tools\log4j\EJB\downtime.properties is required to see which downtime(s) are having issues, e.g.:
DEBUG - Getting DT schedulers method filterLightDowntimes(), id: 6687bc3b8d304b07a3050a34238f5d0b; start time: null; end time: null
DEBUG - constructor DTOccurrenceIterator, schedule start: null; end: null
In the above example the downtime with CMDB_ID 6687bc3b8d304b07a3050a34238f5d0b has an invalid value (null) in start time and end time.
Below are a couple of ways to Identify and remove the problematic downtime(s):
1. list downtimes via BSM GUI, identify the downtime by ID and delete it
2. list downtimes via JMX method (http://<BSM>:8080/jmx-console > Service=DowntimeManager > listAllDowntimesAsHTML) and delete it (http://<BSM>:8080/jmx-console > Service=DowntimeManager > deletedowntimebyID)
If by some reason the two above methods are not available, the downtime can be removed from the corresponding tables in MNG DB. Please engage support for this task.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.