[cisco-voip] Weird behaviour after a reboot

[Voll, Scott]

What OS?  4.2sr7 had a bug where CCM caused 100% CPU utilization.  SR7a
fixed it.

 

scott

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nathan Reeves
Sent: Monday, June 26, 2006 7:04 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Weird behaviour after a reboot

 

Saw an issues with our CCM yesterday which I'd be interested to hear if
anyone else has seen similar.

 

Had a bugcheck reboot on the SUB early Sunday morning.  Everything
failed back to the SUB once it came back up, but most of the AC Pilot
Points were not working.  Was seeing CPU spikes on both the SUB and PUB.
Rebooted the PUB and things went back to normal on that server.   Was
still seeing CPU spikes on the SUB (mostly caused by CTIManager.exe and
CCM.exe).

 

Tried to get the AC Pilot Points working during the day with no luck.
Completed a SUB reboot in the evening and when the server came back up,
none of the devices would fail back.  Saw errors in the event log to do
with CTIManager, Cisco Extended Functions and RIS Data Collector all
terminating unexpectedly.  Completed a second reboot and this time
things came up normally, and devices failed back to the SUB. 

 

I'm trying to work out why I would see services fail like this on one
restart, yet work normally on the next restart.  Our only recent change
has been the installation of 4.1.3 Sr3a from 4.1.3 Sr2.  Anyone ever
seen this kind of issue with restarts causing CCM to not come up
cleanly? 

 

Thanks

 

Nathan 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060627/7bebdf46/attachment.html