Unity Connection 10.5.2.12901-1 Critical Error Upon Fresh Install

tarkington · ‎09-01-2015

I am installing a fresh Unity Connection Publisher on a BE6000M (C220 M4S) and getting a critical error during installation.

"rpm --percent -iv --replacefiles /common/rpm-archive/10.5.2.12901-576.i386.rpm " failed (1)

I have used the ova provided on the server's datastore: CUC_10.5_vmv8_v1.5.ova

CIMC firmware is all up to date, the Cisco custom version of ESXi that came pre-installed is also up to date.

I verified the MD5 checksum of the bootable media before install.

The same error occurs when using the bootable media for version 10.5.2.10000-5.

I've tried reinstalling multiple times and every time this happens.

The same error does not occur with 10.5.1.10000-7, but I get a 404 error when trying to access the web interface for Unity Connection. Restarting the server and/or Tomcat service doesn't solve the issue.

I'm running out of options. please help!

Jaime Valencia · ‎09-01-2015

I've done fresh installs with both of those versions and never had a problem, I'd make sure the checksum for those is OK, download them again, or ask for physical media.

If there's anything else running on the server, try turning it off and give it another shot.

HTH

java

if this helps, please rate

tarkington · ‎09-02-2015

Thanks for the reply Jaime.

I tried again with all other VM's powered-off and got the same results.

I reinstalled the 10.5.1 version and initiated the update to 10.5.2.12901 using the CLI. Now, I can get to the login page, but it doesn't take the credentials I entered during installation. It also errors out when I try to change that password using utils reset_application_ui_administrator_password .

At this point, I'm wondering if I need to wipe out ESXi or reformat the datastores somehow. I've never had problems like this during an install before. Neither CIMC or ESXi is reporting any hardware errors to me.

tarkington · ‎09-02-2015

Here's a new development: When I sent the command to restart Unity Connection, I got some error outputs:

admin:utils system restart

Do you really want to restart ?

Enter (yes/no)? yes

Appliance is being Restarted ...
Warning: Restart could take up to 5 minutes.
Stopping Service Manager...
- Service Manager shutting down services... Please Wait 2015-09-02 09:00:16,931 ERROR [Thread-8] ncs.NcsUtil - NcsClient:com.c isco.ccm.serviceability.conf.TableChangeSubscriberImpl$MyNcsClient@37fdb5 IOException: java.net.ConnectException: Connection r efused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at java.net.Socket.connect(Socket.java:528)
at java.net.Socket.<init>(Socket.java:425)
at java.net.Socket.<init>(Socket.java:208)
at com.cisco.ccm.util.ncs.NcsClient.connect(NcsClient.java:270)
at com.cisco.ccm.util.ncs.NcsClient$ReceiveThread.run(NcsClient.java:357)
2015-09-02 09:00:46,967 ERROR [Thread-8] ncs.NcsUtil - NcsClient:com.cisco.ccm.serviceability.conf.TableChangeSubscriberImpl$My NcsClient@37fdb5 IOException: java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at java.net.Socket.connect(Socket.java:528)
at java.net.Socket.<init>(Socket.java:425)
at java.net.Socket.<init>(Socket.java:208)
at com.cisco.ccm.util.ncs.NcsClient.connect(NcsClient.java:270)
at com.cisco.ccm.util.ncs.NcsClient$ReceiveThread.run(NcsClient.java:357)

Broadcast message from ccmadministrator@cchqv-uconnpub
(unknown) at 9:01 ...

The system is going down for reboot NOW!

Rob Huffman · ‎09-03-2015

Hi Andy,

I don't have an answer for the installation error you are getting, but I do think you may be hitting these two bugs at different stages of the process which are compounding the issues;

Application UI administrator name change doesn't trigger password change

CSCus70952

UC - Installation doc to include administrative account names to avoid

CSCuq79683

Cheers!

Rob

tarkington · ‎09-03-2015

Rob,

Thanks for your reply. In response, I have checked both bug reports and I don't believe I am hitting those bugs.

CSCuq79683 refers to a problem when setting a username "operator" during installation. I did not use that username during installation.

CSCus70952 refers to using the command utils reset_application_ui_administrator_name. I did try this command after getting the 404 error following my 10.5.1.10000 install, but it would not change my credentials. I experienced the 404 error immediately following a fresh installation.

I currently have TAC looking at the issue, but they have come to no conclusions yet. I was able to dump an install log via serial following a failed install of Unity Connection 10.5.2.12901. It is a pretty large log file and has no extension, so I'm not sure how to attach it to this post.

tarkington · ‎09-04-2015

Progress has been made!

TAC was able to identify an issue with the domain name entered during installation. I re-installed without using DNS and it seems to have resolved.

I can't reveal the exact domain, as it was for a customer, but it followed a format similar to this:

"[four letters].[four numbers].net" so an example would be "corp.1337.net"

If I get more clarity as to what part of that string caused the issue, I'll update.

tarkington · ‎09-08-2015

Update:

After successful installation of CUCM, Unity Connection, and IM & Presence without entering DNS information at install, here is the latest status of this bug:

Used the CLI to manually enter DNS servers and domain-name. Here is the failure in the output:

admin:set network domain corp.1337.net

Executed command unsuccessfully
corp.1337.net is an invalid domain name.

I have changed the number in the domain-name to protect customer privacy, but it is a 4-digit number.

At this time, I am trying to install using 11.x media to see if the bug still occurs.

This seems like a major issue. This should be a valid domain-name....our customer uses this format in production and suffers no issues as a result. We have installed Unified Communications operating systems in customer environments which use numbers in their domain-names successfully before, so why does this format cause such a show-stopping error?

Any clues, workarounds, or input is greatly appreciated.

tarkington · ‎09-11-2015

Latest Update:

Cisco has created a bug for this: CSCuw20063

https://tools.cisco.com/bugsearch/bug/CSCuw20063

Rob Huffman · ‎09-11-2015

Hi Andy,

Thanks for posting back with your resolution here (+5). This type of kind gesture and follow-up will help others down the road! I'm surprised they only gave it a Severity level - 3 but at least we know the issue now.

Cheers!

Rob