Gitlab fails to update on CentOS if I'm using my own Postgresql database

Downloading Packages:
gitlab-ce-8.1.3-ce.0.el6.x86_64.rpm                                                                          | 343 MB     00:36
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
gitlab preinstall: Backing up GitLab SQL database (excluding Git repositories, uploads)
Dumping database ...
Dumping PostgreSQL database gitlab_production ... pg_dump: server version: 9.4.5; pg_dump version: 9.2.10
pg_dump: aborting because of server version mismatch
Backup failed
[FAILED]
gitlab preinstall:
gitlab preinstall: Backup failed! If you want to skip this backup, run the following command and
gitlab preinstall: try again:
gitlab preinstall:
gitlab preinstall:   sudo touch /etc/gitlab/skip-auto-migrations
gitlab preinstall:
error: %pre(gitlab-ce-8.1.3-ce.0.el6.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package gitlab-ce-8.1.3-ce.0.el6.x86_64
error:   install: %pre scriptlet failed (2), skipping gitlab-ce-8.1.3-ce.0.el6
  Verifying  : gitlab-ce-8.1.3-ce.0.el6.x86_64                                                                                  1/2
gitlab-ce-8.1.2-ce.0.el6.x86_64 was supposed to be removed but is not!
  Verifying  : gitlab-ce-8.1.2-ce.0.el6.x86_64                                                                                  2/2

Failed:
  gitlab-ce.x86_64 0:8.1.2-ce.0.el6                                gitlab-ce.x86_64 0:8.1.3-ce.0.el6

When I skip the backup everything seems to work by doing

touch /etc/gitlab/skip-auto-migrations
yum install gitlab-ce
gitlab-ctl reconfigure

Suggestion: use old config settings during upgrade and not embedded ones?

Title changed from Gitlab fails to update on centos if I'm using my own Postgresql database to Gitlab fails to update on CentOS if I'm using my own Postgresql database

I tried your workflow (touch /etc/gitlab/skip-auto-migrations) but now i have a:

PG::UndefinedTable: ERROR:  relation "audit_events" does not exist
LINE 5:                WHERE a.attrelid = '"audit_events"'::regclass
                                          ^
:               SELECT a.attname, format_type(a.atttypid, a.atttypmod),
                     pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
                FROM pg_attribute a LEFT JOIN pg_attrdef d
                  ON a.attrelid = d.adrelid AND a.attnum = d.adnum
               WHERE a.attrelid = '"audit_events"'::regclass
                 AND a.attnum > 0 AND NOT a.attisdropped
               ORDER BY a.attnum

So I think it is not a good idea :(

@vicendominguez Did you do sudo gitlab-ctl reconfigure after the update?

Hello Olaf, yes i did. Thank you for answering.

I smell the error is harder. Something related to post-install scripts in the RPM. The error is:

http://pastebin.centos.org/36016/

This is a more extended error messages:

http://pastebin.centos.org/36021/

(note: in this second link you find a new error with the sysctl script. It doesn't matter. I t is because of it is impossible to change that values inside of a vz container).

This is still an issue, tested with latest released rpm. This issue occurs when pre-install script within rpm gets executed. It fails to run "gitlab-rake gitlab:backup:create".

The output is generated when pg_dump from older version tries to access more recent database. I guess this is not issue other way around. (i.e. 9.2 can access 9.1 ). If this would be we probably would see a lot of votes on this issue.

RPM should use postgres tools from the system; either in the path or somewhat otherwise directed where these tools should be. It should not provide these tools at all if it is planned to rely on external postgres installation.

As a temporary solution I did replace all postgres binaries in /opt/gitlab/embedded/bin/ with symbolic links to installed ones (/usr/pgsql-9.4/bin/pg_dump, pg_restore, psql) This need to be done before and after update.

I'm seeing the same problem on debian jessie since I moved to an external psql db.

If someone needs help then copying pg_dump fixes this. Note that you need to do it everytime you update and if your postgre installation is located elsewhere then you can find it with

• sudo whereis pg_dump
• sudo cp /usr/bin/pg_dump /opt/gitlab/embedded/bin/

mentioned in issue #17211 (closed)

mentioned in issue omnibus-gitlab#1456

Status changed to closed

It's been a while (and several new releases) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.

Thank you for using GitLab!

It's been a while (and several new releases) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.

Thank you for using GitLab!

mentioned in merge request !14785