Preview Tool

Cisco Bug: CSCun77018 - CLI, GUI and RTMT indicate ELM DB not started

Last Modified

Aug 09, 2019

Products (1)

  • Cisco Unified Communications Licensing

Known Affected Releases


Description (partial)

Occasionally, ELM DB shows that it is not running from CLI, GUI or RTMT alarm.

Examination of the system through a remote account shows that ELM DB and ELM are both running and fully functional.

After an install or upgrade (potentially after a system restart).

Occurs most often to UCS servers (virtualized)

The below is seen in Detailed level CUCM ServM logs (from CLI issue command: set trace enable Detailed servm)

11:40:24.464 |getPidFromFile - Can not open input PID file /var/run/

11:40:27.969 |servMEvtHdlr::handleScriptResponse() for service Cisco ELM DB
11:40:27.969 |servMScriptMgdProc::handleAsyncResponse - Service - Cisco ELM DB
11:40:27.969 |servMScriptMgdProc::handleAsyncResponse(): Start failed with return Status - 1007
11:40:27.969 |servMProc::setCurState() CurState (notRunning) for service - Cisco ELM DB
11:40:27.969 |servMDepNode::goInactive(): for Cisco ELM DB
11:40:27.969 |servMProc::isAlive() - Invalid pid  0 for service - Cisco ELM DB
11:40:27.969 |servMProc::setCurState() CurState (notRunning) for service - Cisco ELM DB
11:40:27.969 |servMDepNode::goInactive(): for Cisco ELM DB
11:40:27.969 |servMScriptMgdProc::checkHealth(): Either isAlive () or getAmAction () reported failure. Current state of Service set to NotRunning. This will trigger a Graceful Restart of the Service Cisco ELM DB.
11:40:27.969 |servMScriptMgdProc::checkState() CurState (notRunning), DesiredState (running) - Service - Cisco ELM DB

Related Community Discussions

Cisco ELM DB service not running
Hi Guys, I have following error: ----------------------------------------------------------------------------------------------- [RTMT-ALERT-StandAloneCluster] CriticalServiceDown Service operational status is DOWN. Cisco ELM DB. The alert is generated on Mon Jan 04 14:36:48 GMT 2016 on node 10.x.x.x ----------------------------------------------------------------------------------------------- I am running CUCM: System version: Issue started after servers was shut down and rebooted ...
Latest activity: Jan 06, 2016
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.