Grafana do not start after install - edited with log errors

OpenHab run on RPi4 with InfluxDB + Grafana. I cannot get access to grafana.

Platform information:

  • RPi4B with openhabian and openHAB 2.5.0~S1549-1 (Build #1549)
  • Installed InfluxDB and Grafana from openhabian-config

After install port 8080 and 9001 works as expected, but when I try to reach grafana throughIP :3000 from browser, i cant connect.
checking grafana-server.service:

[15:34:37] openhabian@openhab:~$ sudo systemctl status grafana-server
● grafana-server.service - Grafana instance
   Loaded: loaded (/usr/lib/systemd/system/grafana-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-08-19 15:28:37 CEST; 7min ago
     Docs: http://docs.grafana.org
  Process: 14886 ExecStart=/usr/sbin/grafana-server --config=${CONF_FILE} --pidfile=${PID_FILE_DIR}/grafana-server.pid -
 Main PID: 14886 (code=exited, status=1/FAILURE)

Aug 19 15:28:37 openhab systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Aug 19 15:28:37 openhab systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 5.
Aug 19 15:28:37 openhab systemd[1]: Stopped Grafana instance.
Aug 19 15:28:37 openhab systemd[1]: grafana-server.service: Start request repeated too quickly.
Aug 19 15:28:37 openhab systemd[1]: grafana-server.service: Failed with result 'exit-code'.
Aug 19 15:28:37 openhab systemd[1]: Failed to start Grafana instance.

I have tried to reinstall without any success.

After running without grafana to visualize data I tried to see why the grafana-server.service fails.

$ sudo journalctl | grep grafana

show:

Sep 02 14:42:15 openhab systemd[1]: grafana-server.service: Main process exited, code=exited, status=1/FAILURE
Sep 02 14:42:15 openhab systemd[1]: grafana-server.service: Failed with result ‘exit-code’.
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 4.
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Starting Grafana” logger=server version=5.4.3 commit=6539180 branch=HEAD compiled=2019-01-14T15:26:26+0100
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Config loaded from” logger=settings file=/usr/share/grafana/conf/defaults.ini
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Config loaded from” logger=settings file=/etc/grafana/grafana.ini
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Config overridden from command line” logger=settings arg=“default.paths.data=/var/lib/grafana”
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Config overridden from command line” logger=settings arg=“default.paths.logs=/var/log/grafana”
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Config overridden from command line” logger=settings arg=“default.paths.plugins=/var/lib/grafana/plugins”
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Config overridden from command line” logger=settings arg=“default.paths.provisioning=/etc/grafana/provisioning”
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Path Home” logger=settings path=/usr/share/grafana
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Path Data” logger=settings path=/var/lib/grafana
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Path Logs” logger=settings path=/var/log/grafana
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Path Plugins” logger=settings path=/var/lib/grafana/plugins
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Path Provisioning” logger=settings path=/usr/share/grafana/conf/provisioning
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“App mode production” logger=settings
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Writing PID file” logger=server path=/var/run/grafana/grafana-server.pid pid=28876
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Initializing HTTPServer” logger=server
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=info msg=“Initializing SqlStore” logger=server
Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=eror msg=“Server shutdown” logger=server reason=“Service init failed: Fail to connect to database: Unknown database type: influxdb”
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Main process exited, code=exited, status=1/FAILURE
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Failed with result ‘exit-code’.
Sep 02 14:42:16 openhab sudo[28882]: openhabian : TTY=pts/0 ; PWD=/run ; USER=root ; COMMAND=/bin/systemctl status grafana-server
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 5.
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Start request repeated too quickly.
Sep 02 14:42:16 openhab systemd[1]: grafana-server.service: Failed with result ‘exit-code’.
[

It seems that the cause is reported by the statement

Sep 02 14:42:16 openhab grafana-server[28876]: t=2020-09-02T14:42:16+0200 lvl=eror msg="Server shutdown" logger=server reason="Service init failed: Fail to connect to database: Unknown database type: influxdb"

However, I am not able to see why the influxdb should not be known. Storage to the influxdb database works fine, and is visualized in habpanel.

Help is appreciated.

Thanks!

what does the command

sudo journalctl -xu grafana

show ?

@Wolfgang_S: It shows not so much I am afraid:

[21:05:47] openhabian@openhab:~$ sudo journalctl -xu grafana -- Logs begin at Wed 2020-08-19 18:19:37 CEST, end at Wed 2020-08-19 21:05:50 CE -- No entries --

Did you restart the system in the meantime ?
I am asking because this log starts at 18:19:37 CEST while the earlier post showed that the service was tried to start around 15:28:37 CEST.

@ Wolfgang_S: No good answer I am afraid. As I left the house around 4PM the VPN connection went down to the site with the installation. May that have anything to do with the timing?

@Wolfgang_S I tried again after the VPN went down again.

[22:17:39] openhabian@openhab:~$ sudo systemctl status grafana-server
[sudo] password for openhabian:
● grafana-server.service - Grafana instance
Loaded: loaded (/usr/lib/systemd/system/grafana-server.service; enabled; vend
Active: failed (Result: exit-code) since Wed 2020-08-19 15:28:37 CEST; 6h ago
Docs: http://docs.grafana.org
Process: 14886 ExecStart=/usr/sbin/grafana-server --config=${CONF_FILE} --pidf
Main PID: 14886 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomple

[22:17:50] openhabian@openhab:~$ sudo journalctl -xu grafana
– Logs begin at Wed 2020-08-19 19:11:16 CEST, end at Wed 2020-08-19 22:18:35 CE
– No entries –

This fixed my problem:
rm /var/lib/grafana/grafana.db
** systemctl restart grafana-server**