Hi, Stan! Thanks for pointing me in the right direction: the migration was indeed not fully completed. After running "gitlab-rake gitlab:check" I noticed that the DB migration was not done. The output was:
All migrations up? ... no Try fixing it: sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production Please fix the error above and rerun the checks. After running "gitlab-rake db:migrate RAILS_ENV=production" and restarting gitlab everything started to work. Thank you for your help! PS: "gitlab-ctl tail" was printing what Urs initially reported "500 NoMethodError (undefined method `wiki_page_events='" On Friday, April 29, 2016 at 5:27:42 PM UTC+3, Stan Hu wrote: > > Make sure all your migrations are up via "sudo gitlab-rake gitlab:check". > > Could you post the error logs from running "sudo gitlab-ctl tail"? > > > > On Fri, Apr 29, 2016 at 1:27 AM, Razvan Crainea <razvan....@gmail.com > <javascript:>> wrote: > >> >> >> On Thursday, April 28, 2016 at 10:50:03 PM UTC+3, Urs Liska wrote: >>> >>> >>> >>> 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 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. >>> >> >> I upgraded to the latest version, but still does not work. >> >> Actually I am running on jessie, so I don't have passanger* packages, >> only ruby-passenger and ruby-passenger-doc. Could this be an issue? Is the >> new version of GitLab using them? >> >> Thanks, >> Răzvan >> >> -- >> 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+u...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/52674024-1e2b-41de-ad0f-d52663aab580%40googlegroups.com >> >> <https://groups.google.com/d/msgid/gitlabhq/52674024-1e2b-41de-ad0f-d52663aab580%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/81596747-cb17-4bb7-ba27-9048f8f3b6e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
