Hi Morten,
Thanks for responding. Graphite-carbon was installed via the Debian package while the graphite-web was installed using pip. I was able to trace the source of the problem to the webapp's config file as suggested. I ended up performing a new install on a different machine in an attempt to save some time.
The new install was successful and Graphite appears to be working properly. NAV on the other hand renders system metrics graphs but returns empty graphs for port metrics even though Graphite (via browser) presents no issues with port metrics rendering. Given this would probably fall under a rendering issue, I'll see what I can find in the archives on this. Will send out an email in the event I'm unable to sort the "port metrics" issue.
Thanks for your time. Sincerely, Ukeme Noah
On Wed, May 28, 2014 at 3:23 AM, Morten Brekkevold < morten.brekkevold@uninett.no> wrote:
On Tue, 27 May 2014 11:12:37 -0400 Ukeme Noah ukeme.noah@ryerson.ca wrote:
Greetings Everyone,
Hi Ukeme,
All dependencies were installed successfully. Python modules were
installed
using PIP. Graphite and Carbon appear to be installed and working as well (at this point, I launch carbon and graphite using the scripts " carbon-cache.ph" and "run-graphite-devel-server.py" located in "/opt/graphite/bin".
Access to NAV (as well as Graphite's) main page over a web browser
present
no issues however, Availability under Status reads "Graphite
unreachable".
This error usually means NAV has a problem contacting the Graphite web interface. Is the base URL specified correctly in NAV's `graphite.conf`, and is that IP address/port combination open for for access from the NAV server?
In addition, the Graphite web interface presents entries for Carbon and none for NAV.
That is, however, a bit strange. Did you install all the Graphite components (whisper, carbon, graphite-web) using pip or Debian packages?
I am lead to believe that the carbon backend is working given the
contents
of the folder "/var/lib/graphite/whisper/nav" includes entries for NAV seeded devices.
If your data is in `/var/lib/graphite/whisper/nav`, it sounds like you installed the graphite-carbon Debian package. Then you say you have `/opt/graphite/bin/run-graphite-devel-server.py`, which sounds like you installed graphite-web from source or using pip.
Is graphite-web correctly configured to look for whisper files in `/var/lib/graphite/whisper/`, or is it looking in `/opt/graphite/storage/whisper`? Under Graphite's typical /opt layout, the webapp's config is found in `/opt/graphite/webapp/graphite/`.
-- Morten Brekkevold UNINETT