[Help]: Install fails with "main ERROR Unable to locate appender "RollingFile" for logger config..." #607
Answered
by
Mignor-Fints
Mignor-Fints
asked this question in
Help
[Help]: Install fails with "main ERROR Unable to locate appender "RollingFile" for logger config..."
#607
Replies: 6 comments 2 replies
-
|
The output around here makes it seem like despite setting the permissions, it's not able to write to the persistent data directory which is probably a leading indicator of some sort of issue there: I ran your same docker command and the controller started up fine. Do you know anything about the volume mount filesystem that you're using at I don't see it complain when the entrypoint is setting permissions which is interesting. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks, Matt.
I am running this Docker on a Synology DS218+ running DSM 7.2.2-72806 (latest, I believe)
As for Volume 1, it is a Synology Hybrid RAID Storage Pool. The Docker folder on Volume1 has the following permissions configured.
ContainierManager RW
administrators RW
Everyone R
What is worth noting is that if I run any version (from 4.4 up) of your image I get the same errors, but if I run the edofede\omada-eap-controller package, it successfully builds and starts. The issue there is that it is v4.4 of Omada and that is too old for the version of one of my EAPs. Unfortunately, Omada advises that it is not possible to backport the EAP firmware form the version latest version.
…-Chris (Kit) Carda
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Unfortunately I have no idea what those permissions mean as I do not have Synology devices and I do not know what filesystem a The entrypoint is able to copy over files from the container just fine as root as you can see at the very beginning so I am almost certain you're seeing permissions issues. Google took me to: https://kb.synology.com/vi-vn/DSM/tutorial/Docker_container_cant_access_the_folder_or_file so check that out for how to manage permissions. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Matt,
Appreciate the help.
And sorry for any confusion, my Linux skills are a bit rusty to say the least.
The file system for Volume 1 is BTRFS.
/etc/fstab shows the following:
none /proc proc defaults 0 0
/dev/root / ext4 defaults 1 1
/dev/vg1000/lv /volume1 btrfs auto_reclaim_space,ssd,synoacl,noatime,nodev 0 0
Does this help?
…-Chris (Kit) Carda
On Sep 4 2025, at 9:06 AM, Matt Bentley ***@***.***> wrote:
Unfortunately I have no idea what those permissions mean as I do not have Synology devices and I do not know what filesystem a
Synology Hybrid RAID Storage Pool
is. It could be that the other container is running as root which would be one reason why it would work but your container is running as
user:group
of
1026:100
so if Synology is doing something related to the permissions and it's not mapping to that UID and/or GID, that could be why.
—
Reply to this email directly, view it on GitHub (#607 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/BW4SCZUANTL7TOHNH2W7YD33RA2MLAVCNFSM6AAAAACFRVKGSGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZQG42TENA).
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Addiitonally, MOunt shows the following for Docker:
/dev/mapper/vg1000-lv on ***@***.*** type btrfs ***@***.***)
/dev/mapper/vg1000-lv on ***@***.***/btrfs type btrfs ***@***.***)
/dev/mapper/vg1000-lv on ***@***.***/ContainerManager/all_shares/docker type btrfs ***@***.***/docker)
/dev/mapper/vg1000-lv on ***@***.***/ContainerManager/all_shares/family type btrfs ***@***.***/family)
/dev/mapper/vg1000-lv on ***@***.***/ContainerManager/all_shares/homes type btrfs ***@***.***/homes)
/dev/mapper/vg1000-lv on ***@***.***/ContainerManager/all_shares/music type btrfs ***@***.***/music)
/dev/mapper/vg1000-lv on ***@***.***/ContainerManager/all_shares/photo type btrfs ***@***.***/photo)
/dev/mapper/vg1000-lv on ***@***.***/ContainerManager/all_shares/video type btrfs ***@***.***/video)
nsfs on /run/docker/netns/default type nsfs (rw)
Hope this helps.
…-Chris (Kit) Carda
On Sep 4 2025, at 9:13 AM, ***@***.*** wrote:
Hi Matt,
Appreciate the help.
And sorry for any confusion, my Linux skills are a bit rusty to say the least.
The file system for Volume 1 is BTRFS.
/etc/fstab shows the following:
none /proc proc defaults 0 0
/dev/root / ext4 defaults 1 1
/dev/vg1000/lv /volume1 btrfs auto_reclaim_space,ssd,synoacl,noatime,nodev 0 0
Does this help?
-Chris (Kit) Carda
On Sep 4 2025, at 9:06 AM, Matt Bentley ***@***.***> wrote:
>
>
>
> Unfortunately I have no idea what those permissions mean as I do not have Synology devices and I do not know what filesystem a
>
>
>
>
>
>
>
>
> Synology Hybrid RAID Storage Pool
>
>
>
>
>
>
>
>
> is. It could be that the other container is running as root which would be one reason why it would work but your container is running as
>
>
>
>
>
>
>
>
> user:group
>
>
>
>
>
>
>
>
> of
>
>
>
>
>
>
>
>
> 1026:100
>
>
>
>
>
>
>
>
> so if Synology is doing something related to the permissions and it's not mapping to that UID and/or GID, that could be why.
>
>
>
> —
>
> Reply to this email directly, view it on GitHub (#607 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/BW4SCZUANTL7TOHNH2W7YD33RA2MLAVCNFSM6AAAAACFRVKGSGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZQG42TENA).
>
> You are receiving this because you authored the thread.
>
>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
OK, just making sure that the volume mount path doesn't have a filesystem that does not support linux permissions properly. Everything looks fine from a mount perspective so it's not the filesystem or how it's mounted. I still expect it's a problem with the permissions. Can you give me the output of the following commands:
We might have to take a look if there are ACLs applied to the directories but this should give me enough info to get an idea of where the problem could be. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Matt,
I can do that, but after our last exchange, I had a thought and went into my file manager (File Station) and set permissions to the Docker folder to RW for the "users" group.
After that I tried running a build using Docker Compose from the CLI (Putty). That worked and I successfully launched the controller.
I then deleted that container and reran the original Scheduled Task script and that also worked. (The scheduled task runs as root, but I noticed that your build appears to run in the context of the omada user (PUID 508) thus the thought about changing permissions for the "users" group from R to RW for the Docker folder.
Maybe this willbe useful for someone else down the road.
…-Chris (Kit) Carda
On Sep 4 2025, at 10:11 AM, Matt Bentley ***@***.***> wrote:
OK, just making sure that the volume mount path doesn't have a filesystem that does not support linux permissions properly. Everything looks fine from a mount perspective so it's not the filesystem or how it's mounted.
I still expect it's a problem with the permissions. Can you give me the output of the following commands:
Take a look at the filesystem from Synology:
ls -lan /volume1/docker/omada/data
and
ls -lan /volume1/docker/omada/logs
from the CLI of Synology
Take a look at the filesystem from inside the container:
docker exec -it omada-controller ls -lan /opt/tplink/EAPController/data
and
docker exec -it omada-controller ls -lan /opt/tplink/EAPController/logs
Try to touch a file in the container's volume paths while the container is running:
docker exec -it -u 1026:100 omada-controller touch /opt/tplink/EAPController/data/touchtest
and
docker exec -it -u 1026:100 omada-controller touch /opt/tplink/EAPController/logs/touchtest
We might have to take a look if there are ACLs applied to the directories but this should give me enough info to get an idea of where the problem could be.
—
Reply to this email directly, view it on GitHub (#607 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/BW4SCZSZYAKZFQ5U6SIEXIL3RBCAFAVCNFSM6AAAAACFRVKGSGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZQHAZDMNY).
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Good deal, glad that you were able to get it working. I wasn't sure what the mapping was for the users and groups on the Synology permissions but |
Beta Was this translation helpful? Give feedback.
Answer selected by
mbentley
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Controller Version
5.15.24.19
Describe Your Issue or Question
Following the "How to Install TP-Link Omada Controller on Your Synology NAS" the scheduled task completes successfully but the controller cannot be accessed through either port 8088 or 8043. THe container log ends with "main ERROR Unable to locate appender "RollingFile" for logger config..." and the container is only able to stay up for 4 mins max.
Expected Behavior
Expect the controller to launch.
Steps to Reproduce
1' Follow the steps outlined in the this guide:
https://mariushosting.com/how-to-install-tp-link-omada-controller-on-your-synology-nas/
How You're Launching the Container
Container Logs
MongoDB Logs
No response
Additional Context
Omada-Controller json:
{
"CapAdd" : null,
"CapDrop" : null,
"cmd" : "java -server -Xms128m -Xmx1024m -XX:MaxHeapFreeRatio=60 -XX:MinHeapFreeRatio=30 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/tplink/EAPController/logs/java_heapdump.hprof -Djava.awt.headless=true --add-opens java.base/sun.security.x509=ALL-UNNAMED --add-opens java.base/sun.security.util=ALL-UNNAMED -cp /opt/tplink/EAPController/lib/::/opt/tplink/EAPController/properties: com.tplink.smb.omada.starter.OmadaLinuxMain",
"cmd_v2" : "java -server -Xms128m -Xmx1024m -XX:MaxHeapFreeRatio=60 -XX:MinHeapFreeRatio=30 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/tplink/EAPController/logs/java_heapdump.hprof -Djava.awt.headless=true --add-opens java.base/sun.security.x509=ALL-UNNAMED --add-opens java.base/sun.security.util=ALL-UNNAMED -cp /opt/tplink/EAPController/lib/::/opt/tplink/EAPController/properties: com.tplink.smb.omada.starter.OmadaLinuxMain",
"cpu_priority" : 0,
"enable_publish_all_ports" : false,
"enable_restart_policy" : true,
"enabled" : false,
"env_variables" : [
{
"key" : "TZ",
"value" : "America/New_York"
},
{
"key" : "MANAGE_HTTPS_PORT",
"value" : "8043"
},
{
"key" : "PORTAL_HTTPS_PORT",
"value" : "8043"
},
{
"key" : "SSL_CERT_NAME",
"value" : "tls.crt"
},
{
"key" : "SSL_KEY_NAME",
"value" : "tls.key"
},
{
"key" : "PUID",
"value" : "1026"
},
{
"key" : "PGID",
"value" : "100"
},
{
"key" : "MANAGE_HTTP_PORT",
"value" : "8088"
},
{
"key" : "PORTAL_HTTP_PORT",
"value" : "8088"
},
{
"key" : "SHOW_SERVER_LOGS",
"value" : "true"
},
{
"key" : "SHOW_MONGODB_LOGS",
"value" : "false"
},
{
"key" : "PATH",
"value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
}
],
"exporting" : false,
"id" : "fd69c713f750287dae4850b45431c16fc2e5612573c4c333245c6b1733edb644",
"image" : "mbentley/omada-controller",
"is_ddsm" : false,
"is_package" : false,
"labels" : {
"maintainer" : "Matt Bentley [email protected]",
"org.opencontainers.image.source" : "https://github.com/mbentley/docker-omada-controller"
},
"links" : [],
"memory_limit" : 0,
"name" : "omada-controller",
"network" : [
{
"driver" : "host",
"name" : "host"
}
],
"network_mode" : "host",
"port_bindings" : [],
"privileged" : false,
"shortcut" : {
"enable_shortcut" : false,
"enable_status_page" : false,
"enable_web_page" : false,
"web_page_url" : ""
},
"use_host_network" : true,
"version" : 2,
"volume_bindings" : [
{
"host_volume_file" : "/docker/omada/data",
"is_directory" : true,
"mount_point" : "/opt/tplink/EAPController/data",
"type" : "rw"
},
{
"host_volume_file" : "/docker/omada/logs",
"is_directory" : true,
"mount_point" : "/opt/tplink/EAPController/logs",
"type" : "rw"
}
]
}
Beta Was this translation helpful? Give feedback.
All reactions