- observium - lists.observium.org

Re: [Observium] update.php fails to run on latest svn release 7273
by Jason Scholl 17 Dec '15

17 Dec '15

That worked, thanks. I also see that update.php got updated so that it doesn't support direct calls, nice touch.

1 0

New alert options
by Anders Johansson 17 Dec '15

17 Dec '15

Hi, After upgrading to the latest Observium (pro) I've noticed a lot of new alerting destination options. Just curios. * Are they all implemented or just in UI? * If any are activated, how do I configure them? We have internal email to SMS gateways, would it be possible to create one that uses a specific SMS template? I'd like to keep my sms messages short and don't mind creating one myself. When I looked at the code last time it didn't seems to be to much trouble, but perhaps it easier know when some of the code might be written? //Anders

3 3

Re: [Observium] update.php fails to run on latest svn release 7273
by Jason Scholl 17 Dec '15

17 Dec '15

Deleting and re-syncing includes didn't work, though I was able to get it to run successfully by swapping these two lines in update.php include_once("includes/definitions.inc.php"); include("includes/functions.inc.php"); get_obs_attrib is defined in 'includes/common.inc.php', but that is only getting included into update.php through 'includes/functions.inc.php'.

2 1

update.php fails to run on latest svn release 7273
by Jason Scholl 16 Dec '15

16 Dec '15

I just attempted to upgrade to release 7273 and update.php fails to run. It gives no output (just return code 255), and logs nothing to update-errors.log or any other log file. My php skills are pretty weak, but a bit of "got here" debugging lead me through the following. includes/update/update.php 21: include_once("includes/definitions.inc.php"); #bailed on this line includes/definitions.inc.php 513: $rev_old = @get_obs_attrib('current_rev'); #bailed on this line I wasn't able to track it down any further than that because I couldn't even seem to get get_obs_attrib to execute. As a last ditch effort, I also tried commenting out all of my config except the absolutely required pieces, but it still failed in the same way. Is anyone else having this problem or have any ideas?

2 1

Contact Destination - Local file
by Spencer Ryan 16 Dec '15

16 Dec '15

Would it be possible to add a local file option to the providers for a contact? There are situations where we would like to manipulate the data with a script of our own based on triggered alerts and recoveries and instead of mucking around the DB by hand having Observium write out the alerts to a file would be the easiest. Maybe just have it take a path and just >> the alert contents to whatever the user enters? *Spencer Ryan* | Senior Systems Administrator | sryan(a)arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com

5 7

Not alerting (probably user fail)
by Robert Williams 16 Dec '15

16 Dec '15

Hi, We've just finished migrating some of our monitoring targets to an additional instance of Observium, everything is polling fine and all the historic data etc. has been moved OK. The only thing which remains broken is that none of the alerts are actually sending their emails. They do show as being in an alert state OK, for example: However, no actual 'Alerted' time is ever recorded - and no email is ever sent. The sendmail element works fine with: sendmail -vt < testmail.txt The test contains the correct FROM and DEFAULT from the config.php in Observium and this delivers fine. Problem is, it was a very long time ago that I originally configured Observium alerting on the first box and I'm probably missing something stupid. Relevant config sections below: Both of these sections are identical to the working system they were copied from, which works fine. The postfix config is also identical to the working server and I'm confident postfix is OK as the test from it are fine: myhostname = OBSERVIUM.x.y alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = OBSERVIUM, OBSERVIUM.x.y, localhost relayhost = 1.2.3.4 mailbox_size_limit = 0 recipient_delimiter = + Can anyone assist by pointing me at the switch I've obviously failed to turn on, or let me know what additional debugs I can provide to help track this? Cheers! Robert Williams Custodian Data Centre Email: Robert(a)CustodianDC.com http://www.CustodianDC.com

2 2

Alerts, metrics and attributes for applications
by Alex Winder ＠ M5i 16 Dec '15

16 Dec '15

Hi everyone, Does anyone know if there are any attributes or metrics for the UNIX agent applications, in particular NGINX, MySQL, Apache, and PowerDNS Recursor. I'm looking to create some alert checkers for them if it's at all possible. The only information I can find about the attributes and metrics is the following: http://www.observium.org/docs/attribs_metrics/ https://github.com/mgmoerman/docs/blob/master/observium-alert-checkers.md Regards, Alex.

2 2

hd-screen goofed up
by Simon Smith 16 Dec '15

16 Dec '15

Hi Adam, oh dear, the HD update in revision 7264, has goofed up my screen :( Ive had a HDPI Macbook Pro 2012 for years now the issue only appears on servers page tho? i goto our mikrotik switches - fine, tp-links - fine, just not linux or windows servers attached is screenshot for you :) Regards Simon

3 4

Re: [Observium] RRD Perms Issue - Error Drawing Graph
by Adam Armstrong 15 Dec '15

15 Dec '15

It seems that someone has modified your cron jobs to no longer be run as root, since your rrds were created by root and svn has no ability to change them. You need to work out where the poller is run from. It should be /etc/cron.d/observium Adam. Sent with AquaMail for Android http://www.aqua-mail.com On 15 December 2015 18:08:08 Robbie Wright <robbie(a)siuslawbroadband.com> wrote: > Not sure who the poller is running as. What's the easy way to check that? > > Yes, svn update has always been run as su. > > /opt/observium/rrd is owned by www-data, not root unlike the other folders > in the main directory. However, digging into the directory, all of the > folders inside for each host are all owned by root. > > > Robbie Wright > Siuslaw Broadband <https://siuslawbroadband.com> > 541-902-5101 > > On Tue, Dec 15, 2015 at 9:24 AM, Adam Armstrong <adama(a)memetic.org> wrote: > >> Are you running your poller observium poller as a non-root user? >> >> Did you svn up as root? >> >> The contents of the rrd directory, and anything else written to by the >> poller, should be owned by the user who runs the poller. >> >> Adam. >> >> Sent with AquaMail for Android >> http://www.aqua-mail.com >> >> On 15 December 2015 17:06:24 Robbie Wright <robbie(a)siuslawbroadband.com> >> wrote: >> >>> Recently upgraded from 69xx to 72xx after we renewed our license and it >>> broke all of our RRD's, resulting in the "Error Drawing Graph" issue. >>> >>> Running this "./poller.php -h <hostname> -m ports -d" gives me two >>> noticeable, but unobjectionable to me things: >>> >>> SNMP_STATUS[TRUE] >>> o Device status Device is reachable by PING (8.28ms) and SNMP >>> (81.63ms) >>> >>> RRD CMD[update /opt/observium/rrd/hostname/status.rrd N:1] >>> RRD RUNTIME[0.0012s] >>> RRD STDOUT[ERROR: opening '/opt/observium/rrd/hostname/status.rrd': >>> Permission denied] >>> RRD_STATUS[FALSE] >>> >>> and this at the end of the results: >>> >>> >>> Log file '/opt/observium/logs/observium.log' is not writable, check file >>> permissions. >>> >>> >>> So clearly some type of permission issue but not sure what happened >>> during the upgrade that would have caused this. Any thoughts on what >>> chmod's need to be set on the directories or what else could have went >>> haywire? >>> >>> >>> >>> Robbie Wright >>> Siuslaw Broadband <https://siuslawbroadband.com> >>> 541-902-5101 >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>> <http://postman.memetic.org/cgi-bin/mailman/listinfo/observium> >>> >>> >> _______________________________________________ >> observium mailing list >> observium(a)observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> >> > > > > ---------- > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >

3 10

RRD Perms Issue - Error Drawing Graph
by Robbie Wright 15 Dec '15

15 Dec '15

Recently upgraded from 69xx to 72xx after we renewed our license and it broke all of our RRD's, resulting in the "Error Drawing Graph" issue. Running this "./poller.php -h <hostname> -m ports -d" gives me two noticeable, but unobjectionable to me things: SNMP_STATUS[TRUE] o Device status Device is reachable by PING (8.28ms) and SNMP (81.63ms) RRD CMD[update /opt/observium/rrd/hostname/status.rrd N:1] RRD RUNTIME[0.0012s] RRD STDOUT[ERROR: opening '/opt/observium/rrd/hostname/status.rrd': Permission denied] RRD_STATUS[FALSE] and this at the end of the results: Log file '/opt/observium/logs/observium.log' is not writable, check file permissions. So clearly some type of permission issue but not sure what happened during the upgrade that would have caused this. Any thoughts on what chmod's need to be set on the directories or what else could have went haywire? Robbie Wright Siuslaw Broadband <https://siuslawbroadband.com> 541-902-5101

2 2