- observium - lists.observium.org

All ports down
by ira＠cylinder.tv 10 Feb '20

10 Feb '20

2 devices discovered No graphs work Config at pastebin.com/vTg8Ukep Thank you -- Sent from myMail for Android

4 5

Cleaning up Observium
by greggy862 . 06 Feb '20

06 Feb '20

Hello, I would like to cleanup observium, please see below that my largest directories are the logs (1.6 GB) and the rrd (17 GB). I tried cleaning up the logs by running ./housekeeping -sel BUT the size of the logs did not change - nonetheless, the devices with years of logs suddenly have days of logs (since I specified logs should be no older than 30 days). My concern is that I did the cleanup to reduce disk space, but immediately after I saw an increase in disk space, moreover, the space occupied in the log file directory did not change. Is it that observium housekeeping only targets space in the database, I ask because the query hanged for over 30 min doing nothing until I uses the -d (debug) flag and I noticed it was doing an sql query. How do I cleanup the logs directory? do I delete/truncate logs such as observium.log and access.log? What about the rrd directory, if I remove some of the rrds do I loose graphs (like record duration? LAB01:/opt/observium# du -h /opt/observium/ --max-depth=1 | sort -h 20K /opt/observium/templates 52K /opt/observium/probes 472K /opt/observium/attic 512K /opt/observium/scripts 1.3M /opt/observium/tests 1.8M /opt/observium/update 3.2M /opt/observium/libs 8.7M /opt/observium/includes 26M /opt/observium/html 630M /opt/observium/mibs 799M /opt/observium/.svn 2.3G /opt/observium/logs 17G /opt/observium/rrd 21G /opt/observium/ LAB01:/opt/observium# du -h /opt/observium/logs/* --max-depth=1 | sort -h 4.0K /opt/observium/logs/debug.log 12K /opt/observium/logs/cleanup.log 384K /opt/observium/logs/error_log 712K /opt/observium/logs/update-errors.log 1.3M /opt/observium/logs/housekeeping.log 20M /opt/observium/logs/db.log 707M /opt/observium/logs/access_log 1.6G /opt/observium/logs/observium.log Regards, Greg

1 0

Cisco 9300-24p in stack with 3 units not showing all info for stack member 2
by Daniel Johansson 06 Feb '20

06 Feb '20

Hi After setting up a new stack with 3 units of C9300-24p we only see the full inventory for switch 1 and switch 3 not switch 2. That means I can't see the fans or temp sensors for switch 2. Is this an observium parsing issue or an snmp issue in the switches? I attach a full picture of the inventory page. i also have a full snmpwalk dump from the switch if you need to have a look at it. Will send it outside of the list if needed. ---- Regards Daniel

3 3

unsubscribe
by Dose, Volker 04 Feb '20

04 Feb '20

Mit freundlichen Grüßen Volker Dose Volker Dose | IT-Infrastruktur ACO Severin Ahlmann GmbH & Co. KG Am Ahlmannkai | 24782 Büdelsdorf Tel.+49 4331 354-111 | Fax +49 4331 354-325 | Volker.Dose(a)aco.com<mailto:Volker.Dose@aco.com> www.aco.com<http://www.aco.com> [cid:image001.png@01D5DB77.BFA41390] Amtsgericht: Kiel, HRA 132 RD Komplementärin: Acoplast Kunststoff-Verarbeitung GmbH Amtsgericht: Kiel, HRB 131 RD USt-IdNr.: DE 135 372 264 Geschäftsführer: Hans-Julius Ahlmann, Iver Ahlmann, Søren W. Olsen, Thomas Bendixen [cid:image002.png@01D5DB77.BFA41390]<https://www.facebook.com/aco> [cid:image003.png@01D5DB77.BFA41390]<https://www.youtube.com/user/ACO> [cid:image004.png@01D5DB77.BFA41390]<https://www.linkedin.com/company/aco-group/> [cid:image005.png@01D5DB77.BFA41390]<https://www.instagram.com/aco_group> [cid:image006.png@01D5DB77.BFA41390]<https://www.pinterest.de/aco_group/> [cid:image007.png@01D5DB77.BFA41390]<https://twitter.com/aco_gruppe/>

1 0

LDAPS
by Quentin Beggs 04 Feb '20

04 Feb '20

Hey just wondering on the process for setting up LDAPS for authentication for Observium on Debian? We currently have LDAP working successfully but looking to move to LDAPS. I've changed the port and set starttls to true in the config file but I can't work out how/where to import the certificate? Quentin Beggs | Engineer 02 9970 2010 | 0420 361 760 Quentin.Beggs(a)netstrategy.net NetStrategy Pty Ltd | help(a)netstrategy.net Help Desk 1300-736-383 | netstrategy.net 165 Walker St, North Sydney NSW 2060

3 2

Feature Request - Interactive Graphs
by Justin Radke 04 Feb '20

04 Feb '20

Hello, I have been a user of Observium for quite some time and currently paid subscriber, I have always wanted to see interactive graphs to improve usability. What I am asking for specifically is the ability to: 1. Hover the mouse cursor over the graph and have it show pop-up boxes with info that show the current value for that vertex on the graph. 2. The ability to select a time window by clicking and dragging the cursor across the graph. This functionality is commonly seen on stock graphs such as finance.yahoo.com or finance.google.com where you can view values across the timeline and select time ranges by highlighting them on the graph with the mouse cursor. Is this a feature that can be added to Observium? Also, if this is not the appropriate method to issue feature requests please kindly direct me towards the proper method. Regards, -=JGR

8 9

Windows SNMP Timeout
by Luis Londoño 03 Feb '20

03 Feb '20

Hello, Is anyone else having any issues with SNMP timeouts on windows servers? I´ve checked the servers to make sure the port is open and it is listening, but whenever I either do the poller or I manually do the snmpwalk I get a timeout. Same thing if I run the snmpwalk from another server. I do get a ping response so I know they can communicate. I have 3 Windows 2012R2 servers that are having this issue, not sure if maybe it was a recent windows update. TIA

3 3

Re: [Observium] Supermicro: Voltage scale unreliabe
by Mike Stupalov 03 Feb '20

03 Feb '20

Ok, as I see in your output, all sensors with smHealthMonitorType equal to 1, everyone have smHealthMonitorReadingUnit equal to mV. And this mean our sensor definition still correct, not see reason for your changes. But I found 2 additional sensor classes (current type 7, unit mA) and (power type, unit mW). I will add it. smHealthMonitorType.22 = 1 smHealthMonitorType.23 = 1 smHealthMonitorType.24 = 1 smHealthMonitorType.25 = 1 smHealthMonitorType.26 = 1 smHealthMonitorType.27 = 1 smHealthMonitorType.28 = 1 smHealthMonitorType.29 = 1 smHealthMonitorType.30 = 1 smHealthMonitorType.31 = 1 smHealthMonitorType.32 = 1 smHealthMonitorType.33 = 1 .. smHealthMonitorType.42 = 1 smHealthMonitorType.43 = 1 .. smHealthMonitorType.52 = 1 smHealthMonitorType.53 = 1 smHealthMonitorReadingUnit.22 = "mV" smHealthMonitorReadingUnit.23 = "mV" smHealthMonitorReadingUnit.24 = "mV" smHealthMonitorReadingUnit.25 = "mV" smHealthMonitorReadingUnit.26 = "mV" smHealthMonitorReadingUnit.27 = "mV" smHealthMonitorReadingUnit.28 = "mV" smHealthMonitorReadingUnit.29 = "mV" smHealthMonitorReadingUnit.30 = "mV" smHealthMonitorReadingUnit.31 = "mV" smHealthMonitorReadingUnit.32 = "mV" smHealthMonitorReadingUnit.33 = "mV" .. smHealthMonitorReadingUnit.42 = "mV" smHealthMonitorReadingUnit.43 = "mV" .. smHealthMonitorReadingUnit.52 = "mV" smHealthMonitorReadingUnit.53 = "mV" Torstein Eide wrote on 03.02.2020 13:04: > Hi Mike > See attached file > > > man. 27. jan. 2020 kl. 19:21 skrev Mike Stupalov <mike(a)observium.org > <mailto:mike@observium.org>>: > > Hrm, > > please attach discovery debug for more understand, what your > device return in this MIB: > ./discovery.php -d -m sensors -h <device> > > Torstein Eide wrote on 27.01.2020 20:51: >> for voltage, the scale is in mV, (0.001), some times it would >> reset to 1. >> like this, for a 12V rail: >> image.png >> >> It is the fix "+ 'scale' => 0.001," that is >> important. >> since the "map_class" is more reliable then than the " 'mV' => >> 0.001,". >> >> man. 27. jan. 2020 kl. 18:33 skrev Mike Stupalov >> <mike(a)observium.org <mailto:mike@observium.org>>: >> >> Hi, >> >> please describe, what you mean as (voltage was unreliable)? >> >> as I see, you just added min (0) and max (250000), >> if your server return such values, we can exclude in same >> (single) definition. >> Both this values also impossible for fan speed and temperature. >> >> Torstein Eide via observium wrote on 24.01.2020 14:40: >>> Hi >>> >>> For me the scale read by the supermicro voltage was >>> unreliable, so i have change it to be 2 separately entries. >>> Index: includes/definitions/mibs/supermicro.inc.php >>> >>> =================================================================== >>> --- includes/definitions/mibs/supermicro.inc.php >>> (revision 10173) >>> +++ includes/definitions/mibs/supermicro.inc.php >>> (working copy) >>> @@ -29,6 +29,8 @@ >>> 'SUPERMICRO-HEALTH-MIB::smHealthMonitorName.1' => '/.+/' >>> ]; >>> >>> + >>> +// Tempeture and fanspeed >>> $config['mibs'][$mib]['sensor'][] = array( >>> 'table' => 'smHealthMonitorTable', >>> 'oid' => 'smHealthMonitorReading', >>> @@ -35,11 +37,12 @@ >>> 'oid_descr' => 'smHealthMonitorName', >>> 'descr_transform' => [ 'action' => 'ireplace', >>> 'from' => [ 'Temperature', 'Temp', 'Voltage', ' Fan >>> Speed', ' Speed' ], 'to' => '' ], >>> 'oid_class' => 'smHealthMonitorType', >>> - 'map_class' => [ 0 => 'fanspeed', 1 => >>> 'voltage', 2 => 'temperature' ], >>> + 'map_class' => [ 0 => 'fanspeed', 2 => >>> 'temperature' ], >>> // This table have unit oid smHealthMonitorDivisor, >>> but it always 0 >>> 'oid_scale' => 'smHealthMonitorReadingUnit', >>> 'map_scale' => [ 'C' => 1, 'mV' => 0.001, >>> 'RPM' => 1 ], >>> 'oid_num' => >>> '.1.3.6.1.4.1.10876.2.1.1.1.1.4', >>> + 'min' => 0, >>> 'limit_scale' => 'scale', // limits scale >>> same as main scale >>> 'oid_limit_high' => 'smHealthMonitorHighLimit', >>> 'oid_limit_low' => 'smHealthMonitorLowLimit', >>> @@ -47,6 +50,31 @@ >>> 'rename_rrd' => 'supermicro-%index%' >>> ); >>> >>> +// voltage >>> + >>> +$config['mibs'][$mib]['sensor'][] = array( >>> + 'table' => 'smHealthMonitorTable', >>> + 'oid' => 'smHealthMonitorReading', >>> + 'oid_descr' => 'smHealthMonitorName', >>> + 'descr_transform' => [ 'action' => 'ireplace', >>> 'from' => [ 'Temperature', 'Temp', 'Voltage', ' Fan >>> Speed', ' Speed' ], 'to' => '' ], >>> + 'oid_class' => 'smHealthMonitorType', >>> + 'map_class' => [ 1 => 'voltage' ], >>> + // This table have unit oid smHealthMonitorDivisor, >>> but it always 0 >>> + //'oid_scale' => 'smHealthMonitorReadingUnit', >>> + //'map_scale' => [ 'C' => 1, 'mV' => 0.001, >>> 'RPM' => 1 ], >>> + 'limit_scale' => 'scale', // limits scale >>> same as main scale >>> + 'scale' => 0.001, >>> + 'oid_num' => >>> '.1.3.6.1.4.1.10876.2.1.1.1.1.4', >>> + 'min' => 0, >>> + 'max' => 250000, >>> + 'oid_limit_high' => 'smHealthMonitorHighLimit', >>> + 'oid_limit_low' => 'smHealthMonitorLowLimit', >>> + 'test' => [ 'field' => >>> 'smHealthMonitorReadingUnit', 'operator' => 'notin', >>> 'value' => [ 'ThermalText', 'N/A' ] ], >>> + 'rename_rrd' => 'supermicro-%index%' >>> +); >>> >>> >>> This fix the problem i had with scale changing for voltage. >>> >>> -- >>> Torstein Eide >>> Torsteine(a)gmail.com <mailto:Torsteine@gmail.com> >>> >>> >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org <mailto:observium@observium.org> >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> >> -- >> Mike Stupalov >> Observium Limited, http://observium.org >> >> >> >> -- >> Torstein Eide >> Torsteine(a)gmail.com <mailto:Torsteine@gmail.com> > > -- > Mike Stupalov > Observium Limited, http://observium.org > > > > -- > Torstein Eide > Torsteine(a)gmail.com <mailto:Torsteine@gmail.com> -- Mike Stupalov Observium Limited, http://observium.org

1 0

Device need to be rediscovered
by Tomasz Karczewski 02 Feb '20

02 Feb '20

Hi, >From the last update i see many logs like "snmpEngineID changed: -> (probably the device was replaced). The device will be rediscovered" I rediscoverd manually all devices but i still see these logs. Tomasz Karczewski Administrator Sieci tkarczewski(a)man.olsztyn.pl http://www.man.olsztyn.pl http://www.uwm.edu.pl tel. (89) 523 45 55 fax. (89) 523 43 47 Ośrodek Eksploatacji i Zarządzania Miejską Siecią Komputerową OLMAN w Olsztynie Uniwersytet Warmińsko-Mazurski w Olsztynie

4 6

Areca arrays
by cody＠mail-server.cc 01 Feb '20

01 Feb '20

The Areca controller is supported but only very basic infos are availaible as Areca doesn't provide much via SNMP. But there is a areca-hw script that uses the cli tool get the hardware infos out of it: CLI> hw info The Hardware Monitor Information ===================================================== [Controller H/W Monitor] CPU Temperature : 64 C Controller Temp. : 38 C CPU Fan : 8437 RPM 12V : 12.220 V 5V : 5.053 V 3.3V : 3.360 V IO Voltage +1.8V : 1.824 V DDR3 +1.5V : 1.536 V CPU VCore +1.0V : 1.040 V Analog +1.0V : 1.024 V DDR3 +0.75V : 0.752 V Battery Status : Not Installed [Enclosure#1 : SAS RAID Adapter V1.0] ===================================================== GuiErrMsg<0x00>: Success. Would it be possible to extend the areca-hw script to add volume and disk info to check if the volume is in Normal or Degraded state and if possible which disk is gone? CLI> vsf info # Name Raid Name Level Capacity Ch/Id/Lun State =============================================================================== 1 ARC-1882-VOL#000 Raid Set # 000 Raid1+0 480.1GB 00/00/00 Normal 2 ARC-1882-VOL#002 Raid Set # 002 Raid1+0 600.1GB 00/00/01 Normal 3 ARC-1882-VOL#003 Raid Set # 003 Raid1+0 2000.4GB 00/00/02 Normal =============================================================================== GuiErrMsg<0x00>: Success. CLI> disk info # Enc# Slot# ModelName Capacity Usage =============================================================================== 1 01 Slot#1 SAMSUNG MZ7KM480HAHP-0E005(SED 480.1GB Raid Set # 000 2 01 Slot#2 SAMSUNG MZ7KM480HAHP-0E005(SED 480.1GB Raid Set # 000 3 01 Slot#3 N.A. 0.0GB N.A. 4 01 Slot#4 N.A. 0.0GB N.A. 5 01 Slot#5 WDC WD6000HLHX-01JJPV0 600.1GB Raid Set # 002 6 01 Slot#6 WDC WD6000HLHX-01JJPV0 600.1GB Raid Set # 002 7 01 Slot#7 HGST HUS724020ALE640 2000.4GB Raid Set # 003 8 01 Slot#8 HGST HUS724020ALE640 2000.4GB Raid Set # 003 =============================================================================== GuiErrMsg<0x00>: Success. Thanks, Cody

1 0