- observium - lists.observium.org

New Community Edition
by Adam Armstrong 24 Nov '14

24 Nov '14

Hi All, We've released a new Observium Community Edition, version 0.14.11, based on SVN revision 6000. There've been over 770 new commits since the previous release. http://www.observium.org/observium-community-0.14.11.tar.gz http://www.observium.org/wiki/Upgrading#Upgrade_to_latest_Major_release http://www.observium.org/wiki/Changelog (will be updated later!) adam.

17 31

Observium Location Naming
by Gary Tang 24 Nov '14

24 Nov '14

Is there some kind of convention as to how to set the sysLocation snmpd parameters? I am currently having some trouble finding the right naming for OVH BHS. So far none of the following work. OVH, Montregie, Quebec OVH, Beauharnois, Quebec OVH, Beauharnois, Montregie OVH, Beauharnois-Salaberry, Montregie -- Gary Tang Sent with Airmail

4 3

Paid support
by Gavin Henry 24 Nov '14

24 Nov '14

Hi all, I can see some of the support options on the main website, but not way to purchase or get in touch? -- Kind Regards, Gavin Henry. http://www.surevoip.co.uk

7 8

Multiple SNMP Queries
by Lane Eckley 23 Nov '14

23 Nov '14

Hi Guys, On a limited number of CentOS & Ubuntu machines we are monitoring with Observium we are seeing dozens of SNMP queries from Observium in a very short window (10-20 seconds). Snip of the logs from /var/logs/messages Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:55776->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] We are trying to understand why Observium would be sending so many queries back to back as well as why we are seeing this on some machines, but not others. Thanks! -Lane

3 2

hddtemp on CE 0.14.4.5
by deeepdish 23 Nov '14

23 Nov '14

Hello. Great product. Looking forward to evaluating the subscription version after I get a minimum base operational using the CE edition. I have an issue around viewing HDD TEMP graphs driven by data extracted from the UNIX agent and hddtemp script. I can confirm output when auditing output of: telnet (hostname) 36602 or ./poller.php -h (hostname) -d I can also confirm temp. sensor driven graphs do come up for other hosts when using SNMP lmsensors, however not for unix-agent / hddtemp data sources. Can someone point me in the right direction? Thank you.

3 2

Updated changelog!
by Adam Armstrong 22 Nov '14

22 Nov '14

The abridged changelog is now up to date with October and November to date! http://www.observium.org/wiki/Changelog

1 0

unsubscribe
by David Ford [NTLWORLD] 21 Nov '14

21 Nov '14

-- Regards, David Ford Your Old Books & Maps [1] -- Regards, David Ford Your Old Books & Maps [2] Links: ------ [1] http://youroldbooksandmaps.co.uk/?utm_source=TurboSMTP&utm_medium=TurboSMTP… [2] http://youroldbooksandmaps.co.uk/?utm_source=TurboSMTP&utm_medium=TurboSMTP…

2 1

Re: [Observium] hddtemp on CE 0.14.4.5
by deeepdish 21 Nov '14

21 Nov '14

My apologies…. Not using hddtemp script. Using the temperature script (that uses hddtemp).. sn = serial number. Using ZFS on Linux by-vdev definition to map /dev/hd? -> /dev/disk/by-vdev/(sn - serial number) My temperature script below as on monitored host. #!/bin/bash echo "<<<temperature>>>" echo “(sn 1):" `hddtemp /dev/disk/by-vdev/(sn 1) -n` echo “(sn 2):" `hddtemp /dev/disk/by-vdev/(sn 2) -n` echo “(sn 3):" `hddtemp /dev/disk/by-vdev/(sn 3) -n` echo “(sn 4):" `hddtemp /dev/disk/by-vdev/(sn 4) -n` echo “(sn 5):" `hddtemp /dev/disk/by-vdev/(sn 5) -n` ------------------------------ Message: 5 Date: Fri, 21 Nov 2014 10:27:27 -0600 From: "Ron Marosko" <ron(a)rjr-services.com <mailto:ron@rjr-services.com>> To: "'Observium Network Observation System'" <observium(a)observium.org <mailto:observium@observium.org>> Subject: Re: [Observium] hddtemp on CE 0.14.4.5 Message-ID: <001b01d005a8$0aa08140$1fe183c0$(a)rjr-services.com <mailto:001b01d005a8$0aa08140$1fe183c0$@rjr-services.com>> Content-Type: text/plain; charset="us-ascii" Just having a look at the hddtemp agent script. # hddtemp sensor readings # needs hddtemp daemon listening on (at least) localhost # requires netcat to be installed and in the path Have you satisfied those requirements? From: observium [mailto:observium-bounces@observium.org <mailto:observium-bounces@observium.org>] On Behalf Of deeepdish Sent: Friday, November 21, 2014 9:36 AM To: observium(a)observium.org <mailto:observium@observium.org> Subject: [Observium] hddtemp on CE 0.14.4.5 Hello. Great product. Looking forward to evaluating the subscription version after I get a minimum base operational using the CE edition. I have an issue around viewing HDD TEMP graphs driven by data extracted from the UNIX agent and hddtemp script. I can confirm output when auditing output of: telnet (hostname) 36602 or ./poller.php -h (hostname) -d I can also confirm temp. sensor driven graphs do come up for other hosts when using SNMP lmsensors, however not for unix-agent / hddtemp data sources. Can someone point me in the right direction? Thank you.

1 0

hddtemp on CE 0.14.4.5
by deeepdish 21 Nov '14

21 Nov '14

Hello. Great product. Looking forward to evaluating the subscription version after I get a minimum base operational using the CE edition. I have an issue around viewing HDD TEMP graphs driven by data extracted from the UNIX agent and hddtemp script. I can confirm output when auditing output of: telnet (hostname) 36602 or ./poller.php -h (hostname) -d I can also confirm temp. sensor driven graphs do come up for other hosts when using SNMP lmsensors, however not for unix-agent / hddtemp data sources. Can someone point me in the right direction? Thank you.

1 0

r6001 backward compatibility
by Tom Laermans 21 Nov '14

21 Nov '14

Dear all, Revision 6001 cleans up a bunch of old code paths that should not have been used in recent days. If you are upgrading from a revision before r5000, it's probably best to upgrade to r6000 (svn up -r6000) first, run a full discovery and poll cycle, then upgrade to latest trunk. We've removed RRD renaming code for files which should since long have been renamed, and variables that should not exist anymore in your config. Variables to double check: $config['email_*'] should be renamed to $config['email'][*] instead. Tom

3 4