Am 28.04.2016 um 11:56 schrieb Razvan Crainea:
>
>
> On Thursday, April 28, 2016 at 12:29:29 AM UTC+3, Urs Liska wrote:
>
>     Hi Maximilian,
>
>     thanks for considering my issue.
>
>     Am 27.04.2016 um 20:13 schrieb 'Maximilian Kindshofer' via GitLab:
>     >
>     > Am Montag, 25. April 2016 11:14:04 UTC+2 schrieb Urs Liska:
>     >
>     >     I could resolve the issue (if it is the same) by following
>     this message:
>     >
>     >     |You must enable the pg_trgm extension. You can do so by
>     running
>     >     "CREATE EXTENSION pg_trgm;" as a PostgreSQL super user, this
>     must be
>     >     done for every GitLab database.|
>     >
>     >     after this it gitlab worked again after reconfigure and restart
>
>     Do you have any further information *why* this could be the same
>     issue?
>     Looking at my error message, your quoted message and the docs at
>     http://www.postgresql.org/docs/9.1/static/pgtrgm.html
>     <http://www.postgresql.org/docs/9.1/static/pgtrgm.html> that seem to
>     support that assumption.
>
> Hi, eveyrbody!
>
> I am having the same issue as Urs, after upgrading from 8.6.5-ce to
> 8.7.0-ce.
> I tried Maximilian's workaround, but it does not work (the extension
> was already there anyway).
> Backporting to 8.6.7-ce works without any issues. Any other ideas we
> could try?
>
> Thanks,
> Răzvan

FYI:

I just ran apt-get update/upgrade on my server, and the following
packages were updated:
nginx-common nginx-extras passenger passenger-dev passenger-doc

Now I can access the Gitlab installation again.

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/8da6ba38-b6e3-05c1-6bc4-195b0db43508%40ursliska.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to