Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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]: Failed to set up listener: SocketException: Address already in use #380

Closed
stecydube opened this issue Dec 5, 2023 · 0 comments
Closed
Assignees

Comments

@stecydube
Copy link

Controller Version

5.13.22

Describe the Bug

Just updated container to 5.13.22, was working fine before.

Although the container seems to work since I can connect to the web interface, I get the same error in the logs over and over.

Expected Behavior

No error in the log ;)

Steps to Reproduce

Run the container

How You're Launching the Container

version: "3.1"

services:
  omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    network_mode: host
    environment:
      - PUID=1038
      - PGID=65543
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - PORT_APP_DISCOVERY=27001
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V1=29811
      - PORT_MANAGER_V2=29814
      - PORT_DISCOVERY=29810
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=America/Montreal
    volumes:
      - /volume1/docker/omada/data:/opt/tplink/EAPController/data
      - /volume1/docker/omada/logs:/opt/tplink/EAPController/logs

Container Logs

12-05-2023 14:22:16.739 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(): Mongo DB server started
12-05-2023 14:22:28.747 INFO [mongo-check-thread] [] c.t.s.o.s.OmadaBootstrap(): mongod was shutdown, restarting it
12-05-2023 14:22:28.747 ERROR [mongo-check-thread] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: An unexpected error occurred in MongoDb. Omada Controller will try to restart it.
12-05-2023 14:22:28.747 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(): Going to stop mongod which pid is 5411
12-05-2023 14:22:30.783 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(): mongodb process id is 5426
12-05-2023 14:22:30.783 ERROR [mongo-check-thread] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
1

MongoDB Logs

From mongod.log:

2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] MongoDB starting : pid=3939 port=27217 dbpath=../data/db 64-bit host=DiskStation
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] db version v3.6.8
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] git version: 8e540c0b6db93ce994cc548f000900bdc740f80a
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] allocator: tcmalloc
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] modules: none
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] build environment:
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten]     distarch: x86_64
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten]     target_arch: x86_64
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1", port: 27217 }, processManagement: { pidFilePath: "../data/mongo.pid" }, storage: { dbPath: "../data/db", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "../logs/mongod.log" } }
2023-12-05T14:03:03.193-0500 E STORAGE  [initandlisten] Failed to set up listener: SocketException: Address already in use
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] now exiting
2023-12-05T14:03:03.193-0500 I CONTROL  [initandlisten] shutting down with code:48

Additional Context

On synology.

Repository owner locked and limited conversation to collaborators Dec 6, 2023
@mbentley mbentley converted this issue into discussion #381 Dec 6, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants