-
Notifications
You must be signed in to change notification settings - Fork 124
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]: Unable to restore config from backup #383
Comments
Thanks for the detailed report and the SO article! I appreciate the research and this one is easy to fix. |
Added JVM arg to allow restore to function; fixes #383
Revert "Added JVM arg to allow restore to function; fixes #383"
I had to revert this commit because it was breaking 32 bit arm due to it still being on Java 8. I don't have time to fix it right now properly but I will. @JesseWaas - you can override the CMD from the Docker image, setting it to: Which will give you the same functionality as the PR I had to revert. |
Signed-off-by: Matt Bentley <mbentley@mbentley.net>
Signed-off-by: Matt Bentley <mbentley@mbentley.net>
Added armv7l standalone Dockerfile; fixes #383
OK, this should actually be fixed in a way it doesn't break armv7l once the images build. |
Controller Version
v5.13.22
Describe the Bug
Hi, I have noticed that a "Restore failed" error seems to be thrown when attempting to import/restore config files using the controller software run from the v5.13.22 Docker image. The error occurs when attempting to restore a previously backed up config file during initial setup or later through the system settings > maintenance menu. The issue does not appear to affect a native install of v5.13.22 from TP-Link (I can import the same config file there without issue).
Interestingly the issue only seems to affect restoring config backups made with recent versions of the controller. I appear to be able to import a backup from v5.9.9 for example, but not v5.13.22.
I have attached a screenshot of the error messages and a related Omada server.log excerpt that includes some exception details:
java.lang.reflect.InaccessibleObjectException: Unable to make field private static final long java.util.LinkedHashMap.serialVersionUID accessible: module java.base does not "opens java.util" to unnamed module @5a6d67c3
omada_server_log_exrpt.txt
Expected Behavior
Config file should be restored without error.
Steps to Reproduce
(1) Deploy Omada controller using Docker image for v5.13.22.
(2) Complete minimal setup for local controller
(3) Navigate to
System Settings
>Maintenance
(4) Under the
Backup group
leave all settings at default (settings only, do not retain user info, export to local file) and select export(5) Under
Restore
leave all settings at default (import from local file, retain device info), browse to the backup file that was just made, and then clickRestore
(6) Observe that the restore operation fails (error condition described here).
How You're Launching the Container
Container Logs
MongoDB Logs
No response
Additional Context
Possibly related SO article: https://stackoverflow.com/questions/70756414/java-lang-reflect-inaccessibleobjectexception-unable-to-make-field-private-fina
The text was updated successfully, but these errors were encountered: