NethServer Version: 8
Module: Zammad
Good morning @mrmarkuz,
I was just about to update Zammad. It isn’t working and keeps crashing with an error message. See screenshot…
Sorry, the app is broken, see ns8:applications:zammad [NethServer & NethSecurity]
It used bitnami images which aren’t available anymore. I need to update it to use other images.
1 Like
OK… there was also an update for Twenty CRM. The update went smoothly. But now I can’t log in anymore. I can change my password using the reset link, but I can’t log in with the new password afterwards.
2026-03-15T17:37:30+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:30.499 UTC [5110] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE twenty REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2026-03-15T17:37:30+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:30.500 UTC [5109] WARNING: database “twenty” has a collation version mismatch
2026-03-15T17:37:30+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:30.500 UTC [5109] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2026-03-15T17:37:30+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:30.500 UTC [5109] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE twenty REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2026-03-15T17:37:45+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:45.006 UTC [5111] WARNING: database “twenty” has a collation version mismatch
2026-03-15T17:37:45+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:45.006 UTC [5111] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2026-03-15T17:37:45+01:00 [1:twenty1:postgresql-app] 2026-03-15 16:37:45.006 UTC [5111] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE twenty REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2026-03-15T17:37:50+01:00 [1:twenty1:agent@twenty1] task/module/twenty1/e7bc4351-8257-4115-92b3-7999c0416977: get-status/20read is starting
2026-03-15T17:37:50+01:00 [1:twenty1:agent@twenty1] task/module/twenty1/d7039897-b184-494a-a270-ab926b8ee3fd: get-name/50get_name is starting
2026-03-15T17:37:50+01:00 [1:twenty1:agent@twenty1] task/module/twenty1/9dc1bd10-44a9-4b1a-b2b3-2e45be37ab49: get-configuration/20read is starting
2026-03-15T17:37:51+01:00 [1:twenty1:agent@twenty1] task/module/twenty1/9dc1bd10-44a9-4b1a-b2b3-2e45be37ab49: action “get-configuration” status is “completed” (0) at step validate-output.json
2026-03-15T17:37:51+01:00 [1:twenty1:agent@twenty1] task/module/twenty1/d7039897-b184-494a-a270-ab926b8ee3fd: action “get-name” status is “completed” (0) at step 50get_name
2026-03-15T17:37:51+01:00 [1:twenty1:agent@twenty1] task/module/twenty1/e7bc4351-8257-4115-92b3-7999c0416977: action “get-status” status is “completed” (0) at step validate-output.json
1 Like
Thanks @transocean, now I found the issue.
I updated my repo yesterday to allow automatic releases which pushed wrong non-working updates of twenty, wg-easy and zammad. It’s fixed now, sorry for any inconvenience.
2 Likes