Updating Zammad


Before updating to a new version, you may want to have a look into the official release notes. These will provide further information on new feature and fixes, but also technical remarks that may be relevant during an upgrade!

Step 1: Ensure dependencies

Before proceeding, double-check that your system environment matches Zammad’s requirements.

Step 2: Stop Zammad
$ systemctl stop zammad
Step 3: Backup Zammad

See Backup and Restore for more information.

Step 4: Clear Zammad cache
$ zammad run rails r "Cache.clear"
Step 5: Update Zammad
$ apt update
$ apt upgrade


The package comes with maintenance scripts that will run regular tasks during updates for you.

Do not run Zammad updates unattended and always have a look on the outputs these helper scripts generate. Ignoring said output may lead to incomplete updates that may corrupt data or lead to issues you find way too late.
Step 6: Run required extra steps

Extra steps needed for updates are mentioned in our release news.

Updating Elasticsearch may be relevant in this step.

Step 7: Log into Zammad

Yes, that’s it!

Updating Elasticsearch


Updating Elasticsearch does not automatically update it’s plugins! This usually isn’t an issue if Zammad is being updated right after Elasticsearch.

If you want to upgrade your elasticsearch installation, please take a look at the elasticsearch documentation as it will have the most current information for you.

If, for whatever reason, you need to rebuild your search index after upgrading, use:

$ zammad run rake searchindex:rebuild


This step may fail if Zammad is under heavy load: Elasticsearch locks the indices from deletion if you’re pumping in new data, like receiving a new ticket. (This only applies to single-node deployments, not clusters.)

If it does, try killing Zammad first:

$ systemctl stop zammad
$ zammad run rake searchindex:rebuild
$ systemctl start zammad