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/`.