09-30-2024 01:08 PM
Anyone else having issues installing this COP file? I see it listed a requirement in the upgrade guide and TAC confirms I should install this file before Fresh Install with Data import to version 15 .
The cop file will install on some nodes and not others. What Happens is the cop file stays stuck in a status of "Running" as seen in the OS admin web page. If I check via CLI utils upgrade status the output shows failed yet the OS admin web page says running.
If I check the install logs I can see the the cop file install starts and then fails. The command file view install system-history.log cli output shows old 8.6 install in the history from years ago and seems to match the bug for the cop file, and then at the end of the log the failure of the cop file can be seen. I would think if the cop file is not needed it would gracefully shut down and state that in the logs and or OS admin page.
Is there a bug in this bug fix cop file? Again it works on some nodes in the cluster and not others....
10-04-2024 12:54 AM - edited 10-04-2024 12:56 AM
Hi,
I had the same issue, cop file installation through CLI failed in CUCM 11.0.1. Did you manage to solve the issue?
By the logs below it seems that in my case i don't need the cop but I didn't have opportunity yet to run PCD to see if will be able to direct migrate to 15 or not.
BR
10/04/2024 08:37:18 #####################################################################################
10/04/2024 08:37:18
10/04/2024 08:37:18 Starting ciscocm.CSCwi52160_15-direct-migration COP file install
10/04/2024 08:37:18
Product : callmanager installation is supported.
############
10/04/2024 08:37:19 /etc/pam.d/system-auth is ready for direct migration, no additional changes needed. COP install will now exit.
[24/10/04_08:37:19] locale_install.sh: ERROR: Copstart script of ciscocm.CSCwi52160_15-direct-migration_v1.0.k4.cop failed
Installation of ciscocm.CSCwi52160_15-direct-migration_v1.0.k4.cop.sha512 failed
Copstart script of ciscocm.CSCwi52160_15-direct-migration_v1.0.k4.cop failed
10-04-2024 03:16 PM
I tried to install the cop file via CLI as well. I have the same message both when installing via CLI or via the OS admin web page
system-auth is ready for direct migration, no additional changes needed. COP install will now exit.
yet when using the OS admin webpage the webpage just locks up with a status of running and I have to click cancel to get out of that screen.
I opened a TAC case and they cant tell me why the OS admin webpage hangs but they are telling me to move forward with the upgrade as this node should not need the cop file based on that CLI output above.
I have the upgrade change window planned in two weeks, hope all works out well.
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