InfluxDB Losing Database and Users After Service Restart #6
Comments
|
👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull. |
|
Hm, just noticed my influxdb is empty as well. Missing the database and all users gone, don't remember restarting it tho. Can confirm I do have auth enabled (default) as well. |
|
I'm running the add-on with |
|
Same issue here. I've tried switching all the flags on/off (auth, ssl, ip6) to no avail. System Log reports And log from InfluxDB add-on
|
|
@petrfaitl The second error is perfectly normal/fine. Kapacitor starts quicker then InfluxDB, so it fails to connect the first time. It will eventually pick up as soon as InfluxDB is started. So both of those errors are not related, known and kinda expected. |
|
OK, somebody actually handed over some big logs that showed the issue. And the thing is: InfluxDB uses the Hassio Add-on API token as an internal password. This causes issues now. Good news: Your data isn't gone. It is just Chronograf & Kapacitor who can't access the data. I'm tagging this issue high priority and will provide updates ASAP. |
|
Thanks so much for jumping on this @frenck -- really appreciate the work you put in for these add-ons. |
|
I've added in a fix for this issue on the development branch, this fix needs testing. I currently do not have access to a slow device (Raspberry Pi), which is a cause of this problem as well. |
|
OK, so reproducing fails on my test setups (I guess the size of the database matters in this case...). I did, however, restart the add-on like 50 times or so. This release improves on many levels, so I'll do some final testing on the new Hassio API security stuff and will release it tonight. In this case, I'm going to assume this fixes it. (It sure won't break it...) I'll leave this issue open and hope someone is willing to report back on it after upgrading. |
🎉 Released v1.1.0Please give me some feedback on this 🙏 |
|
Hi Frenck, checked this morning (my time in New Zealand) and V1.1.0 is not coming up in Hass.io on my Raspberry PI. I still have 1.0.1 installed and no 'update' option. Can I force an update? Can I uninstall and reinstall without losing my data? oh...saw it was updated only 11 minutes ago, I am probably the first user in the world awake right now to use it :-) |
|
Hey, Found a quick fix for my machine, remove this from configuration.yaml http: Workes now for me. |
|
I've got the update too, but it still failed untill i removed http... |
|
@matthew73210 That cannot possibly be related at all! |
|
@smbunn In the Hass.io add-on store there is a reload button in the top right. Hit it! |
|
OK, that allowed me to see the update which I am installing now. |
|
@frenck Okay maybe a glitch for 'my' system, because that's the only thing I changed and it started working. Thanks for the rapid update. |
|
I have completed the update and InfluxDB will not start: |
|
Did you restart hassio? |
|
@smbunn Thanks! That is my bad! Going to create a hotfix right now! 🚑 |
|
About to do that now |
|
🚑 Created patch, building an edge release right now. As soon as that one finishes, I'll tag a v1.1.1 release. Update: Tagged release v1.1.1, awaiting release builds to finish... |
🎉 Released v1.1.1Please give me some feedback on this 🙏 |
|
Installing now |
|
It seems to be ins some sort of loop. |
|
has moved on |
|
@smbunn Not that is just reporting in... it will do that for a max of 60 seconds after it will stop doing that. What has changed that it now tries to wait for InfluxDB to be started before actually trying to fix the users. It tried to do that every 2 seconds, so that is why you'll see it more often. It will pass now. |
|
It is running! My databases are back. My users are back! Thanks Frenck, you are a star! |
|
I call this resolved for now. If someone still has issues with this, please re-open this issue or just add a comment to it. (This issue will remain unlocked for 30 days). |
I get this now and influx wont start... (i had it on autoupdate and it must have updated during the night to 1.1.1) |
|
Hmmm... seems like 60 seconds is not enough wait time for your system @rpeders... |
|
My influxdb also won't start but I'm always only getting INFO: InfluxDB init process in progress... 5 times before [cont-init.d] 20-system-users.sh: exited 1. I tried changing to debug and trace levels and this added a line above [cont-init.d] 20-system-users.sh: exited 1.: Full log: |
|
@Pteranodon That is not related. This issue is about losing users & databases, you are now reporting in an issue about a fatal error of the add-on, causing it not to start. Don't go off-topic on GitHub issues, that is really not appreciated. I've created issues #9 for you. |
|
For the upcoming release, I've improved this waiting for InfluxDB logic overall, which takes care of the remaining issues listed here. Closing this issue. |
ghost
removed
the
|
I have also that "INFO: InfluxDB init process in progress..." until failure. When that new release should be out? |
|
I've just finished the cross-platform tests, so I'm currently writing the release notes. |
|
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Problem/Motivation
When I restart my InfluxDB addon service, it would remove the users and databases it created.
Expected behavior
I expect my database and users to remain.
Actual behavior
The databses and users are removed
Steps to reproduce
When I log into Hass.IO and go to the addons, I launch the InfluxDB addon and click the restart service.
I did hear back from a reddit thread that another user was having this issue. It was due to the config section having
"auth": trueHere is the link to the reddit thread/comment
Here is my configuration and it now works by changing auth to false:
{
"log_level": "info",
"username": "##remark##",
"password": "##remark##",
"auth": false,
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"ipv6": true
}
Proposed changes
Update InfluxDB to allow for authentication.
The text was updated successfully, but these errors were encountered: