Kobo upgrade ERROR: database "koboform" already exists database "kobocat" already exists

Hello guys,

I have updated to the lastest branch, setup was going fine but the logs are full of this error:

postgres-1 | 2025-12-01 21:21:09.277 GMT [2110] LOG: incomplete startup packet
postgres-1 | 2025-12-01 21:21:09.432 GMT [2112] ERROR: database “koboform” already exists
postgres-1 | 2025-12-01 21:21:09.432 GMT [2112] STATEMENT: CREATE DATABASE “koboform” OWNER “kobo”;
postgres-1 | 2025-12-01 21:21:09.518 GMT [2114] ERROR: database “kobocat” already exists
postgres-1 | 2025-12-01 21:21:09.518 GMT [2114] STATEMENT: CREATE DATABASE “kobocat” OWNER “kobo”;
postgres-1 | 2025-12-01 21:21:19.303 GMT [2122] ERROR: relation “project_ownership_transfer” does not exist at character 885
postgres-1 | 2025-12-01 21:21:19.303 GMT [2122] STATEMENT: SELECT “project_ownership_transfer”.“id”, “project_ownership_transfer”.“date_created”, “project_ownership_transfer”.“date_modified”, “project_ownership_transfer”.“uid”, “project_ownership_transfer”.“asset_id”, “project_ownership_transfer”.“invite_id”, “project_ownership_transfer”.“invite_type”, “project_ownership_invite”.“id”, “project_ownership_invite”.“date_created”, “project_ownership_invite”.“date_modified”, “project_ownership_invite”.“uid”, “project_ownership_invite”.“sender_id”, “project_ownership_invite”.“recipient_id”, “project_ownership_invite”.“status”, “project_ownership_invite”.“invite_type”, “auth_user”.“id”, “auth_user”.“password”, “auth_user”.“last_login”, “auth_user”.“is_superuser”, “auth_user”.“username”, “auth_user”.“first_name”, “auth_user”.“last_name”, “auth_user”.“email”, “auth_user”.“is_staff”, “auth_user”.“is_active”, “auth_user”.“date_joined” FROM “project_ownership_transfer” INNER JOIN “project_ownership_invite” ON (“project_ownership_transfer”.“invite_id” = “project_ownership_invite”.“id”) INNER JOIN “auth_user” ON (“project_ownership_invite”.“sender_id” = “auth_user”.“id”) WHERE “project_ownership_transfer”.“asset_id” IN (257, 238, 258, 176, 237, 230, 236, 235, 234, 233, 232, 231, 229, 228, 240, 211, 255, 254, 250, 249, 247, 184, 246, 165, 212, 245, 244, 243, 208, 173, 225, 224, 223, 222, 221, 220, 219, 204, 218, 210, 209, 207, 206, 197, 205, 202, 10, 239, 242, 241, 75, 227, 216, 226, 217, 167, 8, 196, 203, 201, 200, 192, 195, 194, 9, 12, 191, 190, 189, 188, 187, 186, 123, 94, 183, 181, 182, 130, 157, 141, 179, 180, 178, 177, 174, 175, 172, 171, 169, 166, 162, 161, 160, 136, 153, 155, 154, 151, 152, 150, 149, 148, 147, 146, 145, 39, 143, 142, 140, 138, 137, 135, 133, 134, 22, 132, 131, 129, 98, 103, 96, 110, 119, 105, 109, 90, 99, 92, 124, 95, 122, 121, 120, 100, 107, 104, 115, 93, 101, 111, 117, 116, 114, 113, 89, 108, 106, 102, 91, 36, 62, 70, 87, 86, 35, 85, 82, 81, 83, 84, 80, 79, 78, 42, 46, 74, 69, 72, 67, 68, 71, 66, 28, 65, 64, 63, 18, 60, 17, 45, 34, 58, 59, 51, 49, 40, 55, 25, 44, 48, 47, 43, 52, 38, 33, 32, 30, 24, 15, 20, 13, 21, 19, 16, 26) ORDER BY “project_ownership_transfer”.“date_created” ASC
mongo-1 | {“t”:{“$date”:“2025-12-01T21:21:21.019+00:00”},“s”:“I”, “c”:“NETWORK”, “id”:22943, “ctx”:“listener”,“msg”:“Connection accepted”,“attr”:{“remote”:“172.18.0.12:42356”,“uuid”:“23d765d7-49c7-40d6-a67d-1420c2b50696”,“connectionId”:155,“connectionCount”:1}}
mongo-1 | {“t”:{“$date”:“2025-12-01T21:21:21.020+00:00”},“s”:“I”, “c”:“NETWORK”, “id”:22944, “ctx”:“conn155”,“msg”:“Connection ended”,“attr”:{“remote”:“172.18.0.12:42356”,“uuid”:“23d765d7-49c7-40d6-a67d-1420c2b50696”,“connectionId”:155,“connectionCount”:0}}
postgres-1 | 2025-12-01 21:21:21.043 GMT [2124] LOG: incomplete startup packet
postgres-1 | 2025-12-01 21:21:21.167 GMT [2126] ERROR: database “koboform” already exists
postgres-1 | 2025-12-01 21:21:21.167 GMT [2126] STATEMENT: CREATE DATABASE “koboform” OWNER “kobo”;
postgres-1 | 2025-12-01 21:21:21.244 GMT [2128] ERROR: database “kobocat” already exists
postgres-1 | 2025-12-01 21:21:21.244 GMT [2128] STATEMENT: CREATE DATABASE “kobocat” OWNER “kobo”;

Is there a way for the upgrade script to ignore if the database already exists ( which it should do normally and not try to create new ones!)

Thank you for your help,

@ictm_coraf pinging @stephenoduor for your support!

1 Like

Appreciate the mention. @Kal_Lam , I already reached out to @ictm_coraf