I had setup my raspbery pi3 with influxdb and grafana and everything was working fine.
Suddenly the influxDB has stopped working.
Home assistant UI shows this
I checked the influxdb webpage and it has stored results of measurements upto Jan 10. There was no change done after that.
However, the command line influxdb interface isn’t working.
I tried typing in influx in the terminal and it used to work earlier but now it says “Failed to check token:”
I tried updating influxdb by typing sudo apt-get update && sudo apt-get install influxdb
but that didnt work
Any idea what I can do to ensure that influxdb starts working again?
Had the same problem. I ran the migration script, but after that, both influxdb and grafana crashed after a few hours every time, not responding to anything anymore. After a restart of my raspberry, the crashes were gone, but I got the same message as you have in Home Assistant. Probably something went wrong with the migration script, I don’t know. But after a drop of the home_assistant database in influxdb (and recreating a new one) and a restart of home assistant, it worked fine again. Note however, that you will loose all data in influxdb in this way. For me, that was no problem, as the data was not so important.
I ran the influxdb migration script (after upgrading HA to latest version) but I am stuck at 66.67% (I’ve been waiting for more than an hour):
user1@unix:~$ /srv/hass/bin/hass --script influxdb_migrator -u user -p password -d home_assistant
Cloning from home_assistant to home_assistant__old
[####################################################################] 100.0%
Migrating from home_assistant__old to home_assistant
[#############################################-----------------------] 66.67%
First attempt it was stuck at 33.33%, and then I aborted and restart the script, now it is stuck at 66.67%. I’ve tried abort ing and restarting the script several times but still no luck, it cannot pass 66.67% barrier, it’s been about 1 hour waiting now.
Please ignore my error above, it turns out I have hardware issue. Well, the server is a 6-years old laptop.
The issue was intermittent that made it harder to identify.
After several hours pulling my hair, I end-up reinstalling the OS, only to find out I have a bad memory module!