Could you edit the update script to comment out the steps that were done
during the first attempt? And run that, effectively resuming the update?
On Sep 18, 2016 9:35 AM, "Daniel Le Berre" <daniel.lebe...@gmail.com> wrote:
> Dear all,
> I have been updating manually gitlab from source each month for two years
> and half without problem.
> Last June, while updating to gitlab 8.9, I did not update properly mysql
> rights so the database migration failed.
> I switched back to gitlab 8.8 branch on git, and could run properly my
> gitlab instance.
> So far, so good.
> However, I made the mistake to avoid restoring the database to before the
> migration (I thought the migration was a single transaction).
> Since then, any update process fails because the migration process finds
> already existing tables or columns in the database.
> Is there any way to resume the database migration process?
> I am willing to switch to omnibus at some point to avoid issues like this
> in the future, but I need a clean mysql database anyway to do so.
> Any help on this would be much appreciated.
> 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/ms
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.