Error 502 after Postsql update

I have fixed my problem. Maybe someone will be helped by this another time.

Moral of the story: ALWAYS UPGRADE POSTGRES CORRECTLY

I was running Postgresql 9.2 and the new Zammad 5.0 needs Postgresql 9.3 or higher. I have no experience with this so I simply add the repository and upgrade PostgreSQL.

After several days of errors:

Error #1: 502 when trying to access the website
Error #2: Zammad role does not exist
Error #3: database zammad_production does not exist. Can’t create a database.
Error #4: Postsql-14 failed to restart. Journalctl -xe would show zammad_websocket_1 can not connect
etc., etc. etc…Lots of errors.

After learning more and more about Postgres and how it relates to Zammad. I realize that I need to have Postgresql 9.2 in order to migrate my data. But…Postgresql doesn’t support 9.2 anymore but you need it to do the migration of your data… Days later I find out that CentOS 7 Base Repository is where you get 9.2 and before I installed Postgresql 14 I was instructed to do exclude=postgresql* in my repository base file. I had to remove that and I was able to reinstall PostgreSQL 9.2.

Once that was installed I needed to migrate the old database data to the new folder for that I used this guideCentOS: Upgrade PostgreSQL from 9.2 to 9.6. I was going from 9.2 - 14 but it still worked with some obvious changes to the names of files.

Then after that, I was still getting the error zammad_production database does not exist. At this point, I have to apologize because I can’t remember exactly what I used to fix this but I’m pretty sure I did

su - Postgres

and then as a Postgres user, I created the zammad_production database. I will put some links that were useful to figuring this out below.
Create Database Permissions

Oh, and I did have to manually create the data folder for the new Postgresql-14 so here’s a guide for that. unable-to-start-posgtresql-the-reason-isnt-clear

Sorry if this isn’t as helpful there was a lot of forums I read and it’s a big blur. But before you upgrade PostgreSQL. Back up and then follow someone’s guide who knows what they are doing.

2 Likes