Error Run `rails db:migrate` to update your database then try again


  • Used Zammad version: 2.9.0
  • Used Zammad installation source: Docker-Compose
  • Operating system: Ubuntu 18.04
  • Browser + version: Chrome

Expected behavior:

Migrated from one server to a new one, copied over the compose files + docker volumes and then Zammad crashed at the start

Actual behavior:

docker logs zammaddockercompose_zammad-init_1

initialising / updating database…
creating database…
Database ‘zammad_production’ already exists
seeding database…
Run rails db:migrate to update your database then try again.
I, [2019-04-18T20:28:41.180534 #19-46951470878560] INFO – : Setting.set(‘product_logo’, “e3ba71d37195ea8aabeddccd858235c0.png”)
You have 1 pending migration:
20190408000001 Issue2541FixNotificationEmailWithoutBody

and if I go into the Rails Container and execute “rails db:migrate” I get the following error:

I, [2019-04-18T20:37:20.653382 #2013-47459374485340] INFO – : Migrating to Issue2541FixNotificationEmailWithoutBody (20190408000001)
== 20190408000001 Issue2541FixNotificationEmailWithoutBody: migrating =========
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:

Invalid perform, recipient is missing!

Steps to reproduce the behavior:

@monotek can you possibly help here?

thanks for getting back to me. I fixed it just today by going back to Zammad 2.8, removed a wrongly configured Trigger workflow which had no eMail Body configured, which was fixed in Zammad 2.9 with this ( However the problem is that this fix just throws out the error above and then Zammad Init just stops and repeats the same steps over and over again without Zammad launching. So the only fix for me was to go back to 2.8, remove the wrong trigger and upgrade to 2.9 again

Thanks for getting back to us.
We might need to think about a better migration here.

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