[cisco-voip] CallProcessingNodeCpuPegging

[Voll, Scott]

Kevin-

 

Thanks for the reply..... here is what I know.

 

Pub:

 CDR directory - 0 files / folders

 CMR Dirctory - 0 Files / Folders

 Bad directory - 2695 files

 

Sub:

 CDR directory - 0 files / folders

 CMR Dirctory - 0 Files / Folders

 

I just restarted the CDR insert service on the PUB.

 

Why do I want to trouble shoot further before rebooting?  Seems as it's
windows it might be a better solution.

 

Scott

________________________________

From: Kevin Thorngren [mailto:kthorngr at cisco.com] 
Sent: Monday, July 10, 2006 8:59 AM
To: Voll, Scott
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CallProcessingNodeCpuPegging

 

This may be a separate issue. 

 

If you are getting a build up of thousands of files in one of the
following directories then you would see the System process spike the
CPU each time the folder is accessed. 

 

C:\Program Files\Cisco\CallDetail\CDR 

C:\Program Files\Cisco\CallDetail\CMR 

C:\Program Files\Cisco\CallDetail\BAD 

 

But I would suspect that you would see these spikes throughout the day,
each time a file is copied over from one of the Subscribers. I would
recommend waiting until after hours before checking to see how many
files are in these folders as you run the possibility of spiking the CPU
if there are many thousands of files. 

 

Maybe a restart of the CDR Insert service would resolve the issue. Again
I would wait for after hours in case of a CPU spike. You might want to
enable the CDR Insert traces to troubleshoot the problem before doing
any of the restarts/reboots. 

 

I would recommend starting a perfmon log of Processor usage to find out
which process is spiking the CPU. 

 

Kevin 

 

On Jul 10, 2006, at 11:35 AM, Voll, Scott wrote: 

	 

	I see this in the event log: 

	  

	Event ID 3 

	Source:  Cisco Database Layer 

	  

	Error: kErrorCDRFilesBackingUp - CDR flat files are backing up. 

	  App ID: Cisco Database Layer Monitor 

	  Cluster ID: CMPUB-Cluster 

	  Node ID: CMPUB 

	Explanation: CDR flat files are not being removed.  On the
primary CDR server, verify that the InsertCDR service is running and
properly configured. On a server not the primary, verify that the
location for collecting CDR files is accessible via the network. 

	Recommended Action: Set trace for InsertCDR service to detailed
and look for errors in the trace.  Check enterprise CDR parameters for
accuracy.. 

	  

	I went into the Services and all look to be running.  So I'm not
sure what's up.  I will be rebooting it tonight. 

	  

	Scott 

	  

	  

	 

	From: Kevin Thorngren [mailto:kthorngr at cisco.com] 

	Sent: Monday, July 10, 2006 8:01 AM 

	To: Voll, Scott 

	Cc: cisco-voip at puck.nether.net 

	Subject: Re: [cisco-voip] CallProcessingNodeCpuPegging 

	  

	Do you know which process is pegging the CPU? 

	  

	Kevin 

	On Jul 10, 2006, at 10:52 AM, Voll, Scott wrote: 

		  

		I installed OS 4.2.sr8 and since then I have been
getting CPU pegging out around the midnight hour.  I believe it's the
CDR flat not getting truncated. 

		  

		Has anyone else seen this? 

		  

		Scott 

		_______________________________________________ 

		cisco-voip mailing list 

		cisco-voip at puck.nether.net 

		https://puck.nether.net/mailman/listinfo/cisco-voip 

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