It seems like our instance of Taiga has stopped automatically refreshing for our users and I noticed that the taiga-events container shows a status of ‘exited.’ This has happened twice now. I am wondering if this is a known issue and if there is anything I can do to keep this from happening?
After re-launching taiga, I am having the same problem. Email notifications seem to have stopped working as well.
Hi @GroBot ,
There is no reported issue about this error. Can you share more information we us to find a solution? at least:
- taiga-docker repo version (you can use
git describe --all --long) - logs of the different services
- Have you recently upgraded or changed any values in the settings?
taiga-events is responsible for updating the activity in real time in the kanban and taskboards and taiga-async is responsible for sending emails and performing other tasks asynchronously. Both use the two rabbitmq services.
Best regarsds
1 Like
Thanks for your response, I am very new to this so I apologize if I am not getting you the right information.
git describe --all --long returns: tags/6.7.0-0-gf696137
The taiga-events container seems to be on the latest version. I have not changed anything since launching taiga about 3 weeks ago. After relaunching, it sent all email notifications that had not sent while taiga-events was down, but even now that taiga-events is up, it still requires a refresh of the page to show any new tasks.
I am not sure how to get logs of the different services.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8555a147e9a5 nginx:1.19-alpine "/docker-entrypoint.…" 3 weeks ago Up 3 weeks 0.0.0.0:9000->80/tcp, :::9000->80/tcp taiga-docker-taiga-gateway-1
a44927498c32 taigaio/taiga-back:latest "/taiga-back/docker/…" 3 weeks ago Up 18 hours 8000/tcp taiga-docker-taiga-async-1
84f85e5a8697 taigaio/taiga-back:latest "./docker/entrypoint…" 3 weeks ago Up 3 weeks 8000/tcp taiga-docker-taiga-back-1
05e94352b671 taigaio/taiga-events:latest "./docker/entrypoint…" 3 weeks ago Up 18 hours 8888/tcp taiga-docker-taiga-events-1
88b0dac59633 rabbitmq:3.8-management-alpine "docker-entrypoint.s…" 3 weeks ago Up 3 weeks (healthy) 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp taiga-docker-taiga-events-rabbitmq-1
17da76cadd42 rabbitmq:3.8-management-alpine "docker-entrypoint.s…" 3 weeks ago Up 3 weeks (healthy) 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp taiga-docker-taiga-async-rabbitmq-1
ba56b321bdba postgres:12.3 "docker-entrypoint.s…" 3 weeks ago Up 3 weeks (healthy) 5432/tcp taiga-docker-taiga-db-1
8d11a7b4938a taigaio/taiga-protected:latest "./docker/entrypoint…" 3 weeks ago Up 3 weeks 8003/tcp taiga-docker-taiga-protected-1
088658496d55 taigaio/taiga-front:latest "/docker-entrypoint.…" 3 weeks ago Up 3 weeks 80/tcp taiga-docker-taiga-front-1
Ok, To get logs from a service you can use docker compose logs <service_name>. You can find more options using docker compose logs --help or at docker compose logs | Docker Docs
With docker compose ps -a you can list all the services and see it current status.
$ docker compose ps -a
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
taiga-docker-taiga-async-1 taigaio/taiga-back:latest "/taiga-back/docker/…" taiga-async 33 hours ago Up 16 seconds 8000/tcp
taiga-docker-taiga-async-rabbitmq-1 rabbitmq:3.8-management-alpine "docker-entrypoint.s…" taiga-async-rabbitmq 33 hours ago Up 31 seconds (healthy) 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp
taiga-docker-taiga-back-1 taigaio/taiga-back:latest "./docker/entrypoint…" taiga-back 33 hours ago Up 16 seconds 8000/tcp
taiga-docker-taiga-db-1 postgres:12.3 "docker-entrypoint.s…" taiga-db 33 hours ago Up 31 seconds (healthy) 5432/tcp
taiga-docker-taiga-events-1 taigaio/taiga-events:latest "./docker/entrypoint…" taiga-events 33 hours ago Up 16 seconds 8888/tcp
taiga-docker-taiga-events-rabbitmq-1 rabbitmq:3.8-management-alpine "docker-entrypoint.s…" taiga-events-rabbitmq 33 hours ago Up 32 seconds (healthy) 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp
taiga-docker-taiga-front-1 taigaio/taiga-front:latest "/docker-entrypoint.…" taiga-front 33 hours ago Up 31 seconds 80/tcp
taiga-docker-taiga-gateway-1 nginx:1.19-alpine "/docker-entrypoint.…" taiga-gateway 33 hours ago Up 15 seconds 0.0.0.0:9000->80/tcp, :::9000->80/tcp
taiga-docker-taiga-protected-1 taigaio/taiga-protected:latest "./docker/entrypoint…" taiga-protected 33 hours ago Up 32 seconds 8003/tcp
The chrome dev tools just say that the frontend can’t connect with taiga events, but it could be because taiga-event is not working or because the address (192.168.3.226:9000) is wrong.
Hi again,
Here are the logs from taiga-events:
taiga-docker-taiga-events-1 | Starting Taiga events
taiga-docker-taiga-events-1 |
taiga-docker-taiga-events-1 |
taiga-docker-taiga-events-1 | > taigaio-events@6.7.0 start:production
taiga-docker-taiga-events-1 | > NODE_ENV=production node ./src/index.js
taiga-docker-taiga-events-1 |
taiga-docker-taiga-events-1 |
taiga-docker-taiga-events-1 | {"message":"WS server is started","level":"info","service":"taiga-events","timestamp": "2023-08-31 23:52:50"}
taiga-docker-taiga-events-1 | {"message":"Liveness / Readiness server was started in http://localhost:3023/healthz", "level":"info","service":"taiga-events","timestamp":"2023-08-31 23:52:50"}
taiga-docker-taiga-events-1 | {"message":"ws-connection-open: 04f1bf9f-ef7b-4230-ac5c-f112a2d76d3b","level":"info"," service":"taiga-events","timestamp":"2023-08-31 23:52:55"}
taiga-docker-taiga-events-1 | {"message":"auth: {\"cmd\":\"auth\",\"data\":{\"token\":\"eyJhbGciOiJIUzI1NiIsInR5cCI6 IkpXVCJ9.eyJ0b2tlbl90eXBlIjoiYWNjZXNzIiwiZXhwIjoxNjkzNjAxMTY2LCJqdGkiOiI1OWQwOWJlZWZhZTc0OGRhODAxNzM1YWVlNDE5ODNlOCIs InVzZXJfaWQiOjZ9.PFIHusag_P1ocrZ3r1mvrSuX3mHWf3DuTCnv9cAAAKM\",\"sessionId\":\"b5e9e2e3ad3c6eab3a63caaa7369bd59c98f72 a9\"}}","level":"info","service":"taiga-events","timestamp":"2023-08-31 23:52:55"}
taiga-docker-taiga-events-1 | {"message":"subscribe: {\"cmd\":\"subscribe\",\"routing_key\":\"notifications\"}","lev el":"info","service":"taiga-events","timestamp":"2023-08-31 23:52:55"}
taiga-docker-taiga-events-1 | {"message":"subscribe: {\"cmd\":\"subscribe\",\"routing_key\":\"web_notifications.6\"} ","level":"info","service":"taiga-events","timestamp":"2023-08-31 23:52:56"}
taiga-docker-taiga-events-1 | {"message":"Unhandled Rejection: \"Error: connect ECONNREFUSED 172.21.0.5:5672\"","lev el":"error","service":"taiga-events","timestamp":"2023-08-31 23:52:56"}
taiga-docker-taiga-events-1 | npm notice
taiga-docker-taiga-events-1 | npm notice New major version of npm available! 8.19.4 -> 10.0.0
taiga-docker-taiga-events-1 | npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.0.0>
taiga-docker-taiga-events-1 | npm notice Run `npm install -g npm@10.0.0` to update!
taiga-docker-taiga-events-1 | npm notice
taiga-docker-taiga-events-1 | {"message":"Unhandled Rejection: \"Error: connect ECONNREFUSED 172.21.0.5:5672\"","lev el":"error","service":"taiga-events","timestamp":"2023-08-31 23:52:56"}
It seems there is a configuration problem there, taiga-events is trying to connect to an ip that rabbitmq is not listening on.
What are your settings? Have you modified docker-compose.yml or just .env?
