On 5/3/07, Basil Shubin <[EMAIL PROTECTED]> wrote:
After upgrading to zenoss 1.1.2 I've start receive messages like this:
Device: example.com
Component: ssCpuRawIdle
Severity: Error
Time: 2007/05/03 06:30:04.596
Message:
example.com CPU Utilization threshold of 2 not met: current value 0.03
and this:
Event: 'example.com CPU Utilization threshold of 2 not met: current
value 0.34'
Cleared by: 'example.com CPU Utilization threshold restored current
value: 9.30'
At: 2007/05/03 06:40:05.198
Device: example.com
Component: ssCpuRawIdle
Severity: Error
Message:
example.com CPU Utilization threshold of 2 not met: current value 0.03
1. What are this messages about?
This is the threshold set on the CPU idle data source. If your CPU is
under 2% idle it would mean that it is over 98% utilized, so an event
is generated.
2. Is this some kind of bug or I just haven't understanding about this
new features?
Not a bug in Zenoss, but if your CPU isn't actually spiked it could be
a bug in your NetSNMP agent. Take a look at this thread:
http://lists.alioth.debian.org/pipermail/pkg-net-snmp-devel/2006-August/000014.html
3. Can I ride off this messages and should I?
If you have devices that are affected by the bug, I'd recommend
upgrading their NetSNMP agent if possible. Otherwise, you could create
another sub device class for these systems and remove the ssCpuRawIdle
data source, graph and threshold from its perfConfig.
--
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
