TECHZEN Zenoss User Community ARCHIVE  

4.2.5 failing SNMP perf collection

Subject: 4.2.5 failing SNMP perf collection
Author: [Not Specified]
Posted: 2014-07-09 08:34

I'm getting an error in the zenperfsnmp.log :
DEBUG zen.pbclientfactory: Lost connection to ::1:8789 - [Failure instance: Traceback (failure with no frames): : Connection was closed cleanly.

Not sure why it's not working... I'm getting -NAN in my graphs which come from SNMP... Not sure what to look for, zenhub.log shows:
2014-07-08 11:17:19,801 DEBUG zen.queuepublisher: About to publish this event to the raw event queue:uuid: "f42573ce-06b2-11e4-95ab-525400f651d1"
created_time: 1404832639799
event_class: "/App/Start"
actor {
element_type_id: DEVICE
element_identifier: "localhost"
element_sub_type_id: COMPONENT
element_sub_identifier: "zenhub"
}
summary: "zenhub started"
severity: SEVERITY_CLEAR
event_key: ""
first_seen_time: 1404832639799
, with this routing key: zenoss.zenevent.app.start
2014-07-08 11:17:19,804 DEBUG zen.zenoss.protocols.amqp: Connecting to RabbitMQ...
2014-07-08 11:17:19,805 DEBUG zen.protocols: Creating exchange: zenoss.zenevents.raw
2014-07-08 11:17:19,806 DEBUG zen.zenoss.protocols.amqp: Publishing with routing key zenoss.zenevent.app.start to exchange zenoss.zenevents.raw
2014-07-08 11:17:22,681 DEBUG zen.ZenHub: Registered 4 invalidation filters.
2014-07-08 11:17:22,718 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))
2014-07-08 11:17:22,718 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))
2014-07-08 11:17:22,719 DEBUG zen.ZenHub: Starting /bin/nice -n +5 /opt/zenoss/bin/zenhubworker run -C /opt/zenoss/var/zenhub/localhost_worker.conf
2014-07-08 11:17:22,724 DEBUG zen.ZenHub: Starting /bin/nice -n +5 /opt/zenoss/bin/zenhubworker run -C /opt/zenoss/var/zenhub/localhost_worker.conf
2014-07-08 11:17:22,730 DEBUG zen.Events: =============== incoming event ===============
2014-07-08 11:17:22,730 DEBUG zen.Events: Got a localhost zenhub heartbeat event (timeout 90 sec).
2014-07-08 11:17:22,734 DEBUG zen.zenoss.protocols.amqp: Connecting to RabbitMQ...
2014-07-08 11:17:22,736 DEBUG zen.protocols: Creating exchange: zenoss.heartbeats
2014-07-08 11:17:22,737 DEBUG zen.zenoss.protocols.amqp: Publishing with routing key zenoss.heartbeat.localhost to exchange zenoss.heartbeats

RabbitMQ logs look like:
=INFO REPORT==== 9-Jul-2014::11:09:41 ===
accepting AMQP connection <0.853.0> (127.0.0.1:51912 -> 127.0.0.1:5672)

=INFO REPORT==== 9-Jul-2014::11:09:48 ===
accepting AMQP connection <0.887.0> ([::1]:56472 -> [::1]:5672)

=INFO REPORT==== 9-Jul-2014::11:09:51 ===
accepting AMQP connection <0.895.0> ([::1]:56477 -> [::1]:5672)

=INFO REPORT==== 9-Jul-2014::11:09:52 ===
accepting AMQP connection <0.903.0> (127.0.0.1:51926 -> 127.0.0.1:5672)

=INFO REPORT==== 9-Jul-2014::11:09:56 ===
accepting AMQP connection <0.917.0> ([::1]:56488 -> [::1]:5672)

=INFO REPORT==== 9-Jul-2014::11:10:00 ===
accepting AMQP connection <0.926.0> ([::1]:56495 -> [::1]:5672)

=INFO REPORT==== 9-Jul-2014::11:10:00 ===
accepting AMQP connection <0.935.0> ([::1]:56500 -> [::1]:5672)

=INFO REPORT==== 9-Jul-2014::11:10:12 ===
accepting AMQP connection <0.944.0> ([::1]:56507 -> [::1]:5672)

=INFO REPORT==== 9-Jul-2014::11:10:12 ===
accepting AMQP connection <0.948.0> ([::1]:56508 -> [::1]:5672)

Recreated queues and see zenhub.log showing:
2014-07-09 11:11:25,976 INFO zen.pbclientfactory: Initial connect timed out after 60 seconds
2014-07-09 11:11:25,977 DEBUG zen.pbclientfactory: Lost connection to ::1:8789 - [Failure instance: Traceback (failure with no frames): : Connection was closed cleanly.
]
2014-07-09 11:11:28,919 DEBUG zen.pbclientfactory: Starting connection...
2014-07-09 11:11:28,919 INFO zen.zenperfsnmp: Attempting to connect to zenhub
2014-07-09 11:12:28,925 INFO zen.pbclientfactory: Initial connect timed out after 60 seconds
2014-07-09 11:12:28,927 DEBUG zen.pbclientfactory: Lost connection to ::1:8789 - [Failure instance: Traceback (failure with no frames): : Connection was closed cleanly.
]
2014-07-09 11:12:37,559 DEBUG zen.pbclientfactory: Starting connection...
2014-07-09 11:12:37,559 INFO zen.zenperfsnmp: Attempting to connect to zenhub
[root@zenoss log]# tail zenhub.log
2014-07-09 11:09:51,074 DEBUG zen.ZenHub: Registered 4 invalidation filters.
2014-07-09 11:09:51,113 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))
2014-07-09 11:09:51,113 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))
2014-07-09 11:09:51,113 DEBUG zen.ZenHub: Starting /bin/nice -n +5 /opt/zenoss/bin/zenhubworker run -C /opt/zenoss/var/zenhub/localhost_worker.conf
2014-07-09 11:09:51,119 DEBUG zen.ZenHub: Starting /bin/nice -n +5 /opt/zenoss/bin/zenhubworker run -C /opt/zenoss/var/zenhub/localhost_worker.conf
2014-07-09 11:09:51,124 DEBUG zen.Events: =============== incoming event ===============
2014-07-09 11:09:51,125 DEBUG zen.Events: Got a localhost zenhub heartbeat event (timeout 90 sec).
2014-07-09 11:09:51,128 DEBUG zen.zenoss.protocols.amqp: Connecting to RabbitMQ...
2014-07-09 11:09:51,128 DEBUG zen.protocols: Creating exchange: zenoss.heartbeats
2014-07-09 11:09:51,129 DEBUG zen.zenoss.protocols.amqp: Publishing with routing key zenoss.heartbeat.localhost to exchange zenoss.heartbeats

James Pulver

ZCA Member

CLASSE Computer Group

Cornell University



Subject: So this turned out to be
Author: [Not Specified]
Posted: 2014-07-09 13:20

So this turned out to be because /var filled up. Fixed that and everything worked.

James Pulver

ZCA Member

CLASSE Computer Group

Cornell University



< Previous
zenping not working correctly
  Next
Zenoss 4.2.0 sending empty reports
>