triggerdotdev/trigger.dev

bug: Run task history not showing after upgrading from beta-20 to beta-25

Closed this issue · 4 comments

MattCarneiro commented

Provide environment information

System:
OS: Linux 6.8 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (4) arm64 Neoverse-N1
Memory: 10.92 GB / 23.42 GB
Container: Yes
Shell: 5.1.4 - /bin/bash
Binaries:
Node: 20.11.1 - /usr/local/bin/node
npm: 10.2.4 - /usr/local/bin/npm
pnpm: 8.15.5 - /usr/local/bin/pnpm

node@b7d0b299f36f:/triggerdotdev$

Describe the bug

Image

After upgrading, every production run doesn't show any task log

I don't know to do.

Tasks are running with no problem but I can't see any log history or task run history

Image

Reproduction repo

no link

To reproduce

I just updated and this happens, my env is something likee this

LOGIN_ORIGIN=https://trig.***
APP_ORIGIN=https://trig.***
TRIGGER_API_URL=https://trig.***
PORT=3030
REMIX_APP_PORT=3030
MANAGED_WORKER_SECRET=4e3f1a7c9d***
COORDINATOR_SECRET=1a2b3c4d5e6f7a***
MAGIC_LINK_SECRET=secret
SESSION_SECRET=secret
CLICKHOUSE_URL="http://default:*****@main_clickhouse:8123/default?secure=false"
GOOSE_DRIVER=clickhouse
ENCRYPTION_KEY=ae13021afef0819c****
TRIGGER_SECRET_KEY=tr_dev_oPOezFvLq****
TRIGGER_SECRET_KEY=tr_prod_sZUC582**
TRIGGER_ACCESS_TOKEN=tr_pat_sojg1peo****
POSTGRES_USER=postgres
POSTGRES_PASSWORD=33106e5564***
POSTGRES_DB=main
DATABASE_HOST=main_trigger-db:5432
DATABASE_URL=postgres://postgres:@main_trigger-db:5432/main?sslmode=disable
DIRECT_URL=postgres://postgres:@main_trigger-db:5432/main?sslmode=disable
NODE_ENV=development
AUTH_GITHUB_CLIENT_ID=Ov23l****
AUTH_GITHUB_CLIENT_SECRET=e5a7a****
EMAIL_TRANSPORT=smtp
SMTP_HOST=smtp-pulse.com
SMTP_PORT=465
SMTP_SECURE=true
SMTP_USER=corporativo@*****
SMTP_PASSWORD=****
FROM_EMAIL=corporativo@****
REPLY_TO_EMAIL=notificacoes@****
LOGIN_ORIGIN=https://trig.****
APP_ORIGIN=https://trig.****
RUNTIME_PLATFORM=container

Registry onde as imagens serão publicadas e buscadas

DEPLOY_REGISTRY_HOST=reg2.*****

Credenciais de autenticação no registry (opcional se não exigir login)

DEPLOY_REGISTRY_USERNAME=elementttt
DEPLOY_REGISTRY_PASSWORD=*******

Namespace (opcional, para agrupar imagens)

DEPLOY_REGISTRY_NAMESPACE=******
DEPLOY_IMAGE_PLATFORM=linux/arm64

Configuração do Redis

REDIS_HOST=main_redis
REDIS_PORT=6379

Opcional, caso use autenticação:

REDIS_USERNAME=default
REDIS_PASSWORD=******

Se seu Redis não usa TLS:

REDIS_TLS_DISABLED=true
TRIGGER_BOOTSTRAP_ENABLED=0
TRIGGER_BOOTSTRAP_WORKER_GROUP_NAME=default
TRIGGER_BOOTSTRAP_WORKER_TOKEN_PATH=/data/worker_token

I am using via EasyPanel

Additional information

No response

MattCarneiro commented

I think it has something to do with clickhouse misconfigured

MattCarneiro commented

Log do clickhouse

25.07.31 05:00:34.237871 [ 86 ] {ff058f49-ec72-4b82-a5a4-e05af73b74ee} executeQuery: Code: 60. DB::Exception: Unknown table expression identifier 'goose_db_version' in scope SELECT version_id, is_applied FROM goose_db_version ORDER BY version_id DESC. (UNKNOWN_TABLE) (version 25.7.1.3997 (official build)) (from 10.0.1.22:42274) (in query: SELECT version_id, is_applied FROM goose_db_version ORDER BY version_id DESC), Stack trace (when copying this message, always include the lines below):

Somebody help

MattCarneiro commented

Hey @MattCarneiro you're probably still on an old webapp compose file, try this one: https://github.com/triggerdotdev/trigger.dev/blob/main/hosting/docker/webapp/docker-compose.yml

Thank you so much. I was missing these env here

RUN_REPLICATION_ENABLED: ${RUN_REPLICATION_ENABLED:-1}
RUN_REPLICATION_CLICKHOUSE_URL: ${RUN_REPLICATION_CLICKHOUSE_URL:-http://default:password@clickhouse:8123}
RUN_REPLICATION_LOG_LEVEL: ${RUN_REPLICATION_LOG_LEVEL:-info}

  • 👍1