Message database update required

rastal7707 · September 26, 2024, 4:58pm

Infos:

Used Zammad version: 6.3.1-1727329238.012f549d.bookworm
Used Zammad installation type: source
Operating system: Debian 12
Browser + version: Edge 129.0.2792.52 (Offizielles Build) (64-Bit)

Expected behavior:

Database update via web

Actual behavior:

No database update possible via web
Update database > no response
Discard changes > no response
The following error appears in the Edge developer console:
POST https://zammad.xxxxxxxxxx.de/api/v1/object_manager_attributes_execute_migrations 422 (Unprocessable Content)
Even an update according to the instructions or a reboot were unsuccessful. The message remains.

Steps to reproduce the behavior:

New objects created for tickets

fliebe92 · September 26, 2024, 6:38pm

Hi @rastal7707. What is logged in the production.log when you try to update the database via GUI?

rastal7707 · September 27, 2024, 6:32am

Hey @fliebe92,

in the log I can see the following error message:

E, [2024-09-27T08:28:57.706665#591-150240] ERROR -- : PG::StringDataRightTruncation: FEHLER:  Wert zu lang für Typ character varying(3)
 (ActiveRecord::ValueTooLong)
app/models/object_manager/attribute.rb:648:in `block in migration_execute'
app/models/object_manager/attribute.rb:591:in `migration_execute'
app/controllers/object_manager_attributes_controller.rb:69:in `execute_migrations'
app/controllers/application_controller/has_download.rb:17:in `block (4 levels) in <module:HasDownload>'
app/controllers/application_controller/has_download.rb:16:in `block (3 levels) in <module:HasDownload>'
app/controllers/application_controller/has_download.rb:15:in `block (2 levels) in <module:HasDownload>'
app/controllers/application_controller/handles_transitions.rb:16:in `handle_transaction'

Is the message related to the problem?

Best regards
Matthias

fliebe92 · September 27, 2024, 6:59am

Hi @rastal7707. Yes, it is.

rastal7707 · September 27, 2024, 7:34am

Hi @fliebe92,

OK and how can I fix the error?

fliebe92 · September 27, 2024, 8:17am

Hi @rastal7707. You need to identify which value is already stored in which attribute and is causing the issue. I have no clue about your database and cannot help further on, sorry.

rolfschmidt · September 27, 2024, 1:22pm

This might be helpful

zammad run rails r "pp Ticket.where('LENGTH(personalnummer) > 3').pluck(:number, :title)"

rastal7707 · September 28, 2024, 5:57pm

This is the solution. I was able to find the incorrect ticket and correct it. Thanks!