[Help]: New Container won't boot up in QNAP Docker

[mcor77]

Controller Version

5.13.30.8

Describe Your Issue or Question

So I've been trying to launch (for the first time, never had Omada software before) the software on a docker instance on my QNAP HS-251

I'm getting the error:

tail: cannot open '/opt/tplink/EAPController/logs/server.log' for reading: No such file or directory Error: Could not find or load main class com.tplink.smb.omada.starter.OmadaLinuxMain Caused by: java.lang.ClassNotFoundException: com.tplink.smb.omada.starter.OmadaLinuxMain

With some googling, it seems my CMD was incorrect...but no. This is the CMD I'm using

/usr/bin/java -server -Xms128m -Xmx512m -XX:MaxHeapFreeRatio=60 -XX:MinHeapFreeRatio=30 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/tplink/EAPController/logs/java_heapdump.hprof -Djava.awt.headless=true -cp /opt/tplink/EAPController/lib/*::/opt/tplink/EAPController/properties: com.tplink.smb.omada.starter.OmadaLinuxMain
(I changed the Xmx to 512 as I only have 1GB ram on this QNAP)

My bindings are:

/share/CACHEDEV1_DATA/dockerappdata/omadaconfig/data - /opt/tplink/EAPController/data /share/CACHEDEV1_DATA/dockerappdata/omadaconfig/logs -/opt/tplink/EAPController/logs /share/CACHEDEV1_DATA/dockerappdata/omadaconfig/work -/opt/tplink/EAPController/work

Environment variables:

    - MANAGE_HTTP_PORT=8088 
    - MANAGE_HTTPS_PORT=8043 
    - PGID=100
    - PORTAL_HTTP_PORT=8088 
    - PORTAL_HTTPS_PORT=8043 
    - PUID=100 
    - SHOW_SERVER_LOGS=true 
    - SHOW_MONGODB_LOGS=false 
    - SSL_CERT_NAME=tls.crt 
    - SSL_KEY_NAME=tls.key 
    - TZ=Australia/Melbourne

This is a brand new container that I've stopped and started and recreated several times with no change :(

Expected Behavior

Container launches

Steps to Reproduce

1. I start the container using either Portainer or Container Station
2. Errors

How You're Launching the Container

Launching using Portainer and Container Station using CMD stated above

Container Logs

INFO: Validating user/group (omada:omada) exists with correct UID/GID (100:100)
INFO: Group (omada) already exists with a different name; renaming 'users' to 'omada'
INFO: User (omada) already exists with a different name; renaming '_apt' to 'omada'
INFO: Time zone set to 'Australia/Melbourne'
INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
INFO: Setting 'portal.https.port' to 8043 in omada.properties
INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
INFO: Value of 'port.discovery' already set to 29810 in omada.properties
INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
INFO: Value of 'port.rtty' already set to 29816 in omada.properties
INFO: Value of 'mongo.external' already set to false in omada.properties
INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
INFO: Version check passed; image version (5.13.30.8) >= the last version ran (5.13.30.8); writing image version to last ran file...
INFO: userland/kernel check passed
INFO: Starting Omada Controller as user omada
tail: cannot open '/opt/tplink/EAPController/logs/server.log' for reading: No such file or directory
Error: Could not find or load main class com.tplink.smb.omada.starter.OmadaLinuxMain
Caused by: java.lang.ClassNotFoundException: com.tplink.smb.omada.starter.OmadaLinuxMain
INFO: Validating user/group (omada:omada) exists with correct UID/GID (100:100)
INFO: Group (omada) exists; skipping creation
INFO: User (omada) exists; skipping creation
INFO: Time zone set to 'Australia/Melbourne'
INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
INFO: Value of 'portal.https.port' already set to 8043 in omada.properties
INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
INFO: Value of 'port.discovery' already set to 29810 in omada.properties
INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
INFO: Value of 'port.rtty' already set to 29816 in omada.properties
INFO: Value of 'mongo.external' already set to false in omada.properties
INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
INFO: Version check passed; image version (5.13.30.8) >= the last version ran (5.13.30.8); writing image version to last ran file...
INFO: userland/kernel check passed
INFO: Starting Omada Controller as user omada
tail: cannot open '/opt/tplink/EAPController/logs/server.log' for reading: No such file or directory
Error: Could not find or load main class com.tplink.smb.omada.starter.OmadaLinuxMain
Caused by: java.lang.ClassNotFoundException: com.tplink.smb.omada.starter.OmadaLinuxMain
INFO: Validating user/group (omada:omada) exists with correct UID/GID (100:100)
INFO: Group (omada) exists; skipping creation
INFO: User (omada) exists; skipping creation
INFO: Time zone set to 'Australia/Melbourne'
INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
INFO: Value of 'portal.https.port' already set to 8043 in omada.properties
INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
INFO: Value of 'port.discovery' already set to 29810 in omada.properties
INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
INFO: Value of 'port.rtty' already set to 29816 in omada.properties
INFO: Value of 'mongo.external' already set to false in omada.properties
INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
INFO: Version check passed; image version (5.13.30.8) >= the last version ran (5.13.30.8); writing image version to last ran file...
INFO: userland/kernel check passed
INFO: Starting Omada Controller as user omada
tail: cannot open '/opt/tplink/EAPController/logs/server.log' for reading: No such file or directory

MongoDB Logs

No response

Additional Context

No response

[mbentley]

Could you provide the full compose file for how you're launching the container? It looks like you're using a compose file based on the syntax your provided but it seems like there is something wrong with your formatting or the syntax used in your compose file, most likely specific to the command line.

Anyway, I would expect your command line of your compose file to look like this:

command: ["/usr/bin/java","-server","-Xms128m","-Xmx512m","-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/java.util=ALL-UNNAMED","-cp","/opt/tplink/EAPController/lib/*::/opt/tplink/EAPController/properties:","com.tplink.smb.omada.starter.OmadaLinuxMain"]

You should use this list syntax because it will escape the * which I could easily see getting parsed before sent to the container.

[mbentley]

Hmm, I would think that QNAP would just be based on a certain version of Linux and that you might be able to manually update the package repo and install it manually. What does cat /etc/os-release show?

[mcor77]

I’ll take a look tomorrow as I’m actually about to go bed.
Thanks so much for your help so far! Not only have you helped with the Omada package, you’ve really made me realise this NAS really should be thrown out…
(Other open source NAS distros can’t even be installed, they need way more than 1GB RAM!)

[mbentley]

You bet, happy to help.

[mcor77]

This is the output to cat /etc/os-release
NAME="QTS"
VERSION="4.3.6 (20240131)"
ID=qts
PRETTY_NAME="QTS 4.3.6 (20240131)"
VERSION_ID="4.3.6"

[mbentley]

Ah ok so if it is based on something else, they’ve replaced that metadata.