Runtipi•2d ago

dependency failed to start: container runtipi-queue is unhealthyafter updating to 4.0.0

I tried updating to 4.0.0. I backed up my stuff first then ran the updater script. After that I tried to start runtipi but it errored out with that error. It pops-up everytime I try to start runtipi and tipi doesn't start. OS: Debian 12 I attached the logs of runtipi-queue container.

message.txt

25 Replies

Nicolas•21h ago

This is very weird, because all the logs show that the queue is starting correctly. A few step we can do: 1. Can you run ./runtipi-cli debug and paste the output? 2. Can you run sudo docker exec -it runtipi-queue rabbitmq-diagnostics -q ping do you see a success message? Was it long to respond? 3. Have you something interesting in logs/error.log? Other possible causes: 1. Have you enough disk space left on your device? 2. Is your server a low end device? Maybe the queue is not starting fast enough before the timeout

SkajmerOP•21h ago

message.txt

SkajmerOP•20h ago

2. Success, doesn't take long seems normal 3. The logs there are from before the update 1.1 Around 20-25gb free 2.2 It's low end, but not super low-end I've been running it since January with few containers and it's been doing fine so far

Nicolas•20h ago

If you do docker-compose up -d runtipi-queue does it starts correctly? You can check with docker ps if it is healthy What do you have in your user-config/tipi-compose.yml?

SkajmerOP•20h ago

docker-compose is not found as a command

services:
  runtipi-reverse-proxy:
    ports:
      - 8080:8080
    environment:
      - DYNU_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

services:
  runtipi-reverse-proxy:
    ports:
      - 8080:8080
    environment:
      - DYNU_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Nicolas•20h ago

Sorry docker compose up -d runtipi-queue

SkajmerOP•20h ago

sudo docker compose up -d runtipi-queue
[+] Running 1/1
 ✔ Container runtipi-queue  Running

sudo docker compose up -d runtipi-queue
[+] Running 1/1
 ✔ Container runtipi-queue  Running

and docker ps:

81b56593d59a   rabbitmq:4-alpine                                     "docker-entrypoint.s…"   16 minutes ago   Up 16 minutes (unhealthy)   4369/tcp, 5671-5672/tcp, 15691-15692/tcp, 25672/tcp

81b56593d59a   rabbitmq:4-alpine                                     "docker-entrypoint.s…"   16 minutes ago   Up 16 minutes (unhealthy)   4369/tcp, 5671-5672/tcp, 15691-15692/tcp, 25672/tcp

Nicolas•20h ago

Okay so the healthcheck has a problem. Can you try the following: In tipi-compose.yml

services:
  runtipi-reverse-proxy:
    ports:
      - 8080:8080
    environment:
      - DYNU_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  runtipi-queue:
    healthcheck:
      test: true
      interval: 5s
      timeout: 3s
      retries: 20
      start_period: 15s

services:
  runtipi-reverse-proxy:
    ports:
      - 8080:8080
    environment:
      - DYNU_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  runtipi-queue:
    healthcheck:
      test: true
      interval: 5s
      timeout: 3s
      retries: 20
      start_period: 15s

And then ./runtipi-cli start Oh and before doing this, can you run sudo docker inspect --format='{{json .State.Health}}' runtipi-queue ^ this will give us the reason why the healthcheck failed

SkajmerOP•20h ago

{"Status":"unhealthy","FailingStreak":80,"Log":[{"Start":"2025-05-01T08:46:01.738153497+02:00","End":"2025-05-01T08:46:04.913578058+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:09.915315432+02:00","End":"2025-05-01T08:46:13.084260557+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:18.086667418+02:00","End":"2025-05-01T08:46:21.252179971+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:26.254377942+02:00","End":"2025-05-01T08:46:29.43336011+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:34.434602199+02:00","End":"2025-05-01T08:46:37.611454358+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"}]}

{"Status":"unhealthy","FailingStreak":80,"Log":[{"Start":"2025-05-01T08:46:01.738153497+02:00","End":"2025-05-01T08:46:04.913578058+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:09.915315432+02:00","End":"2025-05-01T08:46:13.084260557+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:18.086667418+02:00","End":"2025-05-01T08:46:21.252179971+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:26.254377942+02:00","End":"2025-05-01T08:46:29.43336011+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"},{"Start":"2025-05-01T08:46:34.434602199+02:00","End":"2025-05-01T08:46:37.611454358+02:00","ExitCode":-1,"Output":"Health check exceeded timeout (3s)"}]}

Nicolas•20h ago

Okay good to know, so the container fails to responds before the 3s timeout

  runtipi-queue:
    healthcheck:
      test: rabbitmq-diagnostics -q ping
      interval: 5s
      timeout: 15s
      retries: 20
      start_period: 15s

  runtipi-queue:
    healthcheck:
      test: rabbitmq-diagnostics -q ping
      interval: 5s
      timeout: 15s
      retries: 20
      start_period: 15s

Increasing it could potentially resolve the issue

SkajmerOP•20h ago

It started successfully now That fixed it

Nicolas•20h ago

The increased timeout?

SkajmerOP•20h ago

Tipi is up but noone of the apps are

Nicolas•20h ago

Yes, after 4.0 the apps need to be started manually Because they have been migrated internally

SkajmerOP•20h ago

they can't start for some reason

Nicolas•20h ago

You get an error log? Okay maybe the queue is still not operational, let's dive more Did you keep the test: rabbitmq-diagnostics -q ping or just have put it to true?

SkajmerOP•20h ago

test: rabbitmq-diagnostics -q ping

Nicolas•20h ago

Okay then it should work for the queue. Now the apps fail to start. Do you have anything in logs/error.log?

SkajmerOP•20h ago

2025-05-01T06:54:41.457Z - error >     Failed to start app bazarr:migrated: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint bazarr_migrated-bazarr-1 (577ca15008954283f0e834ec27e51cb5d36daf1f13c968f044489dc7c94958c4): Bind for 0.0.0.0:6767 failed: port is already allocated

2025-05-01T06:54:41.457Z - error >     Failed to start app bazarr:migrated: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint bazarr_migrated-bazarr-1 (577ca15008954283f0e834ec27e51cb5d36daf1f13c968f044489dc7c94958c4): Bind for 0.0.0.0:6767 failed: port is already allocated

Theres a bunch more of these for all of them

Nicolas•20h ago

Oh okay, so this is a different issue it seems you have apps running on your host machine on the same ports. Did you stop all your apps before upgrading? Do you have for example the bazarr container still running?

SkajmerOP•20h ago

I stopped tipi before the upgrade. I see some running in docker ps.

Nicolas•20h ago

Okey so you had to stop the apps (the script should have done this and asked you to double check) This is not a problem, run for example docker stop bazarr and then you can start it from runtipi

SkajmerOP•20h ago

it's up so I just need to do that for everything else

ABOhiccups•20h ago

I have issues after updating to v4.0. All apps won’t start and it also won’t install. Fresh reinstall Runtipi won’t help for me. I was hoping you will get this resolve.

Nicolas•20h ago

Please open a new thread and send the required info Yes exactly, thanks for taking the time debugging I'll post a patch update for the timeout thing we have discovered

Gaming

Programming

dependency failed to start: container runtipi-queue is unhealthyafter updating to 4.0.0

Did you find this page helpful?