03-25-2015 12:40 PM - edited 03-19-2019 09:23 AM
We have attempted to upgraded a current CUPS server to IM&P and it has failed at the same point 3 times. I engaged TAC and they suggested upgrading to the latest version 8.6 and then attempt, the upgrade to 8.6 worked without issue but the 10.5 upgrade failed at the same point. The failure occurs when the database component is at 90% installed, then a screen that is similar to the one that states that the system is going to reboot comes up and states an error occurred during the post install. This server was part of an existing 8.6 CUCM cluster that has now been upgraded with issues to 10.5. The customer is ok with simply doing a fresh install and moving forward. If we do go this route is there anything I need to do the CUCM to clear out the old presence server? Or can we simply just do the install like there was never a presence node involved.
here is the snippet that was emailed when it failed:
An error occured during the upgrade
Download the log provided. Reboot the system to ensure services affected by the upgrade process are functioning properly.
========================================================
=============== Advanced error messages =================
* Refresh upgrade prepare was successful. The upgrade will continue after automatically rebooting.
========================================================
========= The last few lines from install log =========
03/25/2015 11:46:50 InstallWizard|decryptData : enter|<LVL::Info>
03/25/2015 11:46:50 InstallWizard|decryptData Exit Success|<LVL::Info>
03/25/2015 11:47:09 InstallWizard|Platform Install: view|<LVL::Info>
03/25/2015 14:45:58 installdb|--- --- End -- Performing DB Load and Transforming Copy
03/25/2015 14:47:30 IPM|Internal Error, File:ipm.c:2011, Function: ipmReadNormalizedInputLine(), "/usr/local/cm/script/cm-dbl-install RU PostInstall 10.5.2.20000-1 8.6.5.14900-3 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " failed (1)|<LVL::Critical>
03/25/2015 14:47:32 IPM| end-of-session "Installing database component": 1941.674 secs.|<LVL::Info>
03/25/2015 14:47:32 IPM|Close progress meter "Component Install"|<LVL::Info>
03/25/2015 14:47:32 component_install|Writing database into /common/log/install/component_failed.xml file.|<LVL::Info>
03/25/2015 14:47:32 component_install|/common/log/install/component_failed.xml created : 0|<LVL::Info>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:02 2015 cm-dbms-install DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.ParamObject.validate DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.ParamObject.validate DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doActionL2Update DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doActionL2Update DEBUG: Inside doActionL2Update ...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2Post DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2Post DEBUG: Inside doL2Post ...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doCreateLogDirectory DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doCreateLogDirectory DEBUG: Verifying SDI directory [/var/log/active/cm/trace/dbl/sdi]|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doCreateLogDirectory DEBUG: chown database.ccmbase /var/log/active/cm/trace/dbl/sdi|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doCreateLogDirectory DEBUG: chmod 775 /var/log/active/cm/trace/dbl/sdi|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doCreateLogDirectory DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2Post_setPublisher DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2Post_setPublisher DEBUG: Inside doL2Post_setPublisher...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2Post_setPublisher DEBUG: No publisher record migrated.|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2Post_setPublisher DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2_migrateDB DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.doL2_migrateDB DEBUG: Inside doL2_migrateDB...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.fixSQLLibPaths DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.fixSQLLibPaths DEBUG: Inside fixSQLLibPaths....|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.fixSQLLibPaths DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.fixSQLLibPaths DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.fixSQLLibPaths DEBUG: Inside fixSQLLibPaths....|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.fixSQLLibPaths DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.installdb DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:12 2015 cm-dbl-install.installdb DEBUG: Inside installdb ...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:13 2015 cm-dbl-install.installdb DEBUG: python "/usr/local/cm/bin/dbl" start --safe --nopreflight --log=/common/log/install/capture.txt|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:13 2015 dblstart-plugin.run DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:13 2015 dblstart-plugin.run DEBUG: Start DBMS|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 dblstart-plugin.run DEBUG: do preflight|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 dblstart-plugin.run DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.installdb DEBUG: rm -f /tmp/*.txt /tmp/*.log /tmp/*.err /var/log/active/cm/trace/dbl/sdi/psqlx /tmp/*.bin /tmp/af* /tmp/shmem*|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.installdb DEBUG: Disk size present in dbl/prefs is 80|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.getPublisherFromPrefs DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.getPublisherFromPrefs DEBUG: Inside getPublisherFromPrefs...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.getPublisherFromPrefs DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.importdb DEBUG: -->|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.importdb DEBUG: Inside importdb ...|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:28 2015 cm-dbl-install.importdb DEBUG: su - informix -c "echo 'create database ccm8_6_5_14900_3 in refresh with log' | dbaccess sysmaster - " >/var/log/active/cm/trace/dbl/sdi/createold.log 2>&1|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:29 2015 cm-dbl-install.importdb DEBUG: su -l informix -s /bin/sh -c 'source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; "/usr/local/cm/bin/installdb" -o "DSN=ccm_b" -v /common/component/database'|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:43:37 2015 cm-dbl-install.importdb DEBUG: su -l informix -s /bin/sh -c 'source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; "/usr/local/cm/bin/installdb" -o "DSN=ccm_b" -c /common/component/database'|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:55 2015 cm-dbl-install.importdb DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:55 2015 cm-dbl-install.installdb DEBUG: Adding dbfuncs for pre- data-migrate|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:55 2015 cm-dbl-install.installdb DEBUG: su - informix -c "dbaccess ccm8_6_5_14900_3 /usr/local/cm/db/sql/dbfuncs.sql.pathed.sql" > /var/log/active/cm/trace/dbl/sdi/dbfuncsolddb.log 2>&1|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:55 2015 cm-dbl-install.installdb DEBUG: Defining my_lower for pre- data-migrate|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:55 2015 cm-dbl-install.installdb DEBUG: su - informix -c "echo 'create function my_lower(v1 varchar(255)) returning varchar(255) with(not variant) return lower(v1); end function;' | dbaccess ccm8_6_5_14900_3" >> /var/log/active/cm/trace/dbl/sdi/dbfuncsolddb.log 2>&1|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:56 2015 cm-dbl-install.installdb DEBUG: Calling doNetworkMigration pre-'installdb -f' with executePreDataMigrate flag set to 1|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:45:56 2015 cm-dbl-install.installdb DEBUG: su -l informix -s /bin/sh -c 'source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; "/usr/local/cm/bin/installdb" -rt 36000 -i -f RU "/usr/local/cm" "/common/component/database" 10.5.2.20000-1 8.6.5.14900-3 installdb_ru.log'|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:25 2015 cm-dbl-install.installdb DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:25 2015 cm-dbl-install.doL2_migrateDB DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:25 2015 cm-dbl-install.doL2Post DEBUG: Executing command: /usr/local/cup/bin/cupl2_new.py /usr/local/cup/conf/cupl2onboot.xml import /common/component/database/cupl2.export|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:28 2015 cm-dbl-install.doL2Post DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:28 2015 cm-dbl-install.doActionL2Update DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:28 2015 cm-dbl-install DEBUG: cm-dbl-install [1]|<LVL::Debug>
03/25/2015 14:47:32 component_install|(CAPTURE) Wed Mar 25 14:47:28 2015 cm-dbl-install DEBUG: <--|<LVL::Debug>
03/25/2015 14:47:32 component_install|File:/opt/cisco/install/bin/component_install:807, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
03/25/2015 14:47:32 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:273, Function: refresh_upgrade(), failed to refresh_upgrade infrastructure_post components|<LVL::Critical>
03/25/2015 14:47:32 post_install|File:/opt/cisco/install/bin/post_install:961, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -refresh-upgrade failed (1)|<LVL::Error>
03/25/2015 14:47:32 post_install|Exiting with result 1|<LVL::Info>
03/25/2015 14:47:32 post_install|INSTALL_TYPE="Refresh Upgrade"|<LVL::Debug>
03/25/2015 14:47:32 post_install|Process refresh upgrade failure|<LVL::Info>
03/25/2015 11:47:32 InstallWizard|Platform Install: view|<LVL::Info>
03/25/2015 11:47:32 InstallWizard|openPlatformXml: Parse existing xml document /usr/local/platform/conf/platformConfig.xml.|<LVL::Info>
03/25/2015 11:47:32 InstallWizard|decryptData : enter|<LVL::Info>
03/25/2015 11:47:32 InstallWizard|decryptData Exit Success|<LVL::Info>
========================================================
Has anyone had this issue in the past?
Would be great to upgrade but we can't waste more time if it is pointless.
Thanks,
Joe
05-11-2015 12:59 PM
Hi,
I will upgrade a customer from CUPS 8.6 to IM&P 10.5(2).
I'm trying the upgrade process in my labo with a similar issue.
Did you get any alternative other than the fresh install?
Thanks
Cyril
05-11-2015 01:12 PM
We were not able to resolve the via the upgrade, a fresh install was required.
Thanks,
Joe
06-16-2015 05:58 AM
FYI
I finally upgrade the customer from 8 to 10 without issue.
CUCM from 8.6.2.23065-2 to 10.5.2.11900-3
CUPS from 8.6.4.10000-28 to 10.5.2.21900-4
08-24-2015 06:09 PM
Cyril:
I am running in the exact problem, was upgrading exactly as the version specified on both cucm and IMP fixed the issue? that is
CUCM from 8.6.2.23065-2 to 10.5.2.11900-3
CUPS from 8.6.4.10000-28 to 10.5.2.21900-4
I am no deleting the application server under the upgraded 10.5.2, and let it showed (obsolete), as i understand that the switch version of the IMP will take care of creating the new 10.5.2 presence node and delete the application server of the old cupc.
Any help and advise is appreciated.
08-25-2015 01:13 AM
Hi,
The upgrade process of the IMP will take care to migrate to IMP config (add new imp node, delete old cups application server, create UC Service, ...) to the CUCM/IMP node. It was automatic and took approx 30 min in my scenario.
HTH
Cyril
08-25-2015 07:22 AM
Cyril
thanka, but how did you got it installed? I am also failed at about 90% into the databases operation when installing the imp server. Thanks!
08-25-2015 07:46 AM
Difficult to determine what was not working in my lab when I did the first try. The second attempt was successful.
At the customer site it works at the first attempt.
I just follow the refresh upgrade procedure with the requirements that are in the documentation.
Cyril
01-10-2016 05:41 PM
The issue is that the older version of IMP server is case sensitive when you first installed using the ISO, the hostname "show status" needs to be matching the original case when you upgrade. issue "run sql select * from primary processing node" to see what's in the DB vs what's configured. TAC edited the platformconfig.xml file to fix this issue and upgrade went on..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide