- observium - lists.observium.org

get Inventory via API
by Henry Möller 05 Nov '18

05 Nov '18

Hello, We trying to get information's about the Inventory from Observium. Mainly we trying to get the Serial Number and the Model Number from observium. This works well for a single switch. But it is not working if we have a stacked switch. In this case we get only the serial number of the stack-master. Is there a way to get all the information's that are listed on the inventory via API? [cid:image001.jpg@01D474E6.70D7D4C0] Best Regards Henry Möller ------------------------------------------------------------ Phone: +49 30 520 041 698 Fax: +49 30 520 041 699 Mail: Henry.Moeller(a)pinguin.ag ------------------------------------------------------------ Phone: +49.30.30 36 63 366 Fax: +49.30.30 36 63 367 E-Mail: info(a)pinguin.ag<mailto:info@pinguin.ag> www.pinguin.ag<http://www.pinguin.ag> ------------------------------------------------------------ [cid:pinguin.ag_f1f2f94b-4088-4a1c-afba-e73816a444e1.png] Pinguin AG Hauptstraße 8 | 10827 Berlin | Germany USt-ID: DE240701807 Sitz der Gesellschaft: Berlin-Schöneberg, AG Berlin-Charlottenburg, HRB 101380 B Vorstand: Roland Becker, Aufsichtsratsvorsitzender: Clemens C. Vogelsberg

3 3

fs.com device support
by Pieter Meyer 02 Nov '18

02 Nov '18

HI Adam Can you please add support for devices from fs.com https://www.fs.com/products/72945.html https://www.fs.com/products/29127.html https://www.fs.com/products/73467.html https://www.fs.com/products/29122.html https://www.fs.com/products/29123.html Regards Pieter Meyer

1 0

'rrdcached' Config Issue
by Gordon Cheng (gocheng) 02 Nov '18

02 Nov '18

Hi all, In an attempt to improve the performance (previous email thread with subject Performance Issue - High CPU with 'mysqld'?), I'm trying to use 'rrdcached' on a new setup (version 18.9.9428 (9th September 2018) with the following configuration: === sjc-observium-1:/etc/init.d# cat rrdcached <...snipped...> # Path to the apachectl script, server binary, and short-form for messages. rrdcached=/usr/sbin/rrdcached prog=rrdcached pidfile=/var/run/rrdcached/rrdcached.pid sockfile=/var/run/rrdcached/rrdcached.sock lockfile=/var/lock/subsys/rrdcached RETVAL=0 <...snipped...> - sjc-observium-1:/etc/sysconfig# cat rrdcached <...snipped...> RRDCACHED_USER="apache" OPTIONS="-w 1800 -z 1800 -f 3600 -s apache -l unix:/var/run/rrdcached/rrdcached.sock -j /var/tmp -m 664 -F -b /opt/observium/rrd -B" SOCKPERMS=0660 <...snipped...> - sjc-observium-1:/usr/lib/tmpfiles.d# cat rrdcached.conf d /run/rrdcached - apache apache sjc-observium-1:/usr/lib/tmpfiles.d# - sjc-observium-1:/opt/observium# grep rrd config.php //rrdcached #$config['rrdcached'] = "unix:/var/run/rrdcached/rrdcached.sock"; <<<====== will un-comment once rrdcached is configured and running sjc-observium-1:/opt/observium# - sjc-observium-1:/root# service rrdcached stop Stopping rrdcached (via systemctl): [ OK ] sjc-observium-1:/root# service rrdcached start Starting rrdcached (via systemctl): Job for rrdcached.service failed because a timeout was exceeded. See "systemctl status rrdcached.service" and "journalctl -xe" for details. [FAILED] sjc-observium-1:/root# - sjc-observium-1:/opt/observium# systemctl status rrdcached.service -l ● rrdcached.service - SYSV: rrdcached is a daemon that receives updates to existing rrd files, accumulates them, and writes updates to file Loaded: loaded (/etc/rc.d/init.d/rrdcached; bad; vendor preset: disabled) Active: failed (Result: timeout) since Wed 2018-10-31 16:39:48 PDT; 11min ago Docs: man:systemd-sysv-generator(8) Process: 2449 ExecStart=/etc/rc.d/init.d/rrdcached start (code=exited, status=0/SUCCESS) CGroup: /system.slice/rrdcached.service └─2453 /usr/sbin/rrdcached -w 1800 -z 1800 -f 3600 -s apache -l unix:/var/run/rrdcached/rrdcached.sock -j /var/tmp -m 664 -F -b /opt/observium/rrd -B -p /var/run/rrdcached/rrdcached.pid -l /var/run/rrdcached/rrdcached.sock Oct 31 16:34:51 sjc-observium-1 rrdcached[2453]: queue_thread_main: rrd_update_r (/opt/observium/rrd/aan-oob01/perf-pollermodule-fdb-table.rrd) failed with status -1. (/opt/observium/rrd/aan-oob01/perf-pollermodule-fdb-table.rrd: illegal attempt to update using time 1541024231 when last update time is 1541028534 (minimum one second step)) Oct 31 16:34:51 sjc-observium-1 rrdcached[2453]: queue_thread_main: rrd_update_r (/opt/observium/rrd/aan-oob01/perf-pollermodule-entity-physical.rrd) failed with status -1. (/opt/observium/rrd/aan-oob01/perf-pollermodule-entity-physical.rrd: illegal attempt to update using time 1541024224 when last update time is 1541028525 (minimum one second step)) Oct 31 16:34:51 sjc-observium-1 rrdcached[2453]: queue_thread_main: rrd_update_r (/opt/observium/rrd/aan-oob01/perf-pollermodule-hr-mib.rrd) failed with status -1. (/opt/observium/rrd/aan-oob01/perf-pollermodule-hr-mib.rrd: illegal attempt to update using time 1541024165 when last update time is 1541028466 (minimum one second step)) Oct 31 16:34:51 sjc-observium-1 rrdcached[2453]: queue_thread_main: rrd_update_r (/opt/observium/rrd/aan-oob01/perf-pollermodule-ipSystemStats.rrd) failed with status -1. (/opt/observium/rrd/aan-oob01/perf-pollermodule-ipSystemStats.rrd: illegal attempt to update using time 1541024166 when last update time is 1541028467 (minimum one second step)) Oct 31 16:34:51 sjc-observium-1 rrdcached[2453]: queue_thread_main: rrd_update_r (/opt/observium/rrd/aan-oob01/perf-pollermodule-loadbalancer.rrd) failed with status -1. (/opt/observium/rrd/aan-oob01/perf-pollermodule-loadbalancer.rrd: illegal attempt to update using time 1541024223 when last update time is 1541028524 (minimum one second step)) Oct 31 16:34:51 sjc-observium-1 rrdcached[2453]: queue_thread_main: rrd_update_r (/opt/observium/rrd/aan-oob01/perf-pollermodule-mempools.rrd) failed with status -1. (/opt/observium/rrd/aan-oob01/perf-pollermodule-mempools.rrd: illegal attempt to update using time 1541024147 when last update time is 1541028719 (minimum one second step)) Oct 31 16:39:48 sjc-observium-1 systemd[1]: rrdcached.service start operation timed out. Terminating. Oct 31 16:39:48 sjc-observium-1 systemd[1]: Failed to start SYSV: rrdcached is a daemon that receives updates to existing rrd files, accumulates them, and writes updates to file. Oct 31 16:39:48 sjc-observium-1 systemd[1]: Unit rrdcached.service entered failed state. Oct 31 16:39:48 sjc-observium-1 systemd[1]: rrdcached.service failed. sjc-observium-1:/opt/observium# === Any suggestions or docs/links showing how it can be resolved? Thanks. - Gordon

2 4

Sensor issues since approx November 1st
by Anthony Somerset 02 Nov '18

02 Nov '18

Hi There I’m running a test bed of observium at home seperately of our main installation - i had previously written a very basic observium agent module that polls current power usage for a home monitoring sensor and outputs it, and then a custom polling module that reads this data and basically graphs it as a power sensor under a device (https://gist.github.com/anthonysomerset/3860b7a3b650d8bbbf53faac2d5eeab5 <https://gist.github.com/anthonysomerset/3860b7a3b650d8bbbf53faac2d5eeab5>) the unix-agent is working same as before but since i updated overnight on 1st november the graph has disappeared and my event log is filled up with sensor added events: also under the device itself the sensor is saying deleted around 5 days ago (2018-10-27 00:01:04) this looks like immediately after it updated on that day (looks like last commit on that day was 9517) any thoughts on how i need to fix? Kind regards, Anthony Somerset Somerset Technical Solutions Ltd. www.somersettechsolutions.co.uk Registered in the UK – Company no. 07738444 VAT Registration No: 140 6916 22 T: +44 (0) 33 0088 2751 E: anthony(a)somersettechsolutions.co.uk PGP: 0x7C892BF5

2 2

Observium Syslog issues
by David Rossi 01 Nov '18

01 Nov '18

I have an installation of Observium that has been up and running perfectly for about 18 months. Last Friday I ran updates and now syslog is no longer working. I have found that prior to the upgrade, rsyslog was version 7, now I am at Version 8. In searching I found that a few configuration file changes, I did those, and still a no go. Has anyone else come across this? I am a novice at Linux, and totally at a loss here. I can do a tcpdump and sure enough the syslog messages are hitting the server, but not displayed within Observium. Any help would be appreciated, but, please keep in mind I am a Centos novice. Dave Rossi.

4 11

Juniper
by Christian Eriksson 01 Nov '18

01 Nov '18

Hi, I have some MX104 routers and now there is a firewall button with some empty graphs. What is the meaning of this? :) [cid:image001.png@01D471D0.1A58CAF0] Regards Christian

2 1

Auto install script
by Scott L. Kaiser 31 Oct '18

31 Oct '18

2 1

New Device AKCP SensorProbe2Plus
by Stefan.Immel＠stroeher.de 31 Oct '18

31 Oct '18

We startet to use a SensorProbe2 Plus from AKCP but unfortunatly it is not yet supported by observium. Anybody out there who uses it too and has it implemented? If not, I'm looking for ways to integrate it but unfortunatly I cannot find the right files to do that. Where are the definitions that contain the mappings from sysObjectID to the right OS and MIBS?

1 0

Support for Dell Storage (Compellent)
by Thomas Stather 31 Oct '18

31 Oct '18

Hi I am using the professional edition of Observium and was wondering, if it supports Dell storage arrays. I am particularly interested in the Dell Compellent series as i have 2 of them in production. I have the official Dell MIBS ()MIB2014.01.29) and im willing to help if not implemented. Thanks in advance :) Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany

2 1

Re: [Observium] Performance Issue - High CPU with 'mysqld'?
by Gordon Cheng (gocheng) 31 Oct '18

31 Oct '18

Thanks all. Yes, it's a new set up and a lot of new devices were added about 4 weeks ago. An update here. We just have the number of Cores increased from 4 to 16, and looks like there has been improvement in terms of performance now. But there is a new issue observed. Quite frequently (~1 out of 4 times), Observium is responding HTTP response code 500 with blank page when logging in, or when clicking around after login. Any thoughts or suggestions on this? Here are the logs when it happens: /opt/observium/logs/access_log: 171.68.241.12 - - [30/Oct/2018:21:29:53 -0700] "GET / HTTP/1.1" 500 1728 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:63.0) Gecko/20100101 Firefox/63.0" /opt/observium/logs/error_log: [Tue Oct 30 21:29:54.329931 2018] [:error] [pid 21511] [client 171.68.241.12:54771] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 135168 bytes) in /opt/observium/includes/db/mysqli.inc.php on line 316 [cid:image001.png@01D47099.AD6D0FA0] Thanks. - Gordon From: observium <observium-bounces(a)observium.org> on behalf of Mike Stupalov via observium <observium(a)observium.org> Reply-To: Observium <observium(a)observium.org> Date: Sunday, October 28, 2018 at 4:09 AM To: Observium <observium(a)observium.org> Cc: Mike Stupalov <mike(a)observium.org> Subject: Re: [Observium] Performance Issue - High CPU with 'mysqld'? Simon Mousey Smith via observium wrote on 27/10/2018 23:55: Hi Gordon I think from what I can see from the pics, the 3rd graph along, bottom row It looks like about 3-4 weeks ago its JUMPED UP in the wrapper processing times which means its taking too long to execute on each device or the main server As I see, 4 weeks ago added many new devices. It's not should be big trouble, but seems as need more optimizations, like: - use rrdcached - switch to SSD disks for such number of devices - RRDs and DB must use faster disks, SSD is mandatory for you. Did you change any configs then? Any updates to hardware, software, etc? Have u also tried the latest stable ? 9472 Have u also tried doing /opt/observium/poller.php -h gz-core01 -dd to see where it might be getting stuck? Regards Simon On 26 Oct 2018, at 03:15, Gordon Cheng (gocheng) via observium <observium(a)observium.org<mailto:observium@observium.org>> wrote: Thanks Adam. Our pollerlog pages are below. Should we still try to disable fdb-table as suggested? If so, any docs we can follow to disable it? Any other thoughts or suggestions? Thanks. - Gordon <image001.png> <image002.png> <image003.png> From: observium <observium-bounces(a)observium.org<mailto:observium-bounces@observium.org>> on behalf of Adam Armstrong via observium <observium(a)observium.org<mailto:observium@observium.org>> Reply-To: Observium <observium(a)observium.org<mailto:observium@observium.org>> Date: Tuesday, October 23, 2018 at 12:50 PM To: Chris Neam via observium <observium(a)observium.org<mailto:observium@observium.org>> Cc: Adam Armstrong <adama(a)memetic.org<mailto:adama@memetic.org>> Subject: Re: [Observium] Performance Issue - High CPU with 'mysqld'? Hi, You probably (definitely) need more cores and/or more I/O throughput capacity. It's likely that you have multiple overlapping poller_wrapper processes running because they can't finish quickly enough. what do the graphs on this page look like? http://dev.observium.org/pollerlog/ and what are the slowest devices on this : http://dev.observium.org/pollerlog/view=devices/ You may be able to disable a module or two you don't care about that's taking time : http://dev.observium.org/pollerlog/view=modules/ fdb-table is usually a good candidate. adam. On 2018-10-23 19:54:32, Gordon Cheng (gocheng) via observium <observium(a)observium.org<mailto:observium@observium.org>> wrote: Hi all, I have a new Observium setup (verion 18.9.9428 (9th September 2018)) with the following VM spec: Cores 4 Memory 64GB HD 500GB CentOS 7 PHP 7.0.31 MySQL 5.5.60-MariaDB and with the following network devices to be monitored: Devices - 634 (total), 597 (up), 37 (down) Ports - 58,032 (total), 27,664 (up), 19,967 (down) Sensors - 47,639 (total), 43,243 (ok), 4,396 (down) Statuses - 5,880 (total), 5,854 (ok), 10 (alert) --- Issue is that we are frequently seeing the following error when connecting on GUI/CLI, with slow response time on GUI/CLI: DB Error 1040: Too many connections And we are seeing gaps (broken graphs) like the following: [cid:image001.png@01D46AC5.2F7A6900] We have tried to bump up the number of 'max_connections' from original 151 to 500 and then 200, but it didn't help: sjc-observium-1:/etc# grep max_conn my.cnf max_connections=200 sjc-observium-1:/etc# And it's observed that the CPU load is heavy with 'mysqld': top - 09:36:17 up 35 days, 18:54, 2 users, load average: 74.18, 89.49, 82.67 Tasks: 665 total, 79 running, 586 sleeping, 0 stopped, 0 zombie %Cpu(s): 62.9 us, 36.9 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st KiB Mem : 65810376 total, 2511836 free, 5989292 used, 57309248 buff/cache KiB Swap: 4193020 total, 4141016 free, 52004 used. 59172312 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5152 mysql 20 0 2749132 664216<tel:0%202749132%20664216> 9164 S 20.7 1.0 4058:17 mysqld 31879 root 20 0 419676 27564 8264 R 4.2 0.0 0:00.13 php 31769 root 20 0 417212 25532 8336 S 3.6 0.0 0:00.12 php 31933 root 20 0 416868 25116 8148 S 3.2 0.0 0:00.10 php 31935 root 20 0 416736 24700 7832 S 3.2 0.0 0:00.10 php <snip> My 'config.php' is pretty much with default values. --- I'm new to Observium. It'd be greatly appreciated if someone can shed some light how it can be resolved. Thanks. - Gordon _______________________________________________ observium mailing list observium(a)observium.org<mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ 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

2 1