-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] overseer shows setup screen after update! loses services settings BUT NOT the request and user data #27
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This is the first time we have heard of this issue. This seems to be only affecting Unraid, and I doubt it is a container issue. My only suggestion is to keep track of the settings json file in appdata, and see if it changes the next time this happens. |
Ok, I just made a backup of the file just to be able to compare them after I get the problem again! Thanks for the answer Roxedus |
This is not unique to Unraid. I am using docker on an OMV install and having the exact same issue. Every update is wiping the settings. There must be a path that is not being saved within /config |
@Wdavery would be helpful if you could post your compose please. |
Config directory contains:
Worth noting that settings.json is last modified today, it seems to remain current. |
What's most interesting is the backend seems to continue on while the frontend is prompting to setup:
These logs are post-update, pre-setup. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale. |
Still this is the only 2 reports of this issue I've seen and unable to replicate at all. Only thing I could suggest is where your FYI - I have never used OMV so I have no idea how their shared folders setup. |
Correct about the fuse layer. I will give that a try. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I have that issue too, the settings file is cleared. Its not running on a fuse layer, its runnig in my docker swarm. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I just had this exact behavior on a bog standard Ubuntu 22.04 install. Here's my compose if it helps.
|
Just to keep you updated. We have still not managed to replicate this. |
Any other information that I can give that might be helpful? Unfortunately I had to reboot my VM host multiple times today due to some unrelated issues I was having (thanks ever so much, Realtek) so some of the relevant logs may be gone. It's not a huge issue since once you re-add the plex and sonarr / radarr info everything is back to normal, its just annoying. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
After an update when I try to open the Webui overseer shows me the setup screen!
I have to go through the setup page by adding the plex instance and the radarr and sonarr info and then it throws me in the request menu like nothing happened. It keeps my user data my request history and everything!
Its so weird. The problem DOES NOT happen after a container restart or rebuild only after an update! same thing happened once on my tauttily container from linuxserver too, and many people have posted about this problem on reddit without finding an answer. I will provide whatever you guys need to find what's going on.
I also pasted the logs that have some errors talk about the setup page etc.
Expected Behavior
For the container to update normaly and not throw the setup page
Steps To Reproduce
Problem happens after an update. Just update and run
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: