Help locating upgrade log for CUCM

[thowes]

I performed an upgrade yesterday on my CUCM 8.0(2) switch to the latest 8.5(1)SU1, but the upgrade failed.  The upgrade was still going when I left last night and when I got into work today the switch was still at 8.0(2) so that was when I knew something was wrong.  I am now unable to login to the web interface (other than OS Administration or Disaster Recovery) with any user, as I get an error that says "Non Defined IMS Exception".

Has anybody seen this type of problem before?  Where can I find the upgrade log?  I am not sure it will help me, but it would be nice to know why the upgrade failed.

Unfortunately I didn't make a backup before the upgrade, but this switch is only for testing so other than the headache this is giving me there aren't any problems being caused by the current state of the switch.

[Christos Georgiadis]

As far as I know during the upgrade of callmanager the active partition is not touched. The upgrade writes on the inactive partition only.

You can download the upgrade logs via RTMT . Traces and log central ---> Collect logs ---> Hit next ---> Click on the install and upgrade logs

Choose the active/inactive partition and that's it

regards,

Christos

[thowes]

Unfortunately I don't already have the RTMT installed, and since I can't login to the web interface I can't download/install it.  Is there another way to access the logs?  Maybe using the CLI?  Or is the latest download of the RTMT hidden someplace on Cisco.com?

[Joseph Martini · Accepted solution]

You can download the logs from the command line using "file get install /*" which will ask for an SFTP server to copy the files to.

[thowes]

After much headache I was able to get this to work.  My SFTP server was using port 24 (not the default 22) and cucm couldn't connect to the server.  Once I decided to try rearranging the ports and setting the SFTP server to 22 I was able to get it to work.

Thanks for the help, joemar!

[Stephen Sober]

Upgrade log can be found here:

admin:file view install system-history.log

[Jaime Valencia]

I think he was actually looking for the upgrade/install logs that explain exactly what was happening during the procedure to find out why it failed, those are indeed in the install partition, but look something like install_log_2015-07-19.23.11.48.log