- observium - lists.observium.org

match port_id with rrd graphs
by Zhenhui Liang 30 Mar '15

30 Mar '15

Hi, I would like to do some rrdtool fetch against the raw rrd files observium generated to get some reports. But I couldn’t figure out how to match the portid or device_id from observium tables to get the correct path to match to the rrd files. Rrd files location seemed to be at ~observium/rrd/devicenames. But the rrd file name like port-123.rrd, 123 seems not to be the port_id in the ports table. Rather it’s device specific. Thank you very much for your help. —Zhenhui

4 5

Discovery on Nexus 3K removes all interfaces
by Markus Viitamäki 30 Mar '15

30 Mar '15

I am running 0.15.3.6350 and have noticed that some time ago all interfaces on my nexus 3k's gets marked deleted every time discovery runs. However the interfaces are not deleted.. :/ I have done debugging on the a discovery and the only problems I can find are these (I am not sure these are related at all): http://pastie.org/private/lmqwcfqdp2ujo2nx65pwew // Markus (suom1)

2 2

update errors database structure
by Patrick Marquetecken 29 Mar '15

29 Mar '15

Hi, It seems that I have some problems with my database structure Perhaps related to my alerts & evenlog problems. [2015/01/18 15:05:14 +0100] update.php(2459): ====== Schema update 137 -> 138 ============== [2015/01/18 15:05:14 +0100] update.php(2459): Query: ALTER TABLE `sensors` ADD `entPhysicalIndex_measured` varchar(16) COLLATE utf8_unicode_ci DEFAULT NULL AFTER `sensor_custom_limit`; [2015/01/18 15:05:14 +0100] update.php(2459): Error: Duplicate column name 'entPhysicalIndex_measured' [2015/01/18 15:05:14 +0100] update.php(2459): Query: ALTER TABLE `sensors` ADD `measured_class` VARCHAR( 32 ) NULL DEFAULT NULL AFTER `entPhysicalIndex_measured`; [2015/01/18 15:05:14 +0100] update.php(2459): Error: Duplicate column name 'measured_class' [2015/01/18 15:05:14 +0100] update.php(2459): Query: ALTER TABLE `sensors` ADD `measured_entity` VARCHAR( 32 ) NULL DEFAULT NULL AFTER `measured_class`; [2015/01/18 15:05:14 +0100] update.php(2459): Error: Duplicate column name 'measured_entity' [2015/03/23 14:23:56 +0100] discovery.php(31115): ====== Schema update 183 -> 184 ============== [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: ALTER TABLE `eventlog` CHANGE `reference` `entity_id` INT( 64 ) NULL DEFAULT NULL; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1366) Incorrect integer value: 'NULL' for column 'entity_id' at row 1 [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: ALTER TABLE `eventlog` ADD `severity` TINYINT NOT NULL DEFAULT '6' AFTER `entity_id`; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'entity_id' in 'eventlog' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 4 WHERE `message` REGEXP '(above|under) threshold'; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 5 WHERE `message` REGEXP ' [.(.]by (user|cron|console)'; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 3 WHERE `message` LIKE 'Device status changed to%'; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 4 WHERE `message` LIKE '%probably the device was replaced%'; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 4 WHERE `message` LIKE 'OS changed%'; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 4 WHERE `message` LIKE 'Device rebooted%'; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list' [2015/03/23 14:23:56 +0100] discovery.php(31115): Query: UPDATE `eventlog` SET `severity` = 4 WHERE `entity_type` IN ('bgp_peer', 'sensor') AND `message` REGEXP ' (Up|Down|Alarm): '; [2015/03/23 14:23:56 +0100] discovery.php(31115): Error: (1054) Unknown column 'severity' in 'field list'

2 5

snmp crash on nexus 7k when polling certain OID
by Steve Costaras 29 Mar '15

29 Mar '15

I'm running observium CE 0.14.11.6000. We just ran into an interesting problem on a Nexus 7K running 6.2(12) code. When observium polls the device, the snmp process crashes and reloads (this happens with every 5 minute poll). Managed to track it down to a specific OID that's causing it: 1.3.6.1.4.1.9.9.91.1.1.1.1.4.22809 It takes less than a second to reload the snmp process on the 7K; we're engaging cisco to see about a fix, but in the interim besides disabling the device, is there a specific way to block/not poll this particular OID? Older nexus code appears to not have this problem as. Steve

2 1

New user - I apologize in advance if I am asking stupid questions
by Rich Elwell 28 Mar '15

28 Mar '15

Greetings, I've recently installed observium and find that it is a great tool. Kudos for developing something so useful and easy to use. I do have a couple of questions. I desire to set the device_id for some of the devices to a specific value. This is not supported in the interface. It looks like I *should* be able to modify the code to allow me to do this, but before I do I wanted to check and see if there is already a way for me to accomplish this without having to modify the code. I also desire to be able to add devices programatically via an API call from an external system. I looked over the existing simple API (not extensively) but it didn't seem like that was possible. So basically I want to be able to do something like: http://myserver/api.php?mydetails&including&device_id and have it add the device while specifying the device_id. Is that possible? If not, I'm probably going to build it. Thanks, Rich -- Rich Elwell, MS, CISSP, GCIA, CCNA, CCNA Security /dev/null security ⋅ network *nix administration

3 5

ISSUES/BUg with regards to collect_table Implementation - Suggested Code Changes
by Mark Gibbons 28 Mar '15

28 Mar '15

Hi (especially adam - can you take a read please) Background I have been working on integrating support for Ubiquiti wireless products so that wireless stats can be shown on the "wireless" graph page for these devices. I created routines to process the mibs in /include/polling/graphs using the original loop method to parse the mib to generate and populate the RRD's and everything is working absolutely fine. I will of course submit this work for inclusion once tested/verified fully. However, i read the README (you see people do read README's!!!!!!!!!!): "Please make sure you use the *new* format of graphing poller. Generate a $graph_defs array to be used in collect_table." And i thought I would have a go at the $table_def method. So I defined the MIB as per $tabledef and come across issues with multi indexed oids. In this instance from a MIB walk we have two oids as follows: ubntRadioRssi.1.1 ubntRadioRssi.1.2 So i put the following in table_def: 'ubntRadioRssi.1' => array('index' => '1', 'descr' => 'RSSI Chain 0', 'ds_type' => 'GAUGE', 'ds_name' => 'RadioRssi_0'), 'ubntRadioRssi.1' => array('index' => '2', 'descr' => 'RSSI Chain 1', 'ds_type' => 'GAUGE', 'ds_name' => 'RadioRssi_1'), But, of course, (knowing what i know now) this does not work because the array index is the same and you only get the last entry. So i thought try with a blank index specifying the full oid: 'ubntRadioRssi.1.1' => array('index' => '', 'descr' => 'RSSI Chain 0', 'ds_type' => 'GAUGE', 'ds_name' => 'RadioRssi_0'), 'ubntRadioRssi.1.2' => array('index' => '', 'descr' => 'RSSI Chain 1', 'ds_type' => 'GAUGE', 'ds_name' => 'RadioRssi_1'), But this didn't work so I investgated. The issues surround the handling of the separation of oid and index in both collect table AND snmp_get_multi. Let me Deal with snmp_get_multi first. Snmp_get multi expects an array of full oid's - great. However it spits back an array of oids and index separated. Because you use explode to breakup the oid it will only ever return the first index after the first "." rather than the full index after the first "." I am talking about this code at approx Line 464 in /includes/snmp.inc.php foreach (explode("\n", $data) as $entry) { list($oid,$value) = explode("=", $entry, 2); $oid = trim($oid); $value = trim($value); list($oid, $index) = explode(".", $oid); if (!strstr($value, "at this OID") && isset($oid) && isset($index)) { $array[$index][$oid] = $value; } } This can be corrected if you change it to the following code. In this case the base oid is returned with the FULL index in the index. I can't see that this could/would break other stuff but your experience would know better!! : foreach (explode("\n", $data) as $entry) { list($oid,$value) = explode("=", $entry, 2); $oid = trim($oid); $value = trim($value); $dotpos = strpos($oid, '.'); if ($dotpos != FALSE) { $index = substr($oid, $dotpos+1); $oid = substr($oid, 0, $dotpos); } //list($oid, $index) = explode(".", $oid); if (!strstr($value, "at this OID") && isset($oid) && isset($index)) { $array[$index][$oid] = $value; } } So the next issue is index handling within collect_table and the temporary index of oids created to generate rrdupdate. Current code is at approx 898 in /includes/polling/functions.inc.php: $oids[] = $oid.'.'.$entry['index']; $oids_index[] = array('index' => $entry['index'], 'oid' => $oid); Again if this is changed to the following so that oid and index is re-split like the return from snmp_get_multi we have a working solution where you can specify the full oid as an index for the oid array in table_def with an oid index of '' (blank): if ($entry['index'] != '') { $fulloid = $oid.'.'.$entry['index']; } else { $fulloid = $oid; } $oids[] = $fulloid; $dotpos = strpos($fulloid, '.'); if ($dotpos != FALSE) { $splitindex = substr($fulloid, $dotpos+1); $splitoid = substr($fulloid, 0, $dotpos); } //$oids_index[] = array('index' => $entry['index'], 'oid' => $oid); $oids_index[] = array('index' => $splitindex, 'oid' => $splitoid); So this is a possible solution to the multiple index problem on an oid. By specifying the full oid with blank index. What do you think? Seems like a Win/Win to me but my experience of Observium php code and structure is < 1 week. At least this solution means we can use the table_def method for us but it would mean a lot of maintenance with svn updates. Hope this solution is of possible interest for inclusion. KR's Mark

1 1

FortiGate support
by Thomas Raabo - Zitcom A/S 27 Mar '15

27 Mar '15

At some point we had FortiGate support for session graphing and so on. Now its gone. Does somebody know why? Thomas

2 2

How best to engage the Professional Services team?
by Arthur Bommele (DataByte) 27 Mar '15

27 Mar '15

Dear concerned, How best to engage the Professional Services team? Specifically, regarding Feature Development. Kind regards, Arthur B.

1 0

Help analysis
by Eliezer De Sousa Oliveira 27 Mar '15

27 Mar '15

hello everyone! how to tell the host that causes more traffic on my network? the Community observium, have an option to do this analysis? ass eliezer

2 3

Cronjobs in polling the devices
by Jerico M. Rubion 26 Mar '15

26 Mar '15

Hi there, I would like to inquire about the desired minimum cron jobs that are accepted in observium. I only have a Quad Core Intel(R) Xeon(R) CPU E5405 @ 2.00GHz CPU resources available currently managing 69 HOSTS/Devices. My current setting in /etc/cron.d/observium is */10 * * * * root /opt/observium/poller-wrapper.py 4 >> /dev/null 2>&1 */10 * * * * root /opt/observium/poller.php -h all >> /dev/null 2>&1 Can I comment out the 2nd line -> */10 * * * * root /opt/observium/poller.php -h all >> /dev/null 2>&1 ?? Best Regards, Jerico M. Rubion | 77GSI IT Services Group SEVEN SEVEN GLOBAL SERVICES INC. | 27th Floor, Orient Square Bldg., F. Ortigas Jr. Ortigas Center, Pasig City, Philippines 1605 Office: +632.915.7747 ext. 1911 | Mobile: +63.9175382740 | Duo: +632.9667501 The Information contained and all attachments to this email are for the named recipient(s) only. It contains legally privileged and confidential information intended solely for the use of the addressee. The addressee undertakes to use such information consistent with its privileged and confidential character, and by the receipt thereof appreciates that any use contrary thereto will subject him to sanctions provided for by law. If the reader of this message is not the intended recipient, please be notified that any reading, dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this transmittal in error, please notify the sender immediately.

2 1