Hi all,
I just noticed that the rrd for my alerts have been created in the root rrd directoy instead of in each device directory.
Is this a known issue ?
The alerts availability graphs don’t work as they look for the rrd in the wrong place :
RRDTool Output: ERROR: opening '/data/observium/rrd/lswc11u21 /alert-3375.rrd': No such file or directory
Total time: 0.012 | RRDtool time: 0.011s
# ls -l rrd/alert-337* | head
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3370.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3371.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3372.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3373.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3374.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3375.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3376.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3377.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3378.rrd
-rw-r--r-- 1 root root 233120 Feb 29 12:25 rrd/alert-3379.rrd
It looks like only the visualization code is looking for the rrd in the wrong place.
As If I copy the rrd into the right directory the graph is displayed correctly and it shows that it has been updated when the alert failed.
I am using the stable svn version :
# svn info
Path: .
Working Copy Root Path: /data/observium
URL: http://svn.observium.org/svn/observium/branches/stable
Repository Root: http://svn.observium.org/svn
Repository UUID: 61d68cd4-352d-0410-923a-c4978735b2b8
Revision: 7599
Node Kind: directory
Schedule: normal
Last Changed Author: adama
Last Changed Rev: 7535
Last Changed Date: 2016-01-27 13:11:02 +0000 (Wed, 27 Jan 2016)
Best regards,
Louis
Louis Bailleul Computer Systems Engineer Imaging & Engineering | Imaging Telephone: +44 1932 376000 Direct: +44 1932 376842 VOIP: 74416842 Mobile: +44 7786 525307 Email: louis.bailleul@pgs.com A Clearer Image | www.pgs.com |
Address: 4 The Heights, Brooklands, Weybridge, Surrey, KT13 0NY, United Kingdom This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author. |