Discussion:
HealthService.exe using lots of CPU.
(too old to reply)
Sven Wells
2007-11-02 17:49:08 UTC
Permalink
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when either node is
the active node. When the cluster is failed over to the other node, that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does seem to give
way priority to other processes as those processes need resources, but it
stays up in resources.

I have uninstalled and reinstalled the agent on one of the nodes and this is
stil happening.

Any ideas?
Rem-8
2007-11-02 20:07:51 UTC
Permalink
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when either node is
the active node. When the cluster is failed over to the other node, that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does seem to give
way priority to other processes as those processes need resources, but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes and this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Sven Wells
2007-11-27 18:17:04 UTC
Permalink
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.

Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when either node is
the active node. When the cluster is failed over to the other node, that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does seem to give
way priority to other processes as those processes need resources, but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes and this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Sven Wells
2008-01-30 01:23:02 UTC
Permalink
I am still experiencing this issue with a clustered W2K3 SP1 File Server.
Whichever node is Active will experience this issue, rendering the cluster
useless and will not allow cluster failover due to the high cpu usage. The
HealthService.exe process will consume as much cpu as possible, leaving
little for anything else to use. We have stopped and disabled the
OpsMgrHealth Service for the time being.
Is there a way to change the priority of the HealthService.exe process? Or
is there a hotfix for this posted somewhere?
There are also lots of instances of cscript present as well.

I have heard others are having the same issue, and no resolution has been
provided. This appears to be a serious issue.

Thanks,
Sven
Post by Sven Wells
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.
Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when either node is
the active node. When the cluster is failed over to the other node, that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does seem to give
way priority to other processes as those processes need resources, but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes and this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Marius Sutara [MSFT]
2008-01-30 18:32:12 UTC
Permalink
Sven, if this is SP1 RC, could you please follow steps to enable tracing
(http://blogs.msdn.com/mariussutara/archive/2008/01/21/operations-manager-2007-sp1-tracing.aspx)
so we can try to investigate what is happenning?
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara


This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
I am still experiencing this issue with a clustered W2K3 SP1 File Server.
Whichever node is Active will experience this issue, rendering the cluster
useless and will not allow cluster failover due to the high cpu usage.
The
HealthService.exe process will consume as much cpu as possible, leaving
little for anything else to use. We have stopped and disabled the
OpsMgrHealth Service for the time being.
Is there a way to change the priority of the HealthService.exe process?
Or
is there a hotfix for this posted somewhere?
There are also lots of instances of cscript present as well.
I have heard others are having the same issue, and no resolution has been
provided. This appears to be a serious issue.
Thanks,
Sven
Post by Sven Wells
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.
Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when either node is
the active node. When the cluster is failed over to the other node, that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does seem to give
way priority to other processes as those processes need resources, but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes and this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Sven Wells
2008-01-30 18:48:03 UTC
Permalink
Hi Marius,

Unfortunately this is not SP1. We are waiting for SP1 RTM to be released
before applying this.

Thanks,
Sven
Post by Marius Sutara [MSFT]
Sven, if this is SP1 RC, could you please follow steps to enable tracing
(http://blogs.msdn.com/mariussutara/archive/2008/01/21/operations-manager-2007-sp1-tracing.aspx)
so we can try to investigate what is happenning?
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
I am still experiencing this issue with a clustered W2K3 SP1 File Server.
Whichever node is Active will experience this issue, rendering the cluster
useless and will not allow cluster failover due to the high cpu usage.
The
HealthService.exe process will consume as much cpu as possible, leaving
little for anything else to use. We have stopped and disabled the
OpsMgrHealth Service for the time being.
Is there a way to change the priority of the HealthService.exe process?
Or
is there a hotfix for this posted somewhere?
There are also lots of instances of cscript present as well.
I have heard others are having the same issue, and no resolution has been
provided. This appears to be a serious issue.
Thanks,
Sven
Post by Sven Wells
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.
Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when either node is
the active node. When the cluster is failed over to the other node, that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does seem to give
way priority to other processes as those processes need resources, but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes and this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Marius Sutara [MSFT]
2008-01-30 20:23:45 UTC
Permalink
Any chance you can talk to CSS? There is a way to collect traces in binary
form, we just need to do formatting here (it should not contain customer
private data though)
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara


This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
Hi Marius,
Unfortunately this is not SP1. We are waiting for SP1 RTM to be released
before applying this.
Thanks,
Sven
Post by Marius Sutara [MSFT]
Sven, if this is SP1 RC, could you please follow steps to enable tracing
(http://blogs.msdn.com/mariussutara/archive/2008/01/21/operations-manager-2007-sp1-tracing.aspx)
so we can try to investigate what is happenning?
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
I am still experiencing this issue with a clustered W2K3 SP1 File Server.
Whichever node is Active will experience this issue, rendering the cluster
useless and will not allow cluster failover due to the high cpu usage.
The
HealthService.exe process will consume as much cpu as possible, leaving
little for anything else to use. We have stopped and disabled the
OpsMgrHealth Service for the time being.
Is there a way to change the priority of the HealthService.exe process?
Or
is there a hotfix for this posted somewhere?
There are also lots of instances of cscript present as well.
I have heard others are having the same issue, and no resolution has been
provided. This appears to be a serious issue.
Thanks,
Sven
Post by Sven Wells
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.
Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or more? We
have a cluster on which both nodes are experiencing this when
either
node is
the active node. When the cluster is failed over to the other
node,
that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does
seem
to give
way priority to other processes as those processes need resources, but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes
and
this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Sven Wells
2008-01-30 21:05:01 UTC
Permalink
Excuse my ignorance, but what is CSS?

Thanks,
Sven
Post by Marius Sutara [MSFT]
Any chance you can talk to CSS? There is a way to collect traces in binary
form, we just need to do formatting here (it should not contain customer
private data though)
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
Hi Marius,
Unfortunately this is not SP1. We are waiting for SP1 RTM to be released
before applying this.
Thanks,
Sven
Post by Marius Sutara [MSFT]
Sven, if this is SP1 RC, could you please follow steps to enable tracing
(http://blogs.msdn.com/mariussutara/archive/2008/01/21/operations-manager-2007-sp1-tracing.aspx)
so we can try to investigate what is happenning?
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
I am still experiencing this issue with a clustered W2K3 SP1 File Server.
Whichever node is Active will experience this issue, rendering the cluster
useless and will not allow cluster failover due to the high cpu usage.
The
HealthService.exe process will consume as much cpu as possible, leaving
little for anything else to use. We have stopped and disabled the
OpsMgrHealth Service for the time being.
Is there a way to change the priority of the HealthService.exe process?
Or
is there a hotfix for this posted somewhere?
There are also lots of instances of cscript present as well.
I have heard others are having the same issue, and no resolution has been
provided. This appears to be a serious issue.
Thanks,
Sven
Post by Sven Wells
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.
Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service
agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or
more? We
have a cluster on which both nodes are experiencing this when
either
node is
the active node. When the cluster is failed over to the other
node,
that
node's HealthService.exe process will show high utilization within the
Windows Task Manager, anywhere from 40-57% constantly. It does
seem
to give
way priority to other processes as those processes need resources,
but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes
and
this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB server of
very important application was dead. This is really an issue which MS
should look into within SP1. After I restarted the agent it was again
low down.
Marius Sutara [MSFT]
2008-01-30 21:57:00 UTC
Permalink
Sorry, that was definitely my fault. I meant to say if you can raise this
issue with microsoft. (I believe that CSS stands for Customer Support and
Solutions)
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara


This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
Excuse my ignorance, but what is CSS?
Thanks,
Sven
Post by Marius Sutara [MSFT]
Any chance you can talk to CSS? There is a way to collect traces in binary
form, we just need to do formatting here (it should not contain customer
private data though)
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
Hi Marius,
Unfortunately this is not SP1. We are waiting for SP1 RTM to be released
before applying this.
Thanks,
Sven
Post by Marius Sutara [MSFT]
Sven, if this is SP1 RC, could you please follow steps to enable tracing
(http://blogs.msdn.com/mariussutara/archive/2008/01/21/operations-manager-2007-sp1-tracing.aspx)
so we can try to investigate what is happenning?
--
Marius Sutara
Developer
http://blogs.msdn.com/MariusSutara
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of attachments are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Post by Sven Wells
I am still experiencing this issue with a clustered W2K3 SP1 File Server.
Whichever node is Active will experience this issue, rendering the cluster
useless and will not allow cluster failover due to the high cpu usage.
The
HealthService.exe process will consume as much cpu as possible, leaving
little for anything else to use. We have stopped and disabled the
OpsMgrHealth Service for the time being.
Is there a way to change the priority of the HealthService.exe process?
Or
is there a hotfix for this posted somewhere?
There are also lots of instances of cscript present as well.
I have heard others are having the same issue, and no resolution has been
provided. This appears to be a serious issue.
Thanks,
Sven
Post by Sven Wells
Previously I stated that the processor was running 40-57%, it is actually
100% or very close to it.
I have had to uninstall the agent to keep this from happening.
Any ideas as to why this may be happening?
Post by Rem-8
Post by Sven Wells
Has anyone had an issue with the Operations Manager Health Service
agent,
healthservice.exe, service/process taking lots of CPU, ie. 50% or
more? We
have a cluster on which both nodes are experiencing this when
either
node is
the active node. When the cluster is failed over to the other
node,
that
node's HealthService.exe process will show high utilization
within
the
Windows Task Manager, anywhere from 40-57% constantly. It does
seem
to give
way priority to other processes as those processes need resources,
but it
stays up in resources.
I have uninstalled and reinstalled the agent on one of the nodes
and
this is
stil happening.
Any ideas?
We've had an issue too on that, although our HealthService.exe on
physical node of a cluster ate nearly 100% of CPU and the DB
server
of
very important application was dead. This is really an issue
which
MS
should look into within SP1. After I restarted the agent it was again
low down.
Loading...