Hi,
I did restart the apache server. I have done some tcpdumping and find out very interesting thing:
- when I access ipdevinfo for some device it communicates with graphite server without any problém (Requests are truncated, I attached even some responses, the server serves them all) I think that this serves for availability and response info in status pane.
http://graphite:80/metrics/find?query=nav.devices.DEVICE.%2A http://graphite:80/metrics/find?query=nav.devices.DEVICE.cpu.%2A http://graphite:80/metrics/find?query=nav.devices.DEVICE.cpu.Linecard_slot_1... http://graphite:80/metrics/find?query=nav.devices.DEVICE.ipdevpoll.%2A ...
http://graphite/render?format=json&from=-1day&target=nav.devices.DEV... [{"target": "nav.devices.DEVICE.ping.packetLoss", "datapoints": [[0.0, 1396354560], [0.0, 1396354620], [0.0, 1396354680], [0.0, 1396354740], [0.0, 1396354800], ... http://graphite/render?format=json&from=-1week&target=nav.devices.DE... [{"target": "nav.devices.DEVICE.ping.packetLoss", "datapoints": [[0.0, 1395836400], [0.0, 1395836700], [0.0, 1395837000], [0.0, 1395837300], [0.0, 1395837600], ...
- since then it does not connect graphite server at all - when I click on Port Metrics -> some interface, I just got an error - Error loading image. I have done even some code crawling and found an actual requested link: /ipdevinfo/g/port/1/Octets/?timeframe=day
But I wasn't able to trace it any further. I expect, that NAV actually should proxy this request to graphite (thing which is broken). I'm no expert in python so I got lost there.
I hope this can help you pin down the problem.
I switched to port 80 on graphite side to make things easier.
Best regards
Mat -----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: Wednesday, April 02, 2014 9:43 AM To: JABUREK Martin Cc: nav-users@uninett.no Subject: Re: Graphite on other machine
On Mon, 31 Mar 2014 07:01:09 +0000 "Martin.Jaburek@cah.cz" Martin.Jaburek@cah.cz wrote:
When I first started NAV, it was configured to use the graphite on the same machine as NAV. It worked.
When I changed it and restarted NAV processes it sent statistics to the new IP (I confirmed it via graphite web fronted), but it still tries to access old graphiteweb for rendering graphs, not the one changed in grahpite.conf.
You restarted NAV processes, but did you restart Apache (in which the NAV web UI lives)?
Can there be a problém with certificate? (it is self signed one)
If there was, it wouldn't cause NAV to get graphs from the old URL, it would cause an error. We haven't actually checked to see how accessing Graphite over HTTPS works, so it seems you may be a guinea pig here ;)
-- Morten Brekkevold UNINETT