- observium - lists.observium.org

Re: [Observium] Check IPsec tunnel status on Juniper SRX firewalls
by Youssef BENGELLOUN - ZAHR 07 Nov '16

07 Nov '16

1 1

Force disable 'Neighbours discovery: LLDP-MIB', ['xdp'] = FLASE; not working
by Andy Lemin 06 Nov '16

06 Nov '16

Hi, How can we _Force_ the disablement of discovering hosts via LLDP/XDP? Normally when running poller.php, with '$config['autodiscovery']['xdp'] = FLASE;' set in config.php, everything is fine. However when running '/opt/observium/discovery.php', it finds a switch, and we have LLDP enabled on our servers and switches for other processes related to the management of servers. However this means that Observium takes over an hour to discover a single Virtual Cassis which has 192 ports, with over 100 active servers (all showing up in the LLDP on the switch). Obviously this is a waste of time, and unnecessarily stressful for the servers being scanned and the Observium server. Why is discovery.php not honouring '$config['autodiscovery']['xdp'] = FLASE;' as set in config.php? Cheers, Andy.

3 3

Device Properties - Ports - Toggle Not Working
by Iwanski, Ed 06 Nov '16

06 Nov '16

I tried looking for mailing list archives but didn't find them online, please let me know where to look if I am mistaken. We are on Observium Professional 0.16.10.8181, stable svn update rev 8201 shown so looks up to date. We are having problems using the toggle or disable for an entire column on the device properties port page. I thought it might be a browser issue but I have tried Chrome, Firefox and IE from different computers with no luck. Currently the button just behaves like the save button and submits the form instead of changing the status on the existing page. Any thoughts on what else I could check would be appreciated.

1 0

SSH versus Ping for device_status
by Dano, Leo 03 Nov '16

03 Nov '16

Hi all, I remember back that ssh wasn't supported, in the later versions has this been implemented? We want Observium to notify is a node loses it's ssh capabilities, versus just icmp Thanks, ----------------------- Leo Dano

1 0

Device Down false positive
by Sebastian Klute 03 Nov '16

03 Nov '16

Hi Tom, well it cannot really be that the device is marked as down by alert. Test conditions are as follows: device_status_type ping device_status equals 0 If I understand it correctly, even if snmp is not reachable the device should NOT be marked as down, because it is pingable. Therefore I do not understand why it is still marked as down. Message: 5 Date: Wed, 2 Nov 2016 20:36:19 +0100 From: Tom Laermans <tom.laermans(a)powersource.cx> To: Observium Network Observation System <observium(a)observium.org> Subject: Re: [Observium] Device Down False positive and snmpget Message-ID: <eff1c872-a32b-fe5f-ecb5-eafe35712ff4(a)powersource.cx> Content-Type: text/plain; charset="utf-8"; Format="flowed" Sebastian, The device was likely down due to ping, first... then, as it became pingable but not snmp-able, there was no change logged in device status (down = down). As to why snmpget is telling you 2 is > 128, I'm not sure... Tom On 02/11/2016 20:05, Sebastian Klute wrote: > Hello folks, > > today I got kinda strange problem. I got a Server up and running fine > but it is still shown as device down. "Device status changed to Down > (ping)" > After some debugging and digging into the workflow of polling and > checking egc. I tried to redo the different checks that could lead to > a device down. > First of all: Is it pingable ? > > root@om:/tmp# /usr/bin/fping -t1000 -t 500 -c 20 -q 84.200.41.226 > 84.2xx.xxx.xxx : xmt/rcv/%loss = 20/20/0%, min/avg/max = > 0.20/0.30/0.43 > > seems good to me - no idea why it should be down by ping. > Is the hostname resolvable? Yes it is. Standart ping with hostname is > working fine. > > So I'll dig further into debug logs and found this > > CMD[/usr/bin/snmpget -v2c -c *** -Pu -OQUst -m SNMPv2-MIB -M > /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp > 'udp':'hostname.example':'161' sysObjectID.0 sysUpTime.0] > > CMD EXITCODE[1] > CMD RUNTIME[6.0283s] > STDOUT[ > > ] > STDERR[ > Timeout: No Response from udp:hostname.example:161. > ] > SNMP STATUS[FALSE] > > I wondered why and did it manualy. > The error is as followed: > > Too many object identifiers specified. Only 128 allowed in one > request. > > > The question is now, what can I do to solve this issue? What about the > false positive device down by ping alert? > > > Additional Info: > > > $data - /opt/observium/poller.php:170 > /opt/observium/includes/alerts.inc.php:61 > ========================================= > array( > [device_status] => string(1) "0" > [device_status_type] => string(4) "snmp" > [device_ping] => string(4) "7.34" > [device_snmp] => int(0) > ) > > Thanks for the help and best regards > Sebastian Klute > > -- > Accelerated IT Services GmbH > Kruppstraße 105 - 60388 Frankfurt - Germany > sk(a)accelerated.de -http://www.accelerated.de/ > Phone: +49 69 - 900 180 41 - Fax: +49 69 - 900 180 90 > > HRB: 60665 - Amtsgericht Ludwigshafen - VatID: DE253684415 > Managing Directors: Nicolaj Kamensek & Ole Krieger > > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium -- Accelerated IT Services GmbH Kruppstraße 105 - 60388 Frankfurt - Germany sk(a)accelerated.de - http://www.accelerated.de/ Phone: +49 69 - 900 180 41 - Fax: +49 69 - 900 180 90 HRB: 60665 - Amtsgericht Ludwigshafen - VatID: DE253684415 Managing Directors: Nicolaj Kamensek & Ole Krieger

2 1

Squash the Hamster!
by Marc Elvery 03 Nov '16

03 Nov '16

No, let's not stand on the hamster, put the PNG could be a lot smaller. Using observium on a site with a slow line, during the login, the hamster takes longer to load than needed. When I throw the PNG into https://tinypng.com/ It shrinks from 359KB -> 67KB. Seems worthwile. Maybe some other PNG's can be shrunken aswell? Greetings, Marc

1 0

Device Down False positive and snmpget
by Sebastian Klute 02 Nov '16

02 Nov '16

Hello folks, today I got kinda strange problem. I got a Server up and running fine but it is still shown as device down. "Device status changed to Down (ping)" After some debugging and digging into the workflow of polling and checking egc. I tried to redo the different checks that could lead to a device down. First of all: Is it pingable ? root@om:/tmp# /usr/bin/fping -t1000 -t 500 -c 20 -q 84.200.41.226 84.2xx.xxx.xxx : xmt/rcv/%loss = 20/20/0%, min/avg/max = 0.20/0.30/0.43 seems good to me - no idea why it should be down by ping. Is the hostname resolvable? Yes it is. Standart ping with hostname is working fine. So I'll dig further into debug logs and found this CMD[/usr/bin/snmpget -v2c -c *** -Pu -OQUst -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'hostname.example':'161' sysObjectID.0 sysUpTime.0] CMD EXITCODE[1] CMD RUNTIME[6.0283s] STDOUT[ ] STDERR[ Timeout: No Response from udp:hostname.example:161. ] SNMP STATUS[FALSE] I wondered why and did it manualy. The error is as followed: Too many object identifiers specified. Only 128 allowed in one request. The question is now, what can I do to solve this issue? What about the false positive device down by ping alert? Additional Info: > $data - /opt/observium/poller.php:170 /opt/observium/includes/alerts.inc.php:61 ========================================= array( [device_status] => string(1) "0" [device_status_type] => string(4) "snmp" [device_ping] => string(4) "7.34" [device_snmp] => int(0) ) Thanks for the help and best regards Sebastian Klute -- Accelerated IT Services GmbH Kruppstraße 105 - 60388 Frankfurt - Germany sk(a)accelerated.de - http://www.accelerated.de/ Phone: +49 69 - 900 180 41 - Fax: +49 69 - 900 180 90 HRB: 60665 - Amtsgericht Ludwigshafen - VatID: DE253684415 Managing Directors: Nicolaj Kamensek & Ole Krieger

3 3

Call to undefined function mb_strtolower()
by Simon Smith 02 Nov '16

02 Nov '16

Hi All not sure if its me or my setup setup new server, Ubuntu 16.04, 2 core, 4gb ram, 40gb hdd, LXC container I’m getting the following error when I’m running the poller.php PHP Fatal error: Uncaught Error: Call to undefined function mb_strtolower() in /opt/observium/libs/ref.inc.php:968 Stack trace: #0 /opt/observium/libs/ref.inc.php(993): ref::getBacktrace() #1 /opt/observium/libs/ref.inc.php(81): ref::getInputExpressions(Array) #2 /opt/observium/includes/common.inc.php(706): rt(Array) #3 /opt/observium/includes/polling/system.inc.php(213): print_vars(Array) #4 /opt/observium/includes/polling/functions.inc.php(693): include('/opt/observium/...') #5 /opt/observium/poller.php(170): poll_device(Array, Array) #6 {main} thrown in /opt/observium/libs/ref.inc.php on line 968 Fatal error: Uncaught Error: Call to undefined function mb_strtolower() in /opt/observium/libs/ref.inc.php:968 Stack trace: #0 /opt/observium/libs/ref.inc.php(993): ref::getBacktrace() #1 /opt/observium/libs/ref.inc.php(81): ref::getInputExpressions(Array) #2 /opt/observium/includes/common.inc.php(706): rt(Array) #3 /opt/observium/includes/polling/system.inc.php(213): print_vars(Array) #4 /opt/observium/includes/polling/functions.inc.php(693): include('/opt/observium/...') #5 /opt/observium/poller.php(170): poll_device(Array, Array) #6 {main} thrown in /opt/observium/libs/ref.inc.php on line 968 anybody seen these errors before? regards Simon

2 2

Systems no longer show up
by Macklin, Jason 01 Nov '16

01 Nov '16

Good day everyone! We are no longer seeing anything via the webui. I suspect it is due to a loss of network connectivity over the weekend. Seeing the following in the db.log now: Failed dbQuery (#2006 - MySQL server has gone away) Initial investigation seems to suggest that the client has become disconnected from the mariadb server (they are the same system) and so I'm wondering if there is an easy recovery method. Restarting services has not worked and the server has been rebooted. Still no change. Any help is greatly appreciated! Cheers, Jason -- *Jason Macklin* Lead Consultant - Sequencing Solution Center R&D Roche Molecular Systems | 4300 Hacienda Drive | Pleasanton, CA 94588 | USA T: +1 925 730 8458 | M: +1 925 353 7409 | E: *jason.macklin(a)roche.com <jason.macklin(a)roche.com>*

2 4

unsubscribe
by Justin Smith 01 Nov '16

01 Nov '16

1 0