At the very end of the install of 8.5.x over 8.4.x just now I saw:

gitlab: 
Found /etc/gitlab/skip-auto-migrations, exiting...


On Wednesday, February 24, 2016 at 11:56:18 AM UTC, Stan Hu wrote:
>
> Those commands should work. They did for me for 8.5.0.
>
> I usually keep an eye out that the migrations ran during the install. It 
> always pays to verify everything checks out:
>
> sudo gitlab-rake gitlab:check
>
>
That then produced:

All migrations up? ... no
  Try fixing it:
  sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production

 

> If the migrations haven't been applied, I usually just run:
>
> sudo gitlab-ctl reconfigure
> sudo gitlab-ctl restart
>
>
Gitlab seemed to run okay, but I got a 500 error on an issues page. 

Thinking it was a migrations problem, I ran your two commands rather than 
the suggestion on "Try fixing it", and now it seems okay. The gitlab:check 
task now says all migrations are up. But why is this failing in the first 
place? Have gitlab oversimplified the upgrade instructions?
 
Is it because I have a  /etc/gitlab/skip-auto-migrations file?

Thanks for the help, the check task looks very useful...

B




>
> On Wed, Feb 24, 2016 at 12:57 AM, Barry Rowlingson <b.rowl...@gmail.com 
> <javascript:>> wrote:
>
>> I'm running gitlab CE from the omnibus distribution via the 
>> repositories.  I'm keeping up to date with the 8.x releases.
>>
>> But last time I updated, something didn't go quite right. As on the 
>> update page, I did:
>>
>> sudo apt-get update 
>> sudo apt-get install gitlab-ce
>>
>>
>> but on accessing our gitlab pages there was a problem with public repos 
>> due to a migration that hadn't happened. I submitted a bug report which was 
>> very quickly spotted and fixed thanks to the gitlab staff!
>>
>> So now there's a new 8.x release, and I'm worried things will go wrong 
>> again. Are those two commands really sufficient? Should I shut down all the 
>> services first and start up again afterwards?
>>
>>
>> -- 
>> 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/8fbd6632-5aa9-4acd-9b30-7bc16c13f3d5%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/gitlabhq/8fbd6632-5aa9-4acd-9b30-7bc16c13f3d5%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/ffc0015b-629d-47f3-8238-28553d267d32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to