Database communication error

Nizam.Ahmed · ‎09-17-2015

Hi Experts,

I'm facing problem while trying to login cucm. An error is generating like "Database Communication Error"

Please help me to resolve the issue.

Regards

Nizam

Chris Deren · ‎09-17-2015

can you SSH to the server? How many CUCM nodes do you have, and is this consistent across all of them?

Nizam.Ahmed · ‎09-17-2015

Hi Deren,

Thanks for your response.

Yes I can ssh to the server. Single node.

Nizam

Terry Cheema · ‎09-18-2015

Try running the below command from your server:

utils service restart A Cisco DB

after the service is restarted, tru again and let us know how did you go.

if it didnt work attach the output of below commanda: show status, utils service list, utils dbreplication status. Also mention you CUCM version.

-Terry

Please rate all helpful posts

Nizam.Ahmed · ‎09-20-2015

Hi Terry,

Thanks for your instruction. I've followed your instruction but no improvement. Here are the following outputs which you need.

Output: A Cisco DB

1. Output : Status

2. Output of utils service list:

admin:utils service list

Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STARTED]
Cisco SCSI Watchdog [STARTED]
Service Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
A Cisco DB[STOPPED] Component is not running
A Cisco DB Replicator[STARTED]
Cisco AMC Service[STARTED]
Cisco AXL Web Service[STARTED]
Cisco Audit Event Service[STARTED]
Cisco Bulk Provisioning Service[STARTED]
Cisco CAR DB[STARTED]
Cisco CAR Scheduler[STARTED]
Cisco CAR Web Service[STARTED]
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco CDR Agent[STOPPED] Component is not running
Cisco CDR Repository Manager[STOPPED] Component is not running
Cisco CTIManager[STOPPED] Component is not running
Cisco CTL Provider[STARTED]
Cisco CallManager[STOPPED] Component is not running
Cisco CallManager Admin[STARTED]
Cisco CallManager Cisco IP Phone Services[STARTED]
Cisco CallManager Personal Directory[STARTED]
Cisco CallManager SNMP Service[STOPPED] Component is not running
Cisco CallManager Serviceability[STARTED]
Cisco CallManager Serviceability RTMT[STARTED]
Cisco Certificate Authority Proxy Function[STARTED]
Cisco Certificate Change Notification[STARTED]
Cisco Certificate Expiry Monitor[STARTED]
Cisco Change Credential Application[STARTED]
Cisco DHCP Monitor Service[STARTED]
Cisco DRF Local[STARTED]
Cisco DRF Master[STARTED]
Cisco Database Layer Monitor[STOPPED] Component is not running
Cisco Dialed Number Analyzer[STARTED]
Cisco Dialed Number Analyzer Server[STARTED]
Cisco DirSync[STARTED]
Cisco E911[STARTED]
Cisco ELM Client Service[STARTED]
Cisco Extended Functions[STOPPED] Component is not running
Cisco Extension Mobility[STARTED]
Cisco Extension Mobility Application[STARTED]
Cisco IP Manager Assistant[STARTED]
Cisco IP Voice Media Streaming App[STOPPED] Component is not running
Cisco License Manager[STARTED]
Cisco Location Bandwidth Manager[STOPPED] Component is not running
Cisco Log Partition Monitoring Tool[STOPPED] Component is not running
Cisco Prime LM Admin[STARTED]
Cisco Prime LM DB[STOPPED] Component is not running
Cisco Prime LM Server[STARTED]
Cisco RIS Data Collector[STOPPED] Component is not running
Cisco RTMT Reporter Servlet[STARTED]
Cisco SOAP - CDRonDemand Service[STARTED]
Cisco SOAP - CallRecord Service[STARTED]
Cisco Serviceability Reporter[STARTED]
Cisco Syslog Agent[STARTED]
Cisco TAPS Service[STARTED]
Cisco Tftp[STOPPED] Component is not running
Cisco Tomcat[STARTED]
Cisco Tomcat Stats Servlet[STARTED]
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STARTED]
Cisco Trust Verification Service[STARTED]
Cisco UXL Web Service[STARTED]
Cisco Unified Mobile Voice Access Service[STARTED]
Cisco User Data Services[STARTING]
Cisco WebDialer Web Service[STARTED]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]

3. Output of dbreplication status:

admin:utils dbreplication status

Database is down; please restart the database before reattempting a status check
Use this command to see the output - file view activelog cm/trace/dbl/sdi/ReplicationStatus.2015_09_21_09_58_46.out

Please help me to solve this problem.

Thanks

Nizam

Aman Soi · ‎09-21-2015

Hi Nizam,

can u try the command "utils service start A Cisco DB" to start the Database instead of doing restart?

regds,

aman

Nizam.Ahmed · ‎09-21-2015

Hi Aman,

I've tried and the output is

admin:utils service start A Cisco DB
Service Manager is running
A Cisco DB[STARTING]
A Cisco DB[STARTING]
A Cisco DB[STARTING]
A Cisco DB[STARTING]
A Cisco DB[STARTING]
A Cisco DB[STARTING]
A Cisco DB[STARTING]
A Cisco DB[STARTING]
Component is not running
A Cisco DB[NOTRUNNING]

Please help me to solve this problem.

Nizam

Aman Soi · ‎09-22-2015

Hi Nizam,

Suggest opening TAC case for resolution.

regds,

aamn

Rob Huffman · ‎09-21-2015

Hi Nizam,

It sounds like you may be hitting this bug;

10.5.1SU1a CLI security password change causes DB to not start at reboot

CSCur93287

Symptom:
"A Cisco DB" service will not start. CCMAdmin login attempts result in "Database communication error".

Conditions:
Executing a security password change (not recovery) on UCM 10.5.1SU1a by running "set password user security" from the admin CLI then rebooting the system.

This defect also applies in the following situation:

->"A Cisco DB" will be started but then "Cisco database layer monitor" will not be running.

->After the workaround as per the defect is perfomed then need to perfom the drop DB steps if the RTMT values are showing as (-) as per the following link:
https://techzone.cisco.com/t5/Platform/Unity-Connection-Cluster-Replication-Rebuild/ta-p/204178

Workaround:
- Set SELinux to permissive (run "utils os secure permissive" from the admin CLI)
- Do a security password *recovery* (logging in as pwrecovery / pwreset from the VM console)
- Reboot the node
- Set SELinux back to enforcing (run "utils os secure enforce" from the admin CLI)

Further Problem Description:
A similar defect CSCup30002 causes the same symptom in 10.5.1 for the security password *recovery* (as opposed to a security password *change* via CLI, as documented in this defect), due to an issue with SElinux. CSCup30002 is why the workaround for this defect involves setting SELinux to permissive

CSCus13276 tracks another related issue in 10.5.2 with the same symptoms as CSCup30002

Last Modified:

Jun 26,2015

Status:

Fixed

Severity:

2 Severe

Product:

Cisco Unified Communications Licensing

Support Cases:

7

Known Affected Releases:

(2)

10.5(1.11900.13)

10.5(2)

Nizam.Ahmed · ‎09-22-2015

Hi Huffman,

I've followed the workaround but the problem remains same.

If there are further troubleshooting please instruct me.

Thanks

Nizam

CSCO11563793 · ‎05-10-2019

you could find a solution?