CUCM 7.0 changed hostname causes database to fail to start
I have CUCM 7.0 installed and it was working with the hostname lh; I have since changed it from the CLI using "set network hostname scratchy". Now I cannot access the web page. This is the only server in the cluster - there are no subscribers.
When accessing the ccmadmin or services page, the page loads & I can try to login but it returns a "database communication error". I can access the OS web page and confirm that the publisher ip address and hostname are what I have updated the server to.
In the CLI if i run "utils dbreplication status" I get an error: Database is down; please restart the database before reattempting a status check".
I have rebooted numerous times.
When I run "utils network host scratchy" I immediately get: "hostname resolves to x.x.x.x"
The address resolved to is correct.
None of the dbreplication commands really do anything (as far as cluster resets, reset all, etc.) because there is no connection to the database.
Any thoughts on missing steps in the document for changing the hostname in CUCM 7.0 would be greatly appreciated, because it does not appear to be as simple as this document references:
Re: CUCM 7.0 changed hostname causes database to fail to start
I actually plan on using the IP for resolution, but I have to get to the CCMadmin page to alter the server name to use this - and I think all that is furhter down the line than my initial problem, which is that the database won't start with the different hostname, let alone the CCM service or any of that.
Regardless of using the IP or the hostname to actually access the web page, the database service is not functioning properly for the Tomcat/web service to access it.
Is there a link on how to change the Tomcat settings or the host file on a Linux server?
It's very important to change the Server name or IP from the System/Servers menu in CCM, and ensure it's written/replicated before you actually change the server hostname - otherwise the DB won't start, as it doesn't find itself in the config files.
If you've done this wrong, I've previously been able to change the name/IP back, and go through the steps properly. Otherwise you may need to go to TAC.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...