Cannot invite new member in project

Troubleshooting
1

Hi!
I’ve just installed self managed instance with external database. Successfully tested with ./taiga-manage.sh sample_data and received sample emails. But when I tried to add new member in sample project or my new created project, nothing happened - I dont see new pending user in the list and dont receive any invitation emails.

I tried to create member using API endpoint /api/v1/memberships - received 502 (Bad gateway), member appeared in the list as “pending” but still no email.

./taiga-manage.sh test_emails sumarokov.vp@gmail.com

this test worked fine - received many emails including some sample invitations emails

2 
docker container logs taiga-docker-taiga-back-1

Executing pending migrations
Operations to perform:
  Apply all migrations: admin, attachments, auth, bitbucket, contact, contenttypes, custom_attributes, djmail, easy_thumbnails, epics, external_apps, feedback, github, gitlab, gogs, history, issues, likes, milestones, notifications, projects, references, sessions, settings, tasks, telemetry, timeline, token_denylist, users, userstorage, userstories, votes, webhooks, wiki
Running migrations:
  No migrations to apply.
Load default templates
Installed 2 object(s) from 1 fixture(s)
Give permission to taiga:taiga
Starting Taiga API...
[2024-03-25 20:27:12 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2024-03-25 20:27:12 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
[2024-03-25 20:27:12 +0000] [1] [INFO] Using worker: sync
[2024-03-25 20:27:12 +0000] [34] [INFO] Booting worker with pid: 34
[2024-03-25 20:27:12 +0000] [35] [INFO] Booting worker with pid: 35
[2024-03-25 20:27:12 +0000] [36] [INFO] Booting worker with pid: 36
[2024-03-25 20:30:52 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:34)
[2024-03-25 20:30:53 +0000] [64] [INFO] Booting worker with pid: 64
[2024-03-25 20:42:42 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:35)
[2024-03-25 20:42:42 +0000] [74] [INFO] Booting worker with pid: 74
[2024-03-25 20:45:50 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:64)
[2024-03-25 20:45:50 +0000] [84] [INFO] Booting worker with pid: 84
[2024-03-25 20:53:12 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:36)
[2024-03-25 20:53:12 +0000] [94] [INFO] Booting worker with pid: 94
[2024-03-25 20:54:48 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:74)
[2024-03-25 20:54:49 +0000] [104] [INFO] Booting worker with pid: 104
[2024-03-25 21:00:32 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:104)
[2024-03-25 21:00:33 +0000] [114] [INFO] Booting worker with pid: 114
[2024-03-25 21:03:24 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:114)
[2024-03-25 21:03:25 +0000] [124] [INFO] Booting worker with pid: 124
[2024-03-25 21:04:15 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:84)
[2024-03-25 21:04:16 +0000] [134] [INFO] Booting worker with pid: 134
[2024-03-25 21:19:23 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:134)
[2024-03-25 21:19:24 +0000] [144] [INFO] Booting worker with pid: 144
[2024-03-25 21:22:20 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:144)
[2024-03-25 21:22:21 +0000] [154] [INFO] Booting worker with pid: 154
[2024-03-25 21:23:04 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:124)
[2024-03-25 21:23:04 +0000] [164] [INFO] Booting worker with pid: 164
[2024-03-25 21:23:29 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:154)
[2024-03-25 21:23:29 +0000] [174] [INFO] Booting worker with pid: 174
[2024-03-25 21:23:33 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:94)
[2024-03-25 21:23:34 +0000] [184] [INFO] Booting worker with pid: 184
[2024-03-25 21:24:24 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:164)
[2024-03-25 21:24:25 +0000] [194] [INFO] Booting worker with pid: 194
[2024-03-25 21:24:38 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:184)
[2024-03-25 21:24:38 +0000] [204] [INFO] Booting worker with pid: 204
[2024-03-25 21:29:49 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:204)
[2024-03-25 21:29:50 +0000] [214] [INFO] Booting worker with pid: 214
3

Hi @Vladimir_Sumarokov

Is there any error in taiga-async or taiga-async-rabbitmq? I think your problem here is because taiga-back can create async tasks to send emails.

You can use

docker compose logs taiga-async
docker compose logs taiga-async-rabbitmq

to get all the log messages related to this two services.

Best regards

4

Solved - my mistake - when I use external database, I disabled “taiga-db” service in docker-compose.yaml
When I uncomment this service, all invites works

Thank you and sorry for your time

5

Don’t worry, I’m glad you solved the problem. Feel free to ask if you have any other questions.