Sebastian
Sebastian
TTwenty
Created by Sebastian on 2/14/2025 in #❓︱help
Google Calendar sync stuck
also - should I run these commands on server or worker? @charles
18 replies
TTwenty
Created by Sebastian on 2/14/2025 in #❓︱help
Google Calendar sync stuck
yes, I did run all these commands. I just didn't paste you my whole redis output due to Discord limitations. Do you want me to paste all I have in Redis? @charles
18 replies
TTwenty
Created by Sebastian on 2/14/2025 in #❓︱help
Google Calendar sync stuck
do you need all of them?
18 replies
TTwenty
Created by Sebastian on 2/14/2025 in #❓︱help
Google Calendar sync stuck
that's part of them:
127.0.0.1:6379> keys bull:*
1) "bull:entity-events-to-db-queue:151"
2) "bull:webhook-queue:35"
3) "bull:entity-events-to-db-queue:97"
4) "bull:entity-events-to-db-queue:115"
5) "bull:entity-events-to-db-queue:47"
6) "bull:webhook-queue:19"
7) "bull:entity-events-to-db-queue:145"
8) "bull:webhook-queue:47"
9) "bull:entity-events-to-db-queue:40"
10) "bull:entity-events-to-db-queue:meta"
11) "bull:entity-events-to-db-queue:163"
12) "bull:entity-events-to-db-queue:100"
13) "bull:entity-events-to-db-queue:157"
14) "bull:calendar-queue:1"
15) "bull:entity-events-to-db-queue:139"
16) "bull:entity-events-to-db-queue:50"
17) "bull:entity-events-to-db-queue:85"
18) "bull:cron-queue:events"
19) "bull:entity-events-to-db-queue:36"
20) "bull:cron-queue:repeat:dddf90bd802998940aab1261051870c9:1739529300000"
21) "bull:entity-events-to-db-queue:144"
22) "bull:cron-queue:repeat:14166af08923f86d1550d0acfcc34009:1739530800000"
23) "bull:entity-events-to-db-queue:22"
24) "bull:entity-events-to-db-queue:55"
25) "bull:entity-events-to-db-queue:28"
26) "bull:webhook-queue:41"
27) "bull:entity-events-to-db-queue:34"
28) "bull:webhook-queue:24"
29) "bull:cron-queue:id"
30) "bull:entity-events-to-db-queue:104"
31) "bull:entity-events-to-db-queue:142"
32) "bull:webhook-queue:22"
33) "bull:entity-events-to-db-queue:159"
34) "bull:webhook-queue:48"
35) "bull:entity-events-to-db-queue:166"
36) "bull:email-queue:meta"
37) "bull:entity-events-to-db-queue:60"
38) "bull:entity-events-to-db-queue:128"
39) "bull:entity-events-to-db-queue:172"
40) "bull:webhook-queue:18"
41) "bull:entity-events-to-db-queue:135"
42) "bull:calendar-queue:7"
43) "bull:entity-events-to-db-queue:180"
44) "bull:webhook-queue:71"
45) "bull:cron-queue:meta"
46) "bull:entity-events-to-db-queue:165"
47) "bull:entity-events-to-db-queue:122"
48) "bull:entity-events-to-db-queue:58"
49) "bull:entity-events-to-db-queue:102"
127.0.0.1:6379> keys bull:*
1) "bull:entity-events-to-db-queue:151"
2) "bull:webhook-queue:35"
3) "bull:entity-events-to-db-queue:97"
4) "bull:entity-events-to-db-queue:115"
5) "bull:entity-events-to-db-queue:47"
6) "bull:webhook-queue:19"
7) "bull:entity-events-to-db-queue:145"
8) "bull:webhook-queue:47"
9) "bull:entity-events-to-db-queue:40"
10) "bull:entity-events-to-db-queue:meta"
11) "bull:entity-events-to-db-queue:163"
12) "bull:entity-events-to-db-queue:100"
13) "bull:entity-events-to-db-queue:157"
14) "bull:calendar-queue:1"
15) "bull:entity-events-to-db-queue:139"
16) "bull:entity-events-to-db-queue:50"
17) "bull:entity-events-to-db-queue:85"
18) "bull:cron-queue:events"
19) "bull:entity-events-to-db-queue:36"
20) "bull:cron-queue:repeat:dddf90bd802998940aab1261051870c9:1739529300000"
21) "bull:entity-events-to-db-queue:144"
22) "bull:cron-queue:repeat:14166af08923f86d1550d0acfcc34009:1739530800000"
23) "bull:entity-events-to-db-queue:22"
24) "bull:entity-events-to-db-queue:55"
25) "bull:entity-events-to-db-queue:28"
26) "bull:webhook-queue:41"
27) "bull:entity-events-to-db-queue:34"
28) "bull:webhook-queue:24"
29) "bull:cron-queue:id"
30) "bull:entity-events-to-db-queue:104"
31) "bull:entity-events-to-db-queue:142"
32) "bull:webhook-queue:22"
33) "bull:entity-events-to-db-queue:159"
34) "bull:webhook-queue:48"
35) "bull:entity-events-to-db-queue:166"
36) "bull:email-queue:meta"
37) "bull:entity-events-to-db-queue:60"
38) "bull:entity-events-to-db-queue:128"
39) "bull:entity-events-to-db-queue:172"
40) "bull:webhook-queue:18"
41) "bull:entity-events-to-db-queue:135"
42) "bull:calendar-queue:7"
43) "bull:entity-events-to-db-queue:180"
44) "bull:webhook-queue:71"
45) "bull:cron-queue:meta"
46) "bull:entity-events-to-db-queue:165"
47) "bull:entity-events-to-db-queue:122"
48) "bull:entity-events-to-db-queue:58"
49) "bull:entity-events-to-db-queue:102"
18 replies
TTwenty
Created by Sebastian on 2/14/2025 in #❓︱help
Google Calendar sync stuck
my worker config:
worker:
image: twentycrm/twenty:${TAG}
command: ["yarn", "worker:prod"]
environment:
#PG_DATABASE_URL: postgres://twenty:twenty@${PG_DATABASE_HOST}/default
PG_DATABASE_URL: postgres://${PGUSER_SUPERUSER:-postgres}:${PGPASSWORD_SUPERUSER:-postgres}@${PG_DATABASE_HOST:-db:5432}/default
SERVER_URL: ${SERVER_URL}
REDIS_URL: ${REDIS_URL:-redis://localhost:6379}

FRONT_DOMAIN: ${FRONT_DOMAIN}
FRONT_PROTOCOL: ${FRONT_PROTOCOL}
FRONT_PORT: ${FRONT_PORT}

STORAGE_TYPE: ${STORAGE_TYPE}
STORAGE_S3_REGION: ${STORAGE_S3_REGION}
STORAGE_S3_NAME: ${STORAGE_S3_NAME}
STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}

APP_SECRET: ${APP_SECRET}

AUTH_PASSWORD_ENABLED: ${AUTH_PASSWORD_ENABLED}
AUTH_GOOGLE_ENABLED: ${AUTH_GOOGLE_ENABLED}
AUTH_GOOGLE_CLIENT_ID: ${AUTH_GOOGLE_CLIENT_ID}
AUTH_GOOGLE_CLIENT_SECRET: ${AUTH_GOOGLE_CLIENT_SECRET}
AUTH_GOOGLE_CALLBACK_URL: ${AUTH_GOOGLE_CALLBACK_URL}
AUTH_GOOGLE_APIS_CALLBACK_URL: ${AUTH_GOOGLE_APIS_CALLBACK_URL}

MESSAGING_PROVIDER_GMAIL_ENABLED: ${MESSAGING_PROVIDER_GMAIL_ENABLED}
CALENDAR_PROVIDER_GOOGLE_ENABLED: ${CALENDAR_PROVIDER_GOOGLE_ENABLED}

EMAIL_DRIVER: ${EMAIL_DRIVER}
EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS}
EMAIL_FROM_NAME: ${EMAIL_FROM_NAME}
EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS}
EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST}
EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT}
EMAIL_SMTP_USER: ${EMAIL_SMTP_USER}
EMAIL_SMTP_PASSWORD: ${EMAIL_SMTP_PASSWORD}

ACCESS_TOKEN_EXPIRES_IN: ${ACCESS_TOKEN_EXPIRES_IN}
LOGIN_TOKEN_EXPIRES_IN: ${LOGIN_TOKEN_EXPIRES_IN}

depends_on:
db:
condition: service_healthy
server:
condition: service_healthy
restart: always
worker:
image: twentycrm/twenty:${TAG}
command: ["yarn", "worker:prod"]
environment:
#PG_DATABASE_URL: postgres://twenty:twenty@${PG_DATABASE_HOST}/default
PG_DATABASE_URL: postgres://${PGUSER_SUPERUSER:-postgres}:${PGPASSWORD_SUPERUSER:-postgres}@${PG_DATABASE_HOST:-db:5432}/default
SERVER_URL: ${SERVER_URL}
REDIS_URL: ${REDIS_URL:-redis://localhost:6379}

FRONT_DOMAIN: ${FRONT_DOMAIN}
FRONT_PROTOCOL: ${FRONT_PROTOCOL}
FRONT_PORT: ${FRONT_PORT}

STORAGE_TYPE: ${STORAGE_TYPE}
STORAGE_S3_REGION: ${STORAGE_S3_REGION}
STORAGE_S3_NAME: ${STORAGE_S3_NAME}
STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}

APP_SECRET: ${APP_SECRET}

AUTH_PASSWORD_ENABLED: ${AUTH_PASSWORD_ENABLED}
AUTH_GOOGLE_ENABLED: ${AUTH_GOOGLE_ENABLED}
AUTH_GOOGLE_CLIENT_ID: ${AUTH_GOOGLE_CLIENT_ID}
AUTH_GOOGLE_CLIENT_SECRET: ${AUTH_GOOGLE_CLIENT_SECRET}
AUTH_GOOGLE_CALLBACK_URL: ${AUTH_GOOGLE_CALLBACK_URL}
AUTH_GOOGLE_APIS_CALLBACK_URL: ${AUTH_GOOGLE_APIS_CALLBACK_URL}

MESSAGING_PROVIDER_GMAIL_ENABLED: ${MESSAGING_PROVIDER_GMAIL_ENABLED}
CALENDAR_PROVIDER_GOOGLE_ENABLED: ${CALENDAR_PROVIDER_GOOGLE_ENABLED}

EMAIL_DRIVER: ${EMAIL_DRIVER}
EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS}
EMAIL_FROM_NAME: ${EMAIL_FROM_NAME}
EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS}
EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST}
EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT}
EMAIL_SMTP_USER: ${EMAIL_SMTP_USER}
EMAIL_SMTP_PASSWORD: ${EMAIL_SMTP_PASSWORD}

ACCESS_TOKEN_EXPIRES_IN: ${ACCESS_TOKEN_EXPIRES_IN}
LOGIN_TOKEN_EXPIRES_IN: ${LOGIN_TOKEN_EXPIRES_IN}

depends_on:
db:
condition: service_healthy
server:
condition: service_healthy
restart: always
18 replies
TTwenty
Created by Sebastian on 2/14/2025 in #❓︱help
Google Calendar sync stuck
thanks, commands applied. In worker logs I see only these repeating messages and nothing else:
worker-1 | query: SELECT * FROM current_schema()
worker-1 | query: CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
worker-1 | query: SELECT version();
worker-1 | query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'metadata' AND "table_name" = '_typeorm_migrations'
worker-1 | query: SELECT * FROM "metadata"."_typeorm_migrations" "_typeorm_migrations" ORDER BY "id" DESC
worker-1 | No migrations are pending
worker-1 | query: SELECT * FROM current_schema()
db-1 | 2025-02-14 10:36:26,045 INFO: no action. I am (0a878dffcf46), the leader with the lock
worker-1 | query: CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
worker-1 | query: SELECT version();
worker-1 | query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'core' AND "table_name" = '_typeorm_migrations'
worker-1 | query: SELECT * FROM "core"."_typeorm_migrations" "_typeorm_migrations" ORDER BY "id" DESC
worker-1 | No migrations are pending
worker-1 | Successfuly migrated DB!
worker-1 | touch: /app/docker-data/db_status: No such file or directory
worker-1 | Performed 'create extension "vector (pgvector)"' successfully
worker-1 | Performed 'create schema "public"' successfully
worker-1 | Performed 'create schema "metadata"' successfully
worker-1 | Performed 'create schema "core"' successfully
worker-1 | Performed 'create extension "uuid-ossp"' successfully
worker-1 | query: SELECT * FROM current_schema()
worker-1 | query: CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
worker-1 | query: SELECT version();
worker-1 | query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'metadata' AND "table_name" = '_typeorm_migrations'
worker-1 | query: SELECT * FROM "metadata"."_typeorm_migrations" "_typeorm_migrations" ORDER BY "id" DESC
worker-1 | No migrations are pending
worker-1 | query: SELECT * FROM current_schema()
db-1 | 2025-02-14 10:36:26,045 INFO: no action. I am (0a878dffcf46), the leader with the lock
worker-1 | query: CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
worker-1 | query: SELECT version();
worker-1 | query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'core' AND "table_name" = '_typeorm_migrations'
worker-1 | query: SELECT * FROM "core"."_typeorm_migrations" "_typeorm_migrations" ORDER BY "id" DESC
worker-1 | No migrations are pending
worker-1 | Successfuly migrated DB!
worker-1 | touch: /app/docker-data/db_status: No such file or directory
worker-1 | Performed 'create extension "vector (pgvector)"' successfully
worker-1 | Performed 'create schema "public"' successfully
worker-1 | Performed 'create schema "metadata"' successfully
worker-1 | Performed 'create schema "core"' successfully
worker-1 | Performed 'create extension "uuid-ossp"' successfully
18 replies
TTwenty
Created by Raph on 1/23/2025 in #❓︱help
Gmail email sync (not calendar sync) intermittently stuck.
@Raphaël how can I force the sync manually?
10 replies
TTwenty
Created by Raph on 1/23/2025 in #❓︱help
Gmail email sync (not calendar sync) intermittently stuck.
how do I force sync?
10 replies
TTwenty
Created by Raph on 1/23/2025 in #❓︱help
Gmail email sync (not calendar sync) intermittently stuck.
for message channel I see syncStatus: [null] syncStage: FULL_MESSAGE_LIST_FETCH_PENDING syncedAt: [null] for calendar channel: syncStatus: [null] syncStage: FULL_CALENDAR_EVENT_LIST_FETCH_PENDING syncedAt: [null]
10 replies
TTwenty
Created by Raph on 1/23/2025 in #❓︱help
Gmail email sync (not calendar sync) intermittently stuck.
@Raphaël looks like I have similar issue, or at least one of my users is complaining that contact sync is stuck. Where and how can I check your mentioned "messageChannel and calendarChannel syncStatus and syncStage"?
10 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
great, thanks, I'll do that!
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
would you have time tomorrow to have a video call to debug the upgrade process from 33 to 35 version by version?
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
looks like. also docs are missing updated docker-compose vars, like PG_DATABASE_URL: postgres://${PGUSER_SUPERUSER:-postgres}:${PGPASSWORD_SUPERUSER:-postgres}@${PG_DATABASE_HOST:-db:5432}/default instead of PG_DATABASE_URL: postgres://twenty:twenty@${PG_DATABASE_HOST}/default which I had to find in the repo
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
so I'll restore now to version 33
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
because now after restoring from backups which was running version 33, I did run yarn commands for 33 to 34 version, but now I get in the logs:
server-1 | error: error: column User.defaultWorkspaceId does not exist
server-1 | error: error: column User.defaultWorkspaceId does not exist
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
could you maybe update the documentation with clearer instructions of upgrades? like what has to be after and before, because right now it's unclear when to do dump and when restore of the dump
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
I think I'll just keep it at version 33, I don't want to waste anymore time on that
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
yes, I was playing with that whole day, adding and removing stuff in the database, but still no luck
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
I just restored everything to version 34
28 replies
TTwenty
Created by Sebastian on 1/20/2025 in #❓︱help
Upgrade to latest version doesn't work
no, I keep getting User is not a member of the workspace
28 replies