x/fuel-plugin-influxdb-grafana
Code Issues Proposed changes
Files
ce43f9b5f6d7a6fb6232a44eaf2ee5ea98aada47
fuel-plugin-influxdb-grafana/doc/source/troubleshooting.rst
Maria Zlatkova ce43f9b5f6 [docs] Edits the StackLight InfluxDB-Grafana plugin guide structure 
Edits the table of contents and overall structure of the
StackLight InfluxDB-Grafana plugin for Fuel documentation.

Change-Id: Icc9d73fca27513e8336cca1486bfc83634b5d116
2016-07-20 17:33:10 +03:00

1.6 KiB
Raw Blame History

Troubleshooting

If you get no data in Grafana, follow these troubleshooting tips.

  1. First, check that the LMA Collector is running properly by following the LMA Collector troubleshooting instructions in the LMA Collector Fuel Plugin User Guide.

  2. Check that the nodes are able to connect to the InfluxDB cluster via the VIP address (see above how to get the InfluxDB cluster VIP address) on port 8086:

    root@node-2:~# curl -I http://<VIP>:8086/ping

    The server should return a 204 HTTP status:

    HTTP/1.1 204 No Content
Request-Id: cdc3c545-d19d-11e5-b457-000000000000
X-Influxdb-Version: 0.10.0
Date: Fri, 12 Feb 2016 15:32:19 GMT

  3. Check that InfluxDB cluster VIP address is up and running:

    root@node-1:~# crm resource status vip__influxdb
resource vip__influxdb is running on: node-1.test.domain.local

  4. Check that the InfluxDB service is started on all nodes of the cluster:

    root@node-1:~# service influxdb status
influxdb Process is running [ OK ]

  5. If not, (re)start it:

    root@node-1:~# service influxdb start
Starting the process influxdb [ OK ]
influxdb process was started [ OK ]

  6. Check that Grafana server is running:

    root@node-1:~# service grafana-server status
* grafana is running

  7. If not, (re)start it:

    root@node-1:~# service grafana-server start
* Starting Grafana Server

  8. If none of the above solves the problem, check the logs in /var/log/influxdb/influxdb.log and /var/log/grafana/grafana.log to find out what might have gone wrong.