Voice over IP Cisco - CallProcessingNodeCpuPegging Notice

This is Interesting: Free IT Magazines  
Home > Archive > Voice over IP Cisco > December 2007 > CallProcessingNodeCpuPegging Notice





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author CallProcessingNodeCpuPegging Notice
Weigand, John V.

2007-12-26, 7:11 pm

Serious Medicine for the Defense R

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: jvw@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.

Matthew Saskin

2007-12-26, 7:11 pm

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 =AE <http://www.medicineforthedefense.co=

m/>
> =


> =


> =


> =


> 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=3D 92, %User=3D 33, %System=3D 53, %Nice=

=3D 0, =

> %Idle=3D 8, %IOWait=3D 4, %softirq=3D 1, %irq=3D 0. For processor instanc=

e =

> _Total: %CPU=3D 91, %User=3D 34, %System=3D 50, %Nice=3D 0, %Idle=3D 9, %=

IOWait=3D =

> 3, %softirq=3D 3, %irq=3D 0. For processor instance 0: %CPU=3D 90, %User=

=3D 34, =

> %System=3D 47, %Nice=3D 0, %Idle=3D 10, %IOWait=3D 2, %softirq=3D 6, %irq=

=3D 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=3D 92, %User=3D 31, %Syste=

m=3D =

> 54, %Nice=3D 0, %Idle=3D 8, %IOWait=3D 5, %softirq=3D 2, %irq=3D 0. For p=

rocessor =

> instance _Total: %CPU=3D 93, %User=3D 31, %System=3D 52, %Nice=3D 0, %Idl=

e=3D 7, =

> %IOWait=3D 5, %softirq=3D 4, %irq=3D 1. For processor instance 0: %CPU=3D=

95, =

> %User=3D 32, %System=3D 51, %Nice=3D 0, %Idle=3D 5, %IOWait=3D 5, %softir=

q=3D 6, =

> %irq=3D 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@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com> =


> <mailto:jvw@medicineforthedefense.com>jvw@medicineforthedefense.com =


> <mailto:jvw@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

Weigand, John V.

2007-12-26, 7:11 pm

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@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 b
y 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 prohib
ited. 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@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@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>jvw@medicineforthedefense.com
> <mailto:jvw@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

Ryan Ratliff

2007-12-27, 1:12 am

The dd process is what we use to copy data. 17% to CAR scheduler as the
biggest user seems ok to me for 3AM.


-Ryan
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Weigand, John V.
Sent: Wednesday, December 26, 2007 5:56 PM
To: Matthew Saskin
Cc: cisco Voip
Subject: Re: [cisco-voip] CallProcessingNodeCpuPegging Notice

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@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@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@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>jvw@medicineforthedefense.com
> <mailto:jvw@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Weigand, John V.

2007-12-27, 1:12 am

Serious Medicine for the Defense R

Cool, then I won't worry about it. Thanks so much!




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@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 b
y 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 prohib
ited. 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: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Wednesday, December 26, 2007 9:40 PM
To: Weigand, John V.; 'Matthew Saskin'
Cc: 'Cisco Voip'
Subject: RE: [cisco-voip] CallProcessingNodeCpuPegging Notice

The dd process is what we use to copy data. 17% to CAR scheduler as the
biggest user seems ok to me for 3AM.


-Ryan
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Weigand, John
V.
Sent: Wednesday, December 26, 2007 5:56 PM
To: Matthew Saskin
Cc: cisco Voip
Subject: Re: [cisco-voip] CallProcessingNodeCpuPegging Notice

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@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@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@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>
> <mailto:jvw@medicineforthedefense.com>jvw@medicineforthedefense.com
> <mailto:jvw@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Wes Sisk

2007-12-27, 1:11 pm

________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com