04-06-2019 05:35 AM - edited 04-06-2019 05:37 AM
I am doing a PCD upgrade for the IMP servers and it cannot continue after the first server because the (PAWS) service is down amongst a few others on the primary. Using the 12.5(1) latest upgrade file.
What is the fix for this Cisco?
10-08-2019 06:12 PM
10-08-2019 05:49 PM
Ended up having to open a TAC case. It was an issue where the server was built with the hostname capital letter, node name in lower case, and it caused issue with the hosts file. TAC had to get root access and issue a command to modify the host file.
10-08-2019 06:13 PM
06-13-2020 06:47 AM
I know this is OLD thread and probably might have solved this issue just for any other user how faces this issue for Cisco Presence engine stuck in starting
07-31-2020 01:49 PM
Beyond the referenced bugs many times this symptom of service stuck starting is related to DNS and name resolution. From the admin CLI use the command "show tech network hosts" and pay special attention to the /etc/hosts and localhost sections. Any variations here will likely require a TAC case and remote access to resolve.
Things to check without TAC:
1. ensure forward and reverse DNS resolution of the server name, ensure server is pointing to correct DNS server. Fix any DNS issues and reboot the servers.
2. examine the output of admin CLI command"show tech network hosts".
If you discover any inconsistencies then open a TAC case for further assistance.
01-19-2020 01:30 AM
Great post Michael. +5
I ran into this scenario when upgrading from 10.5.2 to 12.5.1. After issuing this command on each IM&P node, the services started within 5 minutes. No reboot required.
01-19-2020 04:44 PM
Great to hear this worked for you too :)
05-09-2021 02:56 AM
Be careful with this command.
While disabling the replication-sync will allow the services to start up - I do not believe it is not the root cause of the issue.
The reason the services are not start is likely because the database replication is not started or completing.
When replication-sync is enabled it is designed to not allow other services to start:
"The Cisco Replication Watcher service blocks other services from starting until database replication is setup and functioning normally."
The issue I experienced (12.5 SU4) was that the subscriber IMP server did not ask for replication to be initialized.
To fix the issue I had to reset dereplication.
I recommend you check using utils dbreplication runtimestate
And use this reference if necessary to fix.
Gerry
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