Skip to content
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]: The contents of the settings.yml file are gone and the default settings are back #113

Closed
tOOmki opened this issue Dec 3, 2024 · 9 comments
Labels
bug Something isn't working

Comments

@tOOmki
Copy link

tOOmki commented Dec 3, 2024

Describe the bug

I go to the page and I get this message:
"No devices found on this server."

The contents of the settings.yml file are gone and the default settings are back.
This is the third time this has happened.

I did not do any restart.
Version 4.0.2

Debug Output

.Where can I find the logs ?

Steps to reproduce

  1. none

Device Type

Proxmox 8.2.4

UPS Device

APC Back-UPS CS 350, APC Back-UPS CS 650, CyberPower UT850EG

Last Working Version

No response

@tOOmki tOOmki added the bug Something isn't working label Dec 3, 2024
@Brandawg93
Copy link
Owner

This may be fixed in #115. Could you try out the latest test version and let me know if it's working better for you?

brandawg93/peanut:test

@tOOmki
Copy link
Author

tOOmki commented Dec 4, 2024

I use https://community-scripts.github.io/ProxmoxVE/ for installation
I don't know how to change the version to "better settings".

@Brandawg93
Copy link
Owner

You just need to switch to the test tag instead of the latest tag.

@tOOmki
Copy link
Author

tOOmki commented Dec 4, 2024

This is what the command to update the LXC container looks like.

The update does not go through because there is no next version"
"✓ No update required. PeaNUT is already at v4.0.2"

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/peanut.sh)"

@Brandawg93
Copy link
Owner

Hm. That's above me. Maybe someone in that community could help more. I see where the script is getting the latest release version from GitHub and pulling that from docker. But that doesn't really make any sense considering you can just get tags from docker directly. Either way, I will probably just release the work on a new version soon. I don't think the changes could really hurt, only help.

@tOOmki
Copy link
Author

tOOmki commented Dec 4, 2024

They are working on selecting the appropriate branch or version. But when will it work???
community-scripts/ProxmoxVE#330

@Brandawg93
Copy link
Owner

Let me know if v4.1.0 works better for you.

@Brandawg93
Copy link
Owner

This should be fixed in the latest release (v4.2.0). Just let me know if it's still an issue for you.

@tOOmki
Copy link
Author

tOOmki commented Dec 8, 2024

I installed fresh version 4.2
The problem is recurring.

But I think I know why, in my case I have 3 NAS from Synology. I have a work schedule set, the moment the NAS is turned off the settings are cleared. It does not always happen and I do not know why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants