You could disable etherlike polling in Observium as a [temporary?] workaround. (you'll lose some stats, but you'll also lose the logs ;)

Tom

On 01/03/2014 00:17, Robert Williams wrote:

Hi,

 

Thanks, sorry I didn’t realise that was the actual name of it, duh – from that I’ve now found out it’s actually triggered by simply trying to walk  .1.3.6.1.2.1.10.7.2

 

Whilst returning “no object at this OID” it then generates a daemon error level event and sends a syslog alert for every single interface - which seems a bit extreme to me.

 

So looking like it’s a ‘feature’ of whatever the newer kernel in 6.6R1 is, so I’ll take it up with the Vyatta peeps now.

 

Cheers!

 

Robert Williams
Custodian Data Centre
Email: Robert@CustodianDC.com
http://www.CustodianDC.com

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans
Sent: 28 February 2014 22:44
To: Observium Network Observation System
Subject: Re: [Observium] Vyatta snmpd errors in ports module

 

Hi,

The log message says exactly what Observium is accessing... dot3StatsTable.

Tom

On 28/02/2014 21:53, Robert Williams wrote:

Hi,

 

On the latest version of Vyatta (6.6 R1) we are getting these errors for every physical port on every poller run:

 

snmpd[3872]: access:dot3StatsTable,interface_ioctl_dot3Stats_get, cannot get stats information for interface |eth5|

snmpd[3872]: access:dot3StatsTable,interface_ioctl_dot3Stats_get, cannot get stats information for interface |eth0|

snmpd[3872]: access:dot3StatsTable,interface_ioctl_dot3Stats_get, cannot get stats information for interface |eth3|

snmpd[3872]: access:dot3StatsTable,interface_ioctl_dot3Stats_get, cannot get stats information for interface |eth2|

snmpd[3872]: access:dot3StatsTable,interface_ioctl_dot3Stats_get, cannot get stats information for interface |eth4|

snmpd[3872]: access:dot3StatsTable,interface_ioctl_dot3Stats_get, cannot get stats information for interface |eth1|

 

However everything on the graphs looks fine. I’ve tracked it down to the ports module, which when run by itself causes the errors on the Vyatta box:

(The stats are low because it’s not actually in production and only eth4 and eth4.497 are link-up)

 

router.name 311 vyatta (unix)

Uptime: 4h 23m 4s

Module time: 0.0684s

 

Hardware:  Version:  Features: VC6.6R1 Serial:  Asset:

Module time: 0.0132s

Caching Oids: ifEntry ifXEntry dot3StatsDuplexStatus

Port Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller(2) replacing with 64-bit...VLAN == bps(0bps/0bps)bytes(0B/0B)pkts(0pps/0pps)

Checking alerts

 

Port Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller(3) replacing with 64-bit...VLAN == bps(0bps/0bps)bytes(0B/0B)pkts(0pps/0pps)

Checking alerts

 

Port Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller(4) replacing with 64-bit...VLAN == bps(0bps/0bps)bytes(0B/0B)pkts(0pps/0pps)

Checking alerts

 

Port Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller(5) replacing with 64-bit...VLAN == bps(0bps/0bps)bytes(0B/0B)pkts(0pps/0pps)

Checking alerts

 

Port Intel Corporation 82574L Gigabit Network Connection(6) replacing with 64-bit...VLAN == bps(20.6kbps/13.8kbps)bytes(58kB/38.9kB)pkts(12.9pps/13.0pps)

Checking alerts

 

Port Intel Corporation 82574L Gigabit Network Connection(7) replacing with 64-bit...VLAN == bps(0bps/0bps)bytes(0B/0B)pkts(0pps/0pps)

Checking alerts

 

Port eth4.497(8) replacing with 64-bit...VLAN == bps(18.3kbps/13.0kbps)bytes(51.5kB/36.5kB)pkts(12.9pps/13.0pps)

Checking alerts

 

Module time: 0.3932s

Polled in 0.5376 seconds

 

Now this doesn’t occur when polling Vyatta 6.5 R1 so I appreciate it’s probably something which has changed in the Vyatta (or it is now logging something which previously it has ignored). However, to stand a hope of getting it sorted I wondered if anyone could suggest what part of the ‘ports’ module could possibly cause an error like this in the snmpd of the Vyatta? Then I can try to take it up on the Vyatta forums, but at the moment I can’t even explain which I’m trying to poll when the error occurs because I don’t know what steps in the ports module are likely to cause this.

 

Any suggestions / pointers welcome!

Robert Williams
Custodian Data Centre
Email: Robert@CustodianDC.com
http://www.CustodianDC.com




_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

 



_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium