Restart CUCM error message "Restart operation appears to be stuck"

[voip7372]

Hi.  I don't recall seeing this in the past and as far as I can tell, I only noticed this after the system was updated from 10.5.1 to 10.5.2.  I have a publisher and two subscriber servers.  I see this message on all three servers when I restart them.  It does restart and everything else works normally, but every time I restart the servers I have to wait for this long delay and then finally the server will restart.  

Do you know what generally causes this "Restart operation appears to be stuck" message to appear?

Here is the output from the server when I restart one of them:

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...

Restart operation appears to be stuck

Would you like to force the Restart?

continue Restart (yes/no)?
Broadcast message from admin@servername
        (unknown) at 19:15 ...

The system is going down for reboot NOW!

[Vivek Batra]

Although below bug is not mentioned for CUCM 10 but having the same symptom;

https://tools.cisco.com/bugsearch/bug/CSCtu33229/?referring_site=bugquickviewclick

- Vivek

[Carlo Poggiarelli]

Hi.

Maybe you are hitting this bug.

https://tools.cisco.com/bugsearch/bug/CSCur89511/?referring_site=bugquickviewclick

Please try to upgrade to the latest service release which is 10.5(2)SU2a

HTH

Regards

Carlo

[voip7372]

Thanks to both of you.  If it's just a bug that won't affect anything else and only the delayed restart is what I'll experience, I'll just wait for the next time we do another major update. 

I'm on 10.5(2)SU2a right now and see this error.  Another bug I've run into on this release is a bug where the server automatically prefixes 00 to new +E164 DN's I create if I create more than one at a time.  I opened a case with TAC about that and they did confirm it's a bug on this release but didn't update that bug notice to show that this release is affected to.  So, I can imagine this bug with the restart being stuck isn't updated to show this release is affected as well.  

System version: 10.5.2.12901-1

VMware Installation: 4 vCPU Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz, disk 1: 110Gbytes, 6144Mbytes RAM, Partitions aligned