-
Notifications
You must be signed in to change notification settings - Fork 19
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
REM seems to have lost its config #52
Comments
The entire setup is in the data directory. All configuration is located in the controllerConfig.json file. |
I restored the file from my backup. It all seems to be working now. Do you know what would cause this file to be reset back to initial install?
Eric
From: rstrouse ***@***.***>
Reply-To: rstrouse/relayEquipmentManager ***@***.***>
Date: Monday, August 21, 2023 at 8:27 AM
To: rstrouse/relayEquipmentManager ***@***.***>
Cc: Eric Repec ***@***.***>, Author ***@***.***>
Subject: Re: [rstrouse/relayEquipmentManager] REM seems to have lost its config (Issue #52)
The entire setup is in the data directory. All configuration is located in the controllerConfig.json file.
—
Reply to this email directly, view it on GitHub<#52 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALHS65LLT762X2VJDI3QMSTXWN46ZANCNFSM6AAAAAA3XQVPHQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I have seen this once before. The cause for this was related to power. |
Yes, I have had some power issues. |
I wanted to add another data point that I have experienced this same issue - total data/config loss as a result of power loss - on 2 separate occasions. Now that I am aware of the issue (and have backups in place) - recovering is relatively painless, but is still a pain nonetheless. |
Not sure what caused it, but today several components on my Nixe pool controller stopped working. I have narrowed it down to the REM and it does not seem to be configured any longer. I have some backups of the directories, but not sure what director the configuration was in.
The text was updated successfully, but these errors were encountered: