Update Debian, Elasticsearch Zammad

Technical assistance
1

Hello,

I’am new at the company i am working for and not very familiar with Zammad, now i have to update our Zammad VM but did not sure about the right order. And have the fear that elastic search will cause the most problems during the update.

Basically i have the following system:

  • Debain Buster (latest patches installed)
  • Zammad 6.1.0-1701845240.5a81e629.buster (Package installation)
  • Elastic Search 6.8.23 (Package installation)

I like to update:

  • Debian Buster to Bullseye
  • Zammad 6.1 to 6.2 including latest elastic search without breaking the Database

In which order i should do the updates and what steps i should care of not destroy any depencies?

I am at beginners level in Linux, so sorry for my question it is hard to understand all the different Manuals and sort the steps in the right order.

the good thing, since it is a vm and i’ve cloned the production system i have the magic of snapshots :smiley: if things are going wrong… and there will…

Kind regards,

2

First RUN FAILED:

Update Debian Buster to Bullseye by changing the sources.list
result in uninstalled Zammad.

Should i modify the sources.list.d/zammad.list file which was created by dl,packager,io ?

dl,packager,io/srv/deb/zammad/zammad/stable/debian 10 main

to

dl,packager,io/srv/deb/zammad/zammad/stable/debian 11 main

3

Second RUN FAILED:

Keeping Debian Buster but first update Elasticsearch from 6.8 to 7.17 following the Manual result in failing to start Elastic Search after Update

4

Hi Toni!

Why don’t you install a new server (VM) with new debian,
install zammad in the same version as on the old system (but don’t configure it).
Then you create a backup of the old system,
copy it to the new server,
turn off the old server
configure the new server with the same IP-address and hostname as the old server and
then restore the zammad backup,
and if everything works, then update the zammad version from 6.1 to 6.2

maybe you have to run
zammad run rake searchindex:rebuild
after the restore

1 Like
5

Hi Datenschuft,

thanks for the fast ansfer,
if i am wasting to much time, it will be an Option but in my opinion it is also frustrating setting up a new server every patchnight instead of update them simply and fast. :smiley:

6

I wouldn’t say, that a Debian dist-upgrade is a patch run.
Upgrading zammad from 6.1.to 6.2 is a simple patch run (apt full-upgrade).
I suggest to upgrade debian or zammad first and do the other part later.

7

I have to step in a bit here. A distribution upgrade is potentially simpler, yes, but definitely not fast. If not done carefully, you’ll brick your system and in worst case your Zammad instance.

If you’re not too familiar with linux administration (and that is absolutely fine!), the backup and restoration part definitely is the “easier” and safer approach.

1 Like
8

Okay i’ll keep that in mind. For teaching myself i will try to update step by step but if all will not working i’ll setup a new machine and following the Backup / Restore Path described in the manual.

In the midtime i was able to Update Debian 10 to 11 with outcommend the Zammad in the ressource.list.d/zammad.list, then Update Zammad from 6.1 to 6.2 but ran into problems with postgresql 9.6 and elastic search. Which i will take care now or get one step back and:

  1. Update Debian 10 to 11
  2. Update Postgresql minimum to 10
  3. Update Zammad
  4. Update Elastic Search

Thanks for all your Help by now.

9

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