# Upgrade from 6.2 to 6.3 failed

**URL:** https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884
**Category:** Technical assistance
**Created:** [July 8, 2024, 1:14pm UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884 "2024-07-08T13:14:25Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Travis](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/bbce88/32.png) [@Travis](https://community.zammad.org/u/Travis)
#### Post date: [July 8, 2024, 1:14pm UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/1 "2024-07-08T13:14:25Z")

</div>

### Infos:

- Used Zammad version: 6.2.0-1712728678.1fb595f2.bookworm
- Used Zammad installation type: package
- Operating system: Debian GNU/Linux 12 (bookworm)

### Expected behavior:

Zammad version changing from 6.2 to 6.3

### Actual behavior:

Apt fails to install / update the package “zammad”

### Steps to reproduce the behavior:

```auto
systemctl stop zammad
/opt/zammad/contrib/backup/zammad_backup.sh
zammad run rails r "Rails.cache.clear"
apt update
apt upgrade

```

* * *

I’m trying to update the package version of Zammad from 6.2 to 6.3, at the end of the “apt upgrade” process, I see…

```auto
Errors were encountered while processing:
 /tmp/apt-dpkg-install-onGGSF/37-zammad_6.3.1-1720156707.17f20fad.bookworm_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

```

The dpkg log looks like it’s claiming zammad is installed, but I can’t reach it’s webui anymore after doing the steps above.

```auto
2024-07-08 08:08:12 upgrade zammad:amd64 6.2.0-1712728678.1fb595f2.bookworm 6.3.1-1720156707.17f20fad.bookworm
2024-07-08 08:08:12 status half-configured zammad:amd64 6.2.0-1712728678.1fb595f2.bookworm
2024-07-08 08:08:12 status unpacked zammad:amd64 6.2.0-1712728678.1fb595f2.bookworm
2024-07-08 08:08:12 status half-installed zammad:amd64 6.2.0-1712728678.1fb595f2.bookworm
2024-07-08 08:08:13 status unpacked zammad:amd64 6.2.0-1712728678.1fb595f2.bookworm
2024-07-08 08:08:48 status installed zammad:amd64 6.2.0-1712728678.1fb595f2.bookworm

```

I also tried the solution in [this thread](https://community.zammad.org/t/failed-to-update-from-6-2-to-6-3/14363), which mentioned using the -f flag for apt, this causes the package to “successfully install”, however, I then get stuck at a Zammad branded 500 page with the Zammad bird in a birdhouse.

---

<div class="post-metadata">

### Author: ![Thomasvanhoof](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@Thomasvanhoof](https://community.zammad.org/u/Thomasvanhoof)
#### Post date: [July 9, 2024, 9:01am UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/2 "2024-07-09T09:01:26Z")

</div>

Ye got the same problem here ☹

Did you also get an elasticsearch update?

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [July 9, 2024, 10:29am UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/3 "2024-07-09T10:29:12Z")

</div>

> [@Travis](#):
>
> `E: Sub-process /usr/bin/dpkg returned an error code (1)`

Indicates the installer stopped. Our pre install does provide a feedback output in your console which should be higher.

If I’d have to guess: Your database server was not available during upgrade.

---

<div class="post-metadata">

### Author: ![Thomasvanhoof](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@Thomasvanhoof](https://community.zammad.org/u/Thomasvanhoof)
#### Post date: [July 9, 2024, 1:25pm UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/4 "2024-07-09T13:25:01Z")

</div>

This was one of the things that showed up I think yes.

Still not fixed from the bug that was preventing upgrade of 6.0 to 6.1?

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [July 9, 2024, 1:27pm UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/5 "2024-07-09T13:27:49Z")

</div>

You’re supposed to upgrade Zammad without upgrading your database server at the same time. The thing that changed is that the process is telling you that you’ve been a “bad boy” by ignoring this.

---

<div class="post-metadata">

### Author: ![Thomasvanhoof](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@Thomasvanhoof](https://community.zammad.org/u/Thomasvanhoof)
#### Post date: [July 9, 2024, 2:02pm UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/6 "2024-07-09T14:02:34Z")

</div>

Then what is the procedure?

The database is on the same machine 🙂

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [July 9, 2024, 3:05pm UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/7 "2024-07-09T15:05:43Z")

</div>

- Verify that your database server has no update open
- -if- stop Zammad and update the database server directly and start Zammad after
- Apply the rest of the updates

How that’s done depends on your OS at some points. As you’re administering it - you’ll know better than me most likely.

---

<div class="post-metadata">

### Author: ![Travis](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/bbce88/32.png) [@Travis](https://community.zammad.org/u/Travis)
#### Post date: [July 10, 2024, 3:24am UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/8 "2024-07-10T03:24:40Z")

</div>

> [@MrGeneration](#):
>
> You’re supposed to upgrade Zammad without upgrading your database server at the same time.

Thank you, I changed the procedure I was following to…

```auto
systemctl stop zammad
/opt/zammad/contrib/backup/zammad_backup.sh
zammad run rails r "Rails.cache.clear"
apt-mark hold zammad
apt update
apt upgrade
apt-mark unhold zammad
apt update
apt upgrade

```

…so that way I was upgrading “everything else”, and the second upgrade did only the zammad package, which resolved my issue.

It was my first upgrade that didn’t “just work” so I was caught by surprise here and wouldn’t have expected it to care about the other 60 or so packages that had upgrades available since I last apt `update && apt upgrade` a couple weeks ago.

---

<div class="post-metadata">

### Author: ![Thomasvanhoof](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@Thomasvanhoof](https://community.zammad.org/u/Thomasvanhoof)
#### Post date: [July 10, 2024, 7:01am UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/9 "2024-07-10T07:01:18Z")

</div>

I will give this a try this evening 🙂

Thank you

---

<div class="post-metadata">

### Author: ![Thomasvanhoof](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@Thomasvanhoof](https://community.zammad.org/u/Thomasvanhoof)
#### Post date: [July 11, 2024, 7:21am UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/10 "2024-07-11T07:21:09Z")

</div>

> [@Travis](#):
>
> ```auto
> systemctl stop zammad
> /opt/zammad/contrib/backup/zammad_backup.sh
> zammad run rails r "Rails.cache.clear"
> apt-mark hold zammad
> apt update
> apt upgrade
> apt-mark unhold zammad
> apt update
> apt upgrade
> 
> ```

This worked 🙂

Thank you

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [July 18, 2024, 7:22am UTC](https://community.zammad.org/t/upgrade-from-6-2-to-6-3-failed/14884/11 "2024-07-18T07:22:04Z")

</div>

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