Timeline doesn't appear on projects

Troubleshooting
1

Hello,
I run Taiga inside docker and i’ve managed to get it to work nicely.
However, i’ve noticed that the timeline on the homepage of any project does not show any history whatsoever. I have checked each container log and i don’t see any errors or anything that would seem relevant to the issue.
Any ideas?

image
image1114×904 11.2 KB

docker-compose:

version: "3.5"

x-environment:
  &default-back-environment
  # These environment variables will be used by taiga-back and taiga-async.
  # Database settings
  POSTGRES_DB: "taiga"
  POSTGRES_USER: "${POSTGRES_USER}"
  POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
  POSTGRES_HOST: "taiga-db"
  # Taiga settings
  TAIGA_SECRET_KEY: "${SECRET_KEY}"
  TAIGA_SITES_SCHEME: "${TAIGA_SCHEME}"
  TAIGA_SITES_DOMAIN: "${TAIGA_DOMAIN}"
  TAIGA_SUBPATH: "${SUBPATH}"
  # Email settings.
  EMAIL_BACKEND: "django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend"
  DEFAULT_FROM_EMAIL: "${EMAIL_DEFAULT_FROM}"
  EMAIL_USE_TLS: "${EMAIL_USE_TLS}"
  EMAIL_USE_SSL: "${EMAIL_USE_SSL}"
  EMAIL_HOST: "${EMAIL_HOST}"
  EMAIL_PORT: "${EMAIL_PORT}"
  EMAIL_HOST_USER: "${EMAIL_HOST_USER}"
  EMAIL_HOST_PASSWORD: "${EMAIL_HOST_PASSWORD}"
  # Rabbitmq settings
  RABBITMQ_USER: "${RABBITMQ_USER}"
  RABBITMQ_PASS: "${RABBITMQ_PASS}"
  # Telemetry settings
  ENABLE_TELEMETRY: "${ENABLE_TELEMETRY}"
  # ...your customizations go here
  SESSION_COOKIE_SECURE: "False"
  CSRF_COOKIE_SECURE: "False" 
  PUBLIC_REGISTER_ENABLED: "False"

x-volumes:
  &default-back-volumes
  # These volumens will be used by taiga-back and taiga-async.
  - taiga-static-data:/taiga-back/static
  - taiga-media-data:/taiga-back/media
  # - ./config.py:/taiga-back/settings/config.py

services:
  taiga-db:
    image: postgres:12.3
    restart: unless-stopped
    environment:
      POSTGRES_DB: "taiga"
      POSTGRES_USER: "${POSTGRES_USER}"
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER}"]
      interval: 2s
      timeout: 15s
      retries: 5
      start_period: 3s
    volumes:
      - taiga-db-data:/var/lib/postgresql/data
    networks:
      - taiga

  taiga-back:
    image: taigaio/taiga-back:latest
    environment: *default-back-environment
    volumes: *default-back-volumes
    restart: unless-stopped
    networks:
      - taiga
    depends_on:
      taiga-db:
        condition: service_healthy
      taiga-events-rabbitmq:
        condition: service_started
      taiga-async-rabbitmq:
        condition: service_started

  taiga-async:
    image: taigaio/taiga-back:latest
    environment: *default-back-environment
    volumes: *default-back-volumes
    restart: unless-stopped
    networks:
      - taiga
    depends_on:
      taiga-db:
        condition: service_healthy
      taiga-events-rabbitmq:
        condition: service_started
      taiga-async-rabbitmq:
        condition: service_started

  taiga-async-rabbitmq:
    image: rabbitmq:3.8-management-alpine
    restart: unless-stopped
    environment:
      RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}"
      RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}"
      RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}"
      RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}"
    hostname: "taiga-async-rabbitmq"
    volumes:
      - taiga-async-rabbitmq-data:/var/lib/rabbitmq
    networks:
      - taiga

  taiga-front:
    image: taigaio/taiga-front:latest
    restart: unless-stopped
    environment:
      TAIGA_URL: "${TAIGA_SCHEME}://${TAIGA_DOMAIN}"
      TAIGA_WEBSOCKETS_URL: "${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}"
      TAIGA_SUBPATH: "${SUBPATH}"
      PUBLIC_REGISTER_ENABLED: "false"
      # ...your customizations go here
    networks:
      - taiga
    # volumes:
    #   - ./conf.json:/usr/share/nginx/html/conf.json

  taiga-events:
    image: taigaio/taiga-events:latest
    restart: unless-stopped
    environment:
      RABBITMQ_USER: "${RABBITMQ_USER}"
      RABBITMQ_PASS: "${RABBITMQ_PASS}"
      TAIGA_SECRET_KEY: "${SECRET_KEY}"
    networks:
      - taiga
    depends_on:
      taiga-events-rabbitmq:
        condition: service_started

  taiga-events-rabbitmq:
    image: rabbitmq:3.8-management-alpine
    restart: unless-stopped
    environment:
      RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}"
      RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}"
      RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}"
      RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}"
    hostname: "taiga-events-rabbitmq"
    volumes:
      - taiga-events-rabbitmq-data:/var/lib/rabbitmq
    networks:
      - taiga

  taiga-protected:
    image: taigaio/taiga-protected:latest
    restart: unless-stopped
    environment:
      MAX_AGE: "${ATTACHMENTS_MAX_AGE}"
      SECRET_KEY: "${SECRET_KEY}"
    networks:
      - taiga

  taiga-gateway:
    image: nginx:1.19-alpine
    restart: unless-stopped
    ports:
      - "9000:80"
    volumes:
      - /home/administrator/dockerapps/taiga/taiga-gateway/taiga.conf:/etc/nginx/conf.d/default.conf
      - taiga-static-data:/taiga/static
      - taiga-media-data:/taiga/media
    networks:
      - taiga
    depends_on:
      - taiga-front
      - taiga-back
      - taiga-events

volumes:
  taiga-static-data:
  taiga-media-data:
  taiga-db-data:
  taiga-async-rabbitmq-data:
  taiga-events-rabbitmq-data:

networks:
  taiga:
2

Hi @crawmartino

This should be because the service taiga-async is not working propertly. Maybe because the connection with rabbitmq is not working.

Check logs of taiga-async nad taiga-async-rabbitmq to detect if there is some error. Sometime it could be because you change the rabbitmq settings (normaly user and pass) after the first initialization. In these cases, the rabbitmq data volume is created with the initial configuration and stops working with the new modifications.

On the other hand, you share with us your docker-compose file but .env file is needed too to know the value of the env variables you are using.

I hope this can help.

Best regards

3

Hello,

Here is the log for taiga-async:

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-02-24 06:11:15 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2024-02-24 06:11:15 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
[2024-02-24 06:11:15 +0000] [1] [INFO] Using worker: sync
[2024-02-24 06:11:15 +0000] [57] [INFO] Booting worker with pid: 57
[2024-02-24 06:11:15 +0000] [58] [INFO] Booting worker with pid: 58
[2024-02-24 06:11:15 +0000] [59] [INFO] Booting worker with pid: 59

taiga-async-rabbitmq (There are two errors in the logs):

2024-02-24 06:10:23.611 [info] <0.273.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit
2024-02-24 06:10:23.612 [info] <0.273.0> Running boot step rabbit_queue_location_random defined by app rabbit
2024-02-24 06:10:23.612 [info] <0.273.0> Running boot step rabbit_event defined by app rabbit
2024-02-24 06:10:23.612 [info] <0.273.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit
2024-02-24 06:10:23.612 [info] <0.273.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit
2024-02-24 06:10:23.612 [info] <0.273.0> Running boot step rabbit_exchange_type_direct defined by app rabbit
2024-02-24 06:10:23.613 [info] <0.273.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit
2024-02-24 06:10:23.613 [info] <0.273.0> Running boot step rabbit_exchange_type_headers defined by app rabbit
2024-02-24 06:10:23.613 [info] <0.273.0> Running boot step rabbit_exchange_type_topic defined by app rabbit
2024-02-24 06:10:23.613 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step rabbit_priority_queue defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Priority queues enabled, real BQ is rabbit_variable_queue
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step rabbit_queue_location_client_local defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step rabbit_queue_location_min_masters defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step kernel_ready defined by app rabbit
2024-02-24 06:10:23.614 [info] <0.273.0> Running boot step rabbit_sysmon_minder defined by app rabbit
2024-02-24 06:10:23.615 [info] <0.273.0> Running boot step rabbit_epmd_monitor defined by app rabbit
2024-02-24 06:10:23.617 [info] <0.466.0> epmd monitor knows us, inter-node communication (distribution) port: 25672
2024-02-24 06:10:23.617 [info] <0.273.0> Running boot step guid_generator defined by app rabbit
2024-02-24 06:10:23.644 [info] <0.273.0> Running boot step rabbit_node_monitor defined by app rabbit
2024-02-24 06:10:23.645 [info] <0.470.0> Starting rabbit_node_monitor
2024-02-24 06:10:23.645 [info] <0.273.0> Running boot step delegate_sup defined by app rabbit
2024-02-24 06:10:23.647 [info] <0.273.0> Running boot step rabbit_memory_monitor defined by app rabbit
2024-02-24 06:10:23.647 [info] <0.273.0> Running boot step core_initialized defined by app rabbit
2024-02-24 06:10:23.647 [info] <0.273.0> Running boot step upgrade_queues defined by app rabbit
2024-02-24 06:10:23.696 [info] <0.273.0> Running boot step channel_tracking defined by app rabbit
2024-02-24 06:10:23.697 [info] <0.273.0> Setting up a table for channel tracking on this node: 'tracked_channel_on_node_rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.697 [info] <0.273.0> Setting up a table for channel tracking on this node: 'tracked_channel_table_per_user_on_node_rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.697 [info] <0.273.0> Running boot step rabbit_channel_tracking_handler defined by app rabbit
2024-02-24 06:10:23.697 [info] <0.273.0> Running boot step connection_tracking defined by app rabbit
2024-02-24 06:10:23.698 [info] <0.273.0> Setting up a table for connection tracking on this node: 'tracked_connection_on_node_rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.698 [info] <0.273.0> Setting up a table for per-vhost connection counting on this node: 'tracked_connection_per_vhost_on_node_rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.698 [info] <0.273.0> Setting up a table for per-user connection counting on this node: 'tracked_connection_table_per_user_on_node_rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.699 [info] <0.273.0> Running boot step rabbit_connection_tracking_handler defined by app rabbit
2024-02-24 06:10:23.699 [info] <0.273.0> Running boot step rabbit_exchange_parameters defined by app rabbit
2024-02-24 06:10:23.699 [info] <0.273.0> Running boot step rabbit_mirror_queue_misc defined by app rabbit
2024-02-24 06:10:23.699 [info] <0.273.0> Running boot step rabbit_policies defined by app rabbit
2024-02-24 06:10:23.701 [info] <0.273.0> Running boot step rabbit_policy defined by app rabbit
2024-02-24 06:10:23.701 [info] <0.273.0> Running boot step rabbit_queue_location_validator defined by app rabbit
2024-02-24 06:10:23.701 [info] <0.273.0> Running boot step rabbit_quorum_memory_manager defined by app rabbit
2024-02-24 06:10:23.701 [info] <0.273.0> Running boot step rabbit_vhost_limit defined by app rabbit
2024-02-24 06:10:23.702 [info] <0.273.0> Running boot step rabbit_mgmt_reset_handler defined by app rabbitmq_management
2024-02-24 06:10:23.702 [info] <0.273.0> Running boot step rabbit_mgmt_db_handler defined by app rabbitmq_management_agent
2024-02-24 06:10:23.702 [info] <0.273.0> Management plugin: using rates mode 'basic'
2024-02-24 06:10:23.702 [info] <0.273.0> Running boot step recovery defined by app rabbit
2024-02-24 06:10:23.703 [error] <0.273.0> Discarding message {'$gen_cast',{force_event_refresh,#Ref<0.2644467496.635437058.87869>}} from <0.273.0> to <0.524.0> in an old incarnation (1708754729) of this node (1708755007)
2024-02-24 06:10:23.703 [error] emulator Discarding message {'$gen_cast',{force_event_refresh,#Ref<0.2644467496.635437058.87869>}} from <0.273.0> to <0.524.0> in an old incarnation (1708754729) of this node (1708755007)
2024-02-24 06:10:23.705 [info] <0.507.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@taiga-async-rabbitmq/msg_stores/vhosts/DUUPSD51ILPPE6LUATO0IN63B' for vhost 'taiga' exists
2024-02-24 06:10:23.735 [info] <0.507.0> Starting message stores for vhost 'taiga'
2024-02-24 06:10:23.735 [info] <0.511.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2024-02-24 06:10:23.741 [info] <0.507.0> Started message store of type transient for vhost 'taiga'
2024-02-24 06:10:23.741 [info] <0.515.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2024-02-24 06:10:23.747 [info] <0.507.0> Started message store of type persistent for vhost 'taiga'
2024-02-24 06:10:23.790 [info] <0.273.0> Running boot step empty_db_check defined by app rabbit
2024-02-24 06:10:23.790 [info] <0.273.0> Will not seed default virtual host and user: have definitions to load...
2024-02-24 06:10:23.790 [info] <0.273.0> Running boot step rabbit_looking_glass defined by app rabbit
2024-02-24 06:10:23.791 [info] <0.273.0> Running boot step rabbit_core_metrics_gc defined by app rabbit
2024-02-24 06:10:23.791 [info] <0.273.0> Running boot step background_gc defined by app rabbit
2024-02-24 06:10:23.792 [info] <0.273.0> Running boot step routing_ready defined by app rabbit
2024-02-24 06:10:23.792 [info] <0.273.0> Running boot step pre_flight defined by app rabbit
2024-02-24 06:10:23.792 [info] <0.273.0> Running boot step notify_cluster defined by app rabbit
2024-02-24 06:10:23.792 [info] <0.273.0> Running boot step networking defined by app rabbit
2024-02-24 06:10:23.792 [info] <0.273.0> Running boot step definition_import_worker_pool defined by app rabbit
2024-02-24 06:10:23.792 [info] <0.378.0> Starting worker pool 'definition_import_pool' with 16 processes in it
2024-02-24 06:10:23.795 [info] <0.273.0> Running boot step cluster_name defined by app rabbit
2024-02-24 06:10:23.795 [info] <0.273.0> Running boot step direct_client defined by app rabbit
2024-02-24 06:10:23.795 [info] <0.273.0> Running boot step rabbit_management_load_definitions defined by app rabbitmq_management
2024-02-24 06:10:23.795 [info] <0.561.0> Resetting node maintenance status
2024-02-24 06:10:23.795 [info] <0.44.0> Application rabbit started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.802 [info] <0.44.0> Application rabbitmq_management_agent started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.802 [info] <0.44.0> Application cowlib started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.803 [info] <0.44.0> Application cowboy started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.803 [info] <0.44.0> Application rabbitmq_web_dispatch started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.803 [info] <0.44.0> Application amqp_client started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.857 [info] <0.620.0> Management plugin: HTTP (non-TLS) listener started on port 15672
2024-02-24 06:10:23.857 [info] <0.648.0> Statistics database started.
2024-02-24 06:10:23.858 [info] <0.647.0> Starting worker pool 'management_worker_pool' with 3 processes in it
2024-02-24 06:10:23.858 [info] <0.44.0> Application rabbitmq_management started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.909 [info] <0.44.0> Application prometheus started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.913 [info] <0.661.0> Prometheus metrics: HTTP (non-TLS) listener started on port 15692
2024-02-24 06:10:23.913 [info] <0.561.0> Ready to start client connection listeners
2024-02-24 06:10:23.913 [info] <0.44.0> Application rabbitmq_prometheus started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.917 [info] <0.705.0> started TCP listener on [::]:5672
2024-02-24 06:10:26.042 [info] <0.561.0> Server startup complete; 4 plugins started.
 * rabbitmq_prometheus
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * rabbitmq_management_agent
 completed with 4 plugins.
2024-02-24 06:10:26.042 [info] <0.561.0> Resetting node maintenance status

.env:

TAIGA_SCHEME=http
TAIGA_DOMAIN=192.168.1.119:9000
SUBPATH=""
WEBSOCKETS_SCHEME=ws
SECRET_KEY="randomly generated 32 character string"
POSTGRES_USER=taiga
POSTGRES_PASSWORD=taiga
EMAIL_BACKEND=smtp
EMAIL_HOST=redacted
EMAIL_PORT=587
EMAIL_HOST_USER=redacted@redacted.com
EMAIL_HOST_PASSWORD=redacted
EMAIL_DEFAULT_FROM=redacted@redacted.com
EMAIL_USE_TLS=True
EMAIL_USE_SSL=False
RABBITMQ_USER=taiga
RABBITMQ_PASS=taiga
RABBITMQ_VHOST=taiga
RABBITMQ_ERLANG_COOKIE=secret-erlang-cookie
ATTACHMENTS_MAX_AGE=360
ENABLE_TELEMETRY=False
4

Can you send us more logs from taiga-async-rabbitmq? Something like…

taiga-async-rabbitmq-1  |  * rabbitmq_prometheus
taiga-async-rabbitmq-1  |  * rabbitmq_management
taiga-async-rabbitmq-1  |  * rabbitmq_web_dispatch
taiga-async-rabbitmq-1  |  * rabbitmq_management_agent
taiga-async-rabbitmq-1  |  completed with 4 plugins.
taiga-async-rabbitmq-1  | 2024-02-26 16:53:52.358 [info] <0.551.0> Resetting node maintenance status
taiga-async-rabbitmq-1  | 2024-02-26 16:53:54.900 [info] <0.700.0> accepting AMQP connection <0.700.0> (172.21.0.9:35504 -> 172.21.0.4:5672)
taiga-async-rabbitmq-1  | 2024-02-26 16:53:54.902 [info] <0.700.0> connection <0.700.0> (172.21.0.9:35504 -> 172.21.0.4:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga-async-rabbitmq-1  | 2024-02-26 16:53:54.904 [info] <0.708.0> accepting AMQP connection <0.708.0> (172.21.0.9:35506 -> 172.21.0.4:5672)
taiga-async-rabbitmq-1  | 2024-02-26 16:53:54.905 [info] <0.708.0> connection <0.708.0> (172.21.0.9:35506 -> 172.21.0.4:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga-async-rabbitmq-1  | 2024-02-26 16:53:54.912 [info] <0.731.0> accepting AMQP connection <0.731.0> (172.21.0.9:35520 -> 172.21.0.4:5672)
taiga-async-rabbitmq-1  | 2024-02-26 16:53:54.913 [info] <0.731.0> connection <0.731.0> (172.21.0.9:35520 -> 172.21.0.4:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
5

I want to see some line with this message

6

Of course.

2024-02-24 06:10:23.913 [info] <0.44.0> Application rabbitmq_prometheus started on node 'rabbit@taiga-async-rabbitmq'
2024-02-24 06:10:23.917 [info] <0.705.0> started TCP listener on [::]:5672
2024-02-24 06:10:26.042 [info] <0.561.0> Server startup complete; 4 plugins started.
 * rabbitmq_prometheus
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * rabbitmq_management_agent
 completed with 4 plugins.
2024-02-24 06:10:26.042 [info] <0.561.0> Resetting node maintenance status
2024-02-24 09:45:29.855 [info] <0.4762.0> accepting AMQP connection <0.4762.0> (172.30.0.8:40690 -> 172.30.0.6:5672)
2024-02-24 09:45:29.860 [info] <0.4762.0> connection <0.4762.0> (172.30.0.8:40690 -> 172.30.0.6:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
2024-02-24 10:23:14.655 [info] <0.5485.0> accepting AMQP connection <0.5485.0> (172.30.0.8:49094 -> 172.30.0.6:5672)
2024-02-24 10:23:14.660 [info] <0.5485.0> connection <0.5485.0> (172.30.0.8:49094 -> 172.30.0.6:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
2024-02-24 16:33:18.861 [info] <0.12462.0> accepting AMQP connection <0.12462.0> (172.30.0.8:53936 -> 172.30.0.6:5672)
2024-02-24 16:33:18.867 [info] <0.12462.0> connection <0.12462.0> (172.30.0.8:53936 -> 172.30.0.6:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
7

Well, everything seems to be working correctly. I’ll try to stop the server, remove containers and volumes for taiga-async and taiga-async-rabbitmq and start the server again. After that, you should check if timeline entries appear after some action (create or update a story, for example).

You can regenerate the timeline with this command

./taiga-manage.sh rebuild_timeline

With --purge the current entries will be deleted before the regeneration.

8

If i delete the volumes with taiga-async and taiga-async-rabbitmq will my data be lost?

Also, i’ve installed everything through portainer and used the docker-compose file instead of running the .sh script.

9

Your data is store in the database.

The rabbitmq instance is just for managing async tasks (send emails, generate timeline entries,…), so nothing should lose. The valuable information is in the postgresql database and in the “media” volume.

You can access to taiga-back container to rebuild the timeline using ./manage.py if you can use taiga-manage.sh

image
image1920×532 87.2 KB

10

I’ve deleted the async-rabbitmq volume and let it regenerate.

In the taiga-back console, ./manage.py rebuild_timeline shows this error:

root@dd832a7d8d9e:/taiga-back# ./manage.py rebuild_timeline
Project: test1
Traceback (most recent call last):
  File "/taiga-back/./manage.py", line 17, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "/opt/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/venv/lib/python3.11/site-packages/django/core/management/base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/venv/lib/python3.11/site-packages/django/core/management/base.py", line 398, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/taiga-back/taiga/timeline/management/commands/rebuild_timeline.py", line 52, in handle
    rebuild_timeline(options["initial_date"], options["final_date"], options["project"])
  File "/opt/venv/lib/python3.11/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/taiga-back/taiga/timeline/rebuilder.py", line 108, in rebuild_timeline
    "user": extract_user_info(project.owner),
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/taiga-back/taiga/timeline/service.py", line 282, in extract_user_info
    "id": instance.pk
          ^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'pk'
root@dd832a7d8d9e:/taiga-back#

Timeline still does not appear after updating a story.

11

Wow. You should see something like this

image
image1920×525 81.4 KB

Your project test1 is corrupted because it does not have an owner. Try to remove this project from the superadmin panel or assign some owner. This maybe happened with some task that didn’t complete correctly due to an error (maybe a project deletion, I have no idea).

12

Ah. test1 is the first ever project i made and then messed with permissions in the django admin panel breaking it so I deleted it but I guess that must have not worked.

I’ll try getting rid of all the ones that I don’t need and check if that fixes it.

13

I’ve deleted all the “deleted” projects from the django dashboard and the timeline works now!
Thank you for your help.

14

Great!!! \o/

You are welcome.