Docker w/ POE Controller Serial Timeout Fails to Restart

[efaden]

I am running ZWave JS UI in a docker container within an Ubuntu VM on Proxmox. The controller is a TubesZB ZWave controller with the Zooz module installed. It seems to work fine for a time and then for some unknown reason ZWave JS UI exits with the error "Serial port errored: read ETIMEOUT". This causes ZWave JS UI to crash. So that's issue number one... I'm not sure why it gets a read timeout. Issue number two is that when the docker goes to restart it gives

08:33:46.184 DRIVER   Failed to initialize the driver: Error: Failed to lock DB file "/usr/src/app/s
                      tore/d699b88c.jsonl"!
                          at JsonlDB.open (/usr/src/app/node_modules/@alcalzone/jsonl-db/src/lib/db.
                      ts:407:10)
                          at Driver.initNetworkCache (/usr/src/app/node_modules/zwave-js/src/lib/dri
                      ver/Driver.ts:1559:3)
                          at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                      /src/lib/driver/Driver.ts:1709:4)
                          at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive
                      r/Driver.ts:1466:5)

So it seems that when the crash occurs due to the time out it isn't releasing the lock file. Manually killing, removing, and restarting the docker seems to be required to get it to come back up.

Any suggestions?

[robertsLando]

Could you share your docker-compose.yml file or the docker command you are using to start zui?

[efaden]

Sorry for the delay.

services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    tty: true
    stop_signal: SIGINT
    env_file: .env
    environment:
      - SESSION_SECRET
      - TZ
    networks:
      - traefik_default
    volumes:
      - ./data:/usr/src/app/store
    # Or by using local folder
    # - ./store:/usr/src/app/store
    healthcheck:
      test: 'wget --no-verbose --spider --no-check-certificate --header "Accept:
        text/plain" http://localhost:8091/health || exit 1'
      interval: 1m
      timeout: 10s
      start_period: 30s
      retries: 3
      #ports: null
      # - 8091:8091 # port for web interface
      # - 3000:3000 # port for Z-Wave JS websocket server
    labels:
      - traefik.enable=true
      - traefik.http.routers.zwavejsui.entrypoints=https-internal
      - traefik.http.routers.zwavejsui.rule=Host(`zwavejsui.<DOMAIN>`)
      - traefik.http.routers.zwavejsui.middlewares=internal-chain@file
      - traefik.http.routers.zwavejsui.tls=true
      - traefik.http.routers.zwavejsui.service=zwavejsui
      - traefik.http.services.zwavejsui.loadbalancer.server.port=8091
      - traefik.http.routers.zwavejsui-ws.entrypoints=https-internal
      - traefik.http.routers.zwavejsui-ws.rule=Host(`zwavejsui-ws.<DOMAIN>`)
      - traefik.http.routers.zwavejsui-ws.middlewares=internal-chain@file
      - traefik.http.routers.zwavejsui-ws.service=zwavejsui-ws
      - traefik.http.services.zwavejsui-ws.loadbalancer.server.port=3000
networks:
  traefik_default:
    external: true

[robertsLando]

This may be an issue with the VM setup as your docker-compose file looks good. I think this is not the first time I heard this, @AlCalzone what do you think?

[efaden]

It's just a generic Ubuntu... I suppose I could try swapping to an LXC or something else if you want me to test another setup....

…

On Fri, Dec 27, 2024, 03:39 Daniel Lando ***@***.***> wrote: This may be an issue with the VM setup as your docker-compose file looks good. I think this is not the first time I heard this, @AlCalzone <https://github.com/AlCalzone> what do you think? — Reply to this email directly, view it on GitHub <#4069 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAEABBVRO4PR76BWENZDCD2HUG2XAVCNFSM6AAAAABT7NSETOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRXGU4TOMQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[AlCalzone]

@efaden do you happen to have logs that include the Serial port errored: read ETIMEOUT error and possibly a stack trace?

[efaden]

Unfortunately not. It was driving me nuts so I switched back to a USB controller. I can try to go grab logs. How do I get what you need? The issue was that it was completely sporadic.

…

On Tue, Jan 14, 2025 at 5:50 AM AlCalzone ***@***.***> wrote: @efaden <https://github.com/efaden> do you happen to have logs that include the Serial port errored: read ETIMEOUT error and possibly a stack trace? — Reply to this email directly, view it on GitHub <#4069 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAEABDRD2A627MP47SWBFD2KTTXNAVCNFSM6AAAAABT7NSETOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBTGAZTKNQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AlCalzone]

I suppose from the logs you originally found the error in. Not sure if you can reproduce it somehow, e.g. by pulling the ethernet cable or so.

[efaden]

Sorry. Just haven't had a chance. Work schedule has sucked. I'll see if I can get to it this weekend. -Eric

…

On Wed, Jan 15, 2025 at 8:44 AM AlCalzone ***@***.***> wrote: I suppose from the logs you originally found the error in. Not sure if you can reproduce it somehow, e.g. by pulling the ethernet cable or so. — Reply to this email directly, view it on GitHub <#4069 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAEABHTZKOL7B335UKEZND2KZQ5HAVCNFSM6AAAAABT7NSETOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBUGMZTENQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>