[cisco-voip] CallProcessingNodeCpuPegging Notice
Weigand, John V.
jvw at medicineforthedefense.com
Wed Dec 26 17:55:31 EST 2007
Serious Medicine for the Defense R
It's actually CCM5... Stupid Linux appliance. It looks like from the
errors though that it's processes "carschlr" (which I assume is the CAR
Scheduler) and "dd" (no idea what that is).
John V. Weigand
Help Desk Support
Litigation Management, Inc.
300 Allen-Bradley Drive
Suite 200
Mayfield Heights, OH 44124
Tel:
Fax: 440-484-2020
Cell:
email: jvw at medicineforthedefense.com
PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail is intended for the named recipients only. It may contain privileged and confidential material and may be protected under law by the Health Insurance Portability and Accountability Act. Any use of this information by anyone other than the intended receiver is prohibited. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this electronic e-mail or by calling (800) 778-5424. Please delete it from your computer. Thank you.
From: Matthew Saskin [mailto:matt at saskin.net]
Sent: Wednesday, December 26, 2007 5:43 PM
To: Weigand, John V.
Cc: Cisco Voip
Subject: Re: [cisco-voip] CallProcessingNodeCpuPegging Notice
When it's occurring, log onto the server in question and use task
manager to see what process is causing the high CPU utilization. I
actually think RTMT may tell you the process name responsible - not sure
as I don't use it for alerting.
Depending on what application/service is causing high CPU util, you may
need to speak with TAC. There are a few different defects in the
earlier 4x code (4.0/4.1) involving high cpu utilization and the DBL
Monitor service (aupair.exe)
-matt
Weigand, John V. wrote:
>
>
> Litigation Management
>
>
>
> Serious Medicine for the Defense (r)
<http://www.medicineforthedefense.com/>
>
>
>
>
> On and off for the past week while I was out of the office, we were
> getting these errors from RTMT. Any idea what could be causing it, or
> how to troubleshoot it? Should I just talk to TAC? Thanks!
>
>
>
> *From:* RTMT_Admin
>
> *Sent:* Wednesday, December 26, 2007 3:05 AM
> *To:* Weigand, John V.
>
> *Subject:* [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging
>
>
>
> On Wed Dec 26 03:05:18 EST 2007 on node 10.255.251.10. Processor load
> over 90 Percent. dd (32 percent) uses most of the CPU. Processor_Info:
> For processor instance 1: %CPU= 92, %User= 33, %System= 53, %Nice= 0,
> %Idle= 8, %IOWait= 4, %softirq= 1, %irq= 0. For processor instance
> _Total: %CPU= 91, %User= 34, %System= 50, %Nice= 0, %Idle= 9, %IOWait=
> 3, %softirq= 3, %irq= 0. For processor instance 0: %CPU= 90, %User=
34,
> %System= 47, %Nice= 0, %Idle= 10, %IOWait= 2, %softirq= 6, %irq= 1.
>
>
>
> *From:* RTMT_Admin
> *Sent:* Tuesday, December 25, 2007 3:05 AM
> *To:* Weigand, John V.
> *Subject:* [RTMT-ALERT-StandAloneCluster] CallProcessingNodeCpuPegging
>
>
>
> On Tue Dec 25 03:04:51 EST 2007 on node 10.255.251.10. Processor load
> over 90 Percent. carschlr (17 percent) uses most of the CPU.
> Processor_Info: For processor instance 1: %CPU= 92, %User= 31,
%System=
> 54, %Nice= 0, %Idle= 8, %IOWait= 5, %softirq= 2, %irq= 0. For
processor
> instance _Total: %CPU= 93, %User= 31, %System= 52, %Nice= 0, %Idle= 7,
> %IOWait= 5, %softirq= 4, %irq= 1. For processor instance 0: %CPU= 95,
> %User= 32, %System= 51, %Nice= 0, %Idle= 5, %IOWait= 5, %softirq= 6,
> %irq= 1.
>
>
>
>
> *John V. Weigand*
> Help Desk Support
>
> Litigation Management, Inc.
> 300 Allen-Bradley Drive
> Suite 200
> Mayfield Heights, OH 44124
>
>
>
>
>
>
> Tel:
> Fax: 440-484-2020
> Cell:
> email: <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>
> <mailto:jvw at medicineforthedefense.com>jvw at medicineforthedefense.com
> <mailto:jvw at medicineforthedefense.com>
>
>
> PRIVILEGE AND CONFIDENTIALITY NOTICE
>
> The information in this electronic mail is intended for the named
> recipients only. It may contain privileged and confidential material
and
> may be protected under law by the Health Insurance Portability and
> Accountability Act. Any use of this information by anyone other than
the
> intended receiver is prohibited. If the reader of this message is not
> the intended recipient, you are hereby notified that any
dissemination,
> distribution, copying, or other use of this message or its attachments
> is strictly prohibited. If you have received this message in error,
> please notify the sender immediately by replying to this electronic
> e-mail or by calling (800) 778-5424. Please delete it from your
> computer. Thank you.
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list