-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Unable to reach grafana dashboard and query influxdb #286
Comments
I think you should get on lwamaas system in order to access those. It's a separate gateway. |
@kembyct Ok, I don't think I have access to lwamaas, what hostname should I use to ssh there? And which ports are used for grafana, etc.? Currently I have this for dsa110maas in my .ssh/config, so I assume its something similar:
|
@rh-codebase @kembyct Vikram informed me that h00 is currently refusing to boot, and that is likely the cause of this. We can pause on this issue until its back online. |
OK. But it's reachable from lwamaas. I tried it. |
I take it back. I've just noticed the grafana on lwa system is seperate from the one on dsa system. I'll look further into this, and get back to you shortly. |
dsa110maas is the correct gw to use. dsa110 is separate from lwa but they do use the same paradigm. grafana, influx are separate and exist for lwa and dsa. @mbsherma The reason they are not reachable is because the server hosting those services is down. Trying to get it back online. |
Gotcha, Vikram informed me about the down server as well, thanks for taking a look! |
I am currently unable to reach the grafana dashboard or query from influxdb. By my understanding, they should be reachable via dsa110maas or dsastorage, which I am able to reach by ssh over the ovro network (e.g. dsastorage.ovro.pvt and dsa110maas.ovro.pvt). When I tried using 'ping grafanaservice.sas.pvt and ping influxdbservice.sas.pvt', I get the error 'Destination Host Unreachable'. Are they reachable over another network? I'm aware this may just be due to the changes during commissioning and become more stable later on.
Thanks!
The text was updated successfully, but these errors were encountered: