Jump to content

mbentley

Members
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

 Content Type 

Posts posted by mbentley

    [Support] omada-controller

    in Docker Containers

    Posted

    6 hours ago, CyBuzz said:

    I just installed an update today and now the container wont start. I grabbed a screenshot of the logs but it closes out too quickly to catch much. I got this much in the screenshot. I tried to force an update but no luck.  Any pointers as to how to fix this?

     

    image.thumb.png.0dc537c6ba9322068af1ffe683baaa67.png

     

    I also caught this error when I restarted again.

     

    image.thumb.png.13e6b9391da58b9223d53e04fe93aeab.png

     

    Get container logs using:

    docker logs omada-controller >& output.log

     

    And mongodb logs using:

    docker cp omada-controller:/opt/tplink/EAPController/logs/mongod.log mongod.log

     

    Replace the container name if it is not omada-controller.

    [Support] omada-controller

    in Docker Containers

    Posted

    On 11/21/2023 at 8:36 AM, olco said:

    @mbentley

    Do I have to insert the name of my omada docker container or the name of my omada controller?

      

    docker inspect --format '{{json .Mounts}}' Omada-Controller
[{"Type":"volume","Name":"a13fa10908be8af6443af13b1d41a1a8ffa0fbd1f9fa8e98224ae985e83e679d","Source":"/var/lib/docker/volumes/a13fa10908be8af6443af13b1d41a1a8ffa0fbd1f9fa8e98224ae985e83e679d/_data","Destination":"/opt/tplink/EAPController/data","Driver":"local","Mode":"","RW":true,"Propagation":""},{"Type":"volume","Name":"9038ba554ee7b24e19c77106f41be5313d61031dff1c5d6ba64e149a24dc1a3f","Source":"/var/lib/docker/volumes/9038ba554ee7b24e19c77106f41be5313d61031dff1c5d6ba64e149a24dc1a3f/_data","Destination":"/opt/tplink/EAPController/logs","Driver":"local","Mode":"","RW":true,"Propagation":""}]

     

     

    Worked like a charm, thanks!

     

    Sorry, I missed the notification on this.  Based on these volume paths, you did not specify a volume name.  You can either use Docker managed volumes where you provide the persistent data path a name or you can use a bind mount.  The image is configured to automatically create a volume but if you do not specify a name, it will create one with a random guid.  In this case, your data is in the volume `a13fa10908be8af6443af13b1d41a1a8ffa0fbd1f9fa8e98224ae985e83e679d` and your logs are in `9038ba554ee7b24e19c77106f41be5313d61031dff1c5d6ba64e149a24dc1a3f` for this instance of your controller.  You probably have other volumes that show with `docker volume ls` but you won't be able to tell what is what without manually inspecting the contents in `/var/lib/docker/volumes/<volume_guid>/_data`.

    [Support] omada-controller

    in Docker Containers

    Posted

    11 hours ago, olco said:

    I can see a folder for each of my docker containers in /mnt/user/appdata but none for the omada-controller.

     

    Settings > Docker shows me Default appdata storage location: /mnt/user/appdata/

     

    The data of the running omada controller docker has to be somewhere..

     

    Edit:

    I can only find one folder including the term "omada".

    Screenshot_20231120_001811_Termius.thumb.jpg.e4394001c0bfe2ba07f8c4c4773f940f.jpg

    If you don't know where the container is mounted the data, you can use docker inspect to find out:

     

    This just lists the mounts:

      

    # docker inspect omada-controller | jq '.[]|.Mounts'
[
  {
    "Type": "bind",
    "Source": "/zfs/apps/omada-controller/cert",
    "Destination": "/cert",
    "Mode": "",
    "RW": false,
    "Propagation": "rprivate"
  },
  {
    "Type": "bind",
    "Source": "/zfs/apps/omada-controller/data",
    "Destination": "/opt/tplink/EAPController/data",
    "Mode": "",
    "RW": true,
    "Propagation": "rprivate"
  },
  {
    "Type": "bind",
    "Source": "/zfs/apps/omada-controller/logs",
    "Destination": "/opt/tplink/EAPController/logs",
    "Mode": "",
    "RW": true,
    "Propagation": "rprivate"
  }
]

     

    Or if you don't have jq:

      

    # docker inspect --format '{{json .Mounts}}' omada-controller
[{"Type":"bind","Source":"/zfs/apps/omada-controller/data","Destination":"/opt/tplink/EAPController/data","Mode":"","RW":true,"Propagation":"rprivate"},{"Type":"bind","Source":"/zfs/apps/omada-controller/logs","Destination":"/opt/tplink/EAPController/logs","Mode":"","RW":true,"Propagation":"rprivate"},{"Type":"bind","Source":"/zfs/apps/omada-controller/cert","Destination":"/cert","Mode":"","RW":false,"Propagation":"rprivate"}]

     

    [Support] omada-controller

    in Docker Containers

    Posted · Edited by mbentley

    14 hours ago, LotF said:

    I updated this morning and just get a page for starting a new configuration when tryin to login to the Controller. Seems like for me all settings are still vanished. Haven't tried to set it up and load a saved config yet. Might work that way, still something is wrong with the update, I believe.

     

    EDIT: Even when I load a backup all the devices state "managed by others" and would have to be adapted again :(

     

    Sounds like you did not map your persistent data to a volume or a bind mounted location.

    [Support] omada-controller

    in Docker Containers

    Posted

    Sorry about that - an issue with a new experimental feature to allow users to make the MongoDB work from another container or host accidentally broke the connection to the MongoDB that the controller spins up.  I forgot to add a default connection string but it should be fixed now.

    • Thanks 2

    [Support] omada-controller

    in Docker Containers

    Posted

    4 hours ago, ibphantom said:

    The container is broken for me

     

    "

    text  error  warn  system  array  login  

    tar: html/Omada.png: Cannot write: No space left on device
    tar: html/echarts.min.js: Cannot write: No space left on device
    tar: html/logo.png: Cannot write: No space left on device
    tar: Exiting with failure status due to previous errors
    /entrypoint.sh: line 301: echo: write error: No space left on device
    INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
    INFO: Group (omada) doesn't exist; creating
    INFO: User (omada) doesn't exist; creating
    INFO: Time zone set to 'America/Los_Angeles'
    INFO: Setting 'manage.http.port' to 18088 in omada.properties
    INFO: Setting 'manage.https.port' to 18043 in omada.properties
    INFO: Setting 'portal.http.port' to 18088 in omada.properties
    INFO: Setting 'portal.https.port' to 18843 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: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html'
    html/
    html/Omada.png
    html/echarts.min.js
    html/logo.png
    INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
    INFO: Group (omada) exists; skipping creation
    INFO: User (omada) exists; skipping creation
    INFO: Time zone set to 'America/Los_Angeles'
    INFO: Value of 'manage.http.port' already set to 18088 in omada.properties
    INFO: Value of 'manage.https.port' already set to 18043 in omada.properties
    INFO: Value of 'portal.http.port' already set to 18088 in omada.properties
    INFO: Value of 'portal.https.port' already set to 18843 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: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf'
    WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada)
    WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada)
    WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
    INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db'
    done
    INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file...

    text  error  warn  system  array  login  

    tar: html/Omada.png: Cannot write: No space left on device
    tar: html/echarts.min.js: Cannot write: No space left on device
    tar: html/logo.png: Cannot write: No space left on device
    tar: Exiting with failure status due to previous errors
    /entrypoint.sh: line 301: echo: write error: No space left on device
    INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
    INFO: Group (omada) doesn't exist; creating
    INFO: User (omada) doesn't exist; creating
    INFO: Time zone set to 'America/Los_Angeles'
    INFO: Setting 'manage.http.port' to 18088 in omada.properties
    INFO: Setting 'manage.https.port' to 18043 in omada.properties
    INFO: Setting 'portal.http.port' to 18088 in omada.properties
    INFO: Setting 'portal.https.port' to 18843 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: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html'
    html/
    html/Omada.png
    html/echarts.min.js
    html/logo.png
    INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
    INFO: Group (omada) exists; skipping creation
    INFO: User (omada) exists; skipping creation
    INFO: Time zone set to 'America/Los_Angeles'
    INFO: Value of 'manage.http.port' already set to 18088 in omada.properties
    INFO: Value of 'manage.https.port' already set to 18043 in omada.properties
    INFO: Value of 'portal.http.port' already set to 18088 in omada.properties
    INFO: Value of 'portal.https.port' already set to 18843 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: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf'
    WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada)
    WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada)
    WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
    INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db'
    done
    INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file...

     You’re out of disk space wherever it is trying to write to. Errors specifically call that out.

    • Upvote 1

    [Support] omada-controller

    in Docker Containers

    Posted · Edited by mbentley

    20 hours ago, LotF said:

    Since an update today I cannot log into the controller anymore. Does anybody else have that problem? I am very sure that I am using the correct credentials.

     

    Yes, others are reporting the same.  I created an issue on the TP-Link forums: https://community.tp-link.com/en/business/forum/topic/623942?replyId=1258164 and there is a discussion tracking it on the image GitHub: https://github.com/mbentley/docker-omada-controller/issues/342.  People are also posting about it on Reddit: https://www.reddit.com/r/TPLink_Omada/comments/16rb07h/admin_login_doesnt_work_after_updating_to_latest/

     

    It doesn't seem to be happening to everyone though so that's the odd part.

     

    [Support] omada-controller

    in Docker Containers

    Posted · Edited by mbentley
    link didn't work

    On 7/26/2023 at 10:19 PM, taprackpew said:

    they are the default values of 18043 for https and 18088 for http.  when I click the webui button it opens https://192.168.10.5:18043/login , which is correct.  however, I get a "cannot connect to server" error page.  its odd for sure as all of my other apps are perfectly accessible.

     

    I am not as familiar with the interface for starting a container but just make sure that the ports exposed AND the environment variables that you used to launch the container match.  If you have previously launched the container with different ports, you can't just change them due to how the controller software is written.  Take a look at this part of the readme if you want to fully understand but the env vars modify a properties file which is only read on the very first startup by default.

    [Support] omada-controller

    in Docker Containers

    Posted

    Hey all - I'm the Docker image author.  If people are having specific issues with the image not running or unexpected errors, I can help but would appreciate issues being posted to GitHub.

     

    @hedrinbc - No idea where or how the container image is published to the marketplace but there may be an update needed to change how the container is run as it looks like some people are hitting ulimits as you can see here: https://github.com/mbentley/docker-omada-controller/issues/298#issuecomment-1491937963

     

    This would be a change to how the run command is defined assuming it uses docker run type parameters.

    • Like 1
    • Thanks 1
    • Upvote 2
×
×
  • Create New...