Migration from Zammad 6.5.0 to 7.0.1 (Ubuntu 20.04 → 24.04) – Elasticsearch Reindex Fails, Ticket Search Broken

Technical assistance
1

Note: This post was generated with the assistance of AI.

Used Zammad version:
6.5.0-1743595505.adab1853.focal

Used Zammad installation type:
package (on Ubuntu 20.04)

Operating system:
Ubuntu 20.04

Attachment storage:
filesystem (not database)

Database:

  • Old server (Ubuntu 20.04): psql (PostgreSQL) 12.22 (Ubuntu 12.22-0ubuntu0.20.04.4)
  • New server (Ubuntu 24.04, Elasticsearch 9): psql (PostgreSQL) 16.14 (Ubuntu 16.14-0ubuntu0.24.04.1)
  • New server (Ubuntu 24.04, Elasticsearch 7.17.29): psql (PostgreSQL) 16.14 (Ubuntu 16.14-0ubuntu0.24.04.1)

Browser + version:
(Not specified, as this issue is server-side)

Expected behavior:

After migrating from Zammad 6.5.0 to 7.0.1 (Ubuntu 24.04, Elasticsearch 9.4.1), the ticket search should work correctly, and all data should be indexed properly.

Actual behavior:

  • The migration of data from the old Zammad server to the new one (Ubuntu 24.04, Zammad 7.0.1-1781094672.f87b427.ubuntu24, Elasticsearch 9.4.1) was successful.
  • However, when running zammad run rake zammad:searchindex:rebuild, an error occurs that I cannot resolve, resulting in ticket search not working.
  • I ran /opt/zammad/contrib/packager.io/postinstall.sh after the migration to ensure all adjustments were applied, but the reindex issue persisted.
  • In another ticket, the request was not addressed, which reinforces my suspicion that the issue might be Elasticsearch-related. Nevertheless, I would still appreciate feedback here.

Steps to reproduce the behavior:

  1. Set up a new VM with Ubuntu 24.04.
  2. Install Zammad 7.0.1-1781094672.f87b427.ubuntu24 and Elasticsearch 9.4.1 (or 7.17.29).
  3. Migrate data from the old Zammad (6.5.0, Elasticsearch 7.17.6) to the new server.
  4. Run /opt/zammad/contrib/packager.io/postinstall.sh to finalize the migration.
  5. Run zammad run rake zammad:searchindex:rebuild
  6. Result: An error message appears, and the reindex fails. Ticket search does not work.
  7. Alternative attempt: Set up a new Ubuntu 24.04 server with Zammad 7.0.1 and Elasticsearch 7.17.29, then upgrade Elasticsearch to 9.4.1.
  8. Result: Reindex still fails with the same error, ticket search remains broken.

Additional Notes:

I already checked the following forum posts, but they did not help resolve my issue:

Note:
I am unsure whether this is a Zammad or Elasticsearch issue. If this is the wrong place to ask, please let me know, and I will post in the Elasticsearch forum instead. If you need the exact error message, I can provide it.

2

But what is the error you receive when trying to rebuilt…?
So much text and description, but no error message.

1 Like
3

I might found the answer because the reindex didn’t wrote

“rake aborted!”

yet.

There are “only” 200k tickets to reindex so it probably takes the whole businesses-day.

If this was the answer if write it in here.

Hint:

this and some database changes.

4

Did you set up and generate an ES user and password to be used with Zammad?

5

i redid
the “Set Elasticsearch user:”

rested the Elasticsearch and placed it in the es_password

es_url was not set to https://localhost:9200 so i stetted it to it

es_ssl_verfy was false stetted it to true.

Disclaimer it is still going and not done yet so idk if it really did the trick.

6

the reason why i didn’t do those steps was cause i thought when i setup the zammad server first (pre migration) i did those steps and i thought that those parameters get saved and not overwritten so i didn’t checked them again after i migrated.

7

These information are indeed stored in your databaw. But ES was bunped from ES 7 earlier this year and since then requires user authentication.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.