Infos:
- Used Zammad version: v6.3.1
- Used Zammad installation type: Package Install
- Operating system: Ubuntu 24.04 LTS
- Browser + version: Multiple, Chrome, Firefox, Edge
Looking for more general guidence here rather than help with a specific item here, but here goes;
Expected behavior: Currently are attempting to perform a import from Kayako and we are seeing the following error in the window that displays the status updates;
‘’‘{undefined local variable or method `e’ for Sequencer::Unit::Import::Kayako::Request:Class}‘’’
In looking into the system it appears to have properly imported the Groups, Organizations, and Users, but get’s stuck on the tickets showing a progress of 3168/3700 tickets - and no matter how long we let it sit no further progress is shown.
Running a command line to check the status of the update as per the documentation shows the following;
‘’‘{
root@support:/var/log/zammad# zammad run rails r “pp ImportJob.find_by(name: ‘Import::Kayako’)”
#<ImportJob:0x00007fee2071efb0
id: 1,
name: “Import::Kayako”,
dry_run: false,
payload: {},
result:
{“Groups”=>{“skipped”=>0, “created”=>9, “updated”=>0, “unchanged”=>0, “failed”=>0, “deactivated”=>0, “sum”=>9, “total”=>9},
“Organizations”=>{“skipped”=>0, “created”=>69143, “updated”=>0, “unchanged”=>0, “failed”=>0, “deactivated”=>0, “sum”=>69143, “total”=>69143},
“Users”=>{“skipped”=>0, “created”=>247573, “updated”=>0, “unchanged”=>0, “failed”=>0, “deactivated”=>0, “sum”=>247573, “total”=>247573},
“Tickets”=>{“skipped”=>7, “created”=>3607, “updated”=>4, “unchanged”=>0, “failed”=>0, “deactivated”=>0, “sum”=>3618, “total”=>3700},
“error”=>"undefined local variable or method `e’ for Sequencer::Unit::Import::Kayako::Request:Class"},
started_at: Wed, 21 Aug 2024 22:28:48.223000000 UTC +00:00,
finished_at: Thu, 22 Aug 2024 09:06:28.987000000 UTC +00:00,
created_at: Wed, 21 Aug 2024 22:28:48.006000000 UTC +00:00,
updated_at: Thu, 22 Aug 2024 09:06:28.988000000 UTC +00:00>
}‘’’
In looking into the production log I can find the specific error listed as being a in the production log and that points to a specific ticket but there’s nothing special about it - so I have removed the ticket, rolled back the server and started the process again, however I wonder is there a better way to handle this type of situation and avoid having to restart the entire migration process over? I’ve got 500k+ tickets that we are looking at having to move and if it’s going to be restarting the process this frequently this is going to be a long haul to get things moved over.
Any better suggestions for managing that migration process?
