Hi Sytse, Thanks for your support.
I've compared my GL7 database to an newly installed GL7 (using backup functionality). I found some strange stuff, try to manually clean and restore them. That solve the homepage problem! But when I want to edit the project properties, I don't have error 500 anymore, but an red popups "Import status is invalid" and no error in production.log. Regards, Wolfy Le jeudi 26 juin 2014 12:13:52 UTC+2, Sytse Sijbrandij a écrit : > > Hi Wolfy, > > I'm sorry that you're experiencing problems with GitLab. > > You are doing the hardest possible migration one can do but the steps > you took look fine. > > The problem looks like a difficult puzzle. the database schema is > messed up, but I cannot tell when that happened. > > Best regards, > Sytse > > > > > On Wed, Jun 25, 2014 at 5:58 PM, mickael micallef <[email protected] > <javascript:>> wrote: > > Hi everyone, > > > > I've previously installed Gitlab 6.0 on an Debian 7.5 using Bitnami and > > update it many times (maybe the wrong way?), but I now want to switch to > an > > Omnibus installation. > > > > My last Bitnami update was Gitlab 6.9.0, so I've: > > - build an new server using Centos 6.5 > > - backup data > > - convert mysql -> postgresql > > - install Omnibus Gitlab 6.9.0 > > - restore backup > > - configure > > - install omnibus 7.0 > > - configure > > > > Everything seems to works, but one of my project have many error 500. > > When I access the project home page, my production.log say: > > > >> Started GET "/internal/myproject" for 127.0.0.1 at 2014-06-25 > 10:33:02 > >> -0400 > >> Processing by ProjectsController#show as HTML > >> Parameters: {"id"=>"internal/myproject"} > >> Completed 500 Internal Server Error in 68ms > >> > >> ActionView::Template::Error (undefined method `+' for nil:NilClass): > >> 58: > >> 59: - if @project.gitlab_ci? > >> 60: %hr > >> 61: = link_to @project.gitlab_ci_service.builds_path do > >> 62: = image_tag > @project.gitlab_ci_service.status_img_path, > >> alt: " > >> build status" > >> app/models/project_services/gitlab_ci_service.rb:55:in `builds_path' > >> app/views/projects/show.html.haml:61:in > >> `_app_views_projects_show_html_haml__2 > >> 631361046872696347_38652420' > >> app/controllers/projects_controller.rb:69:in `block (2 levels) in > show' > >> app/controllers/projects_controller.rb:63:in `show' > > > > > > I also cannot save any change to the project settings: > > > >> Started PATCH "/internal/myproject" for 127.0.0.1 at 2014-06-25 > 11:48:54 > >> -0400 > >> Processing by ProjectsController#update as JS > >> Parameters: {"utf8"=>"V", "project"=>{"name"=>"Replaced", > >> "description"=>"Replaced", "default_branch"=>"master", > "visibility_level" > >> =>"0", "label_list"=>"", "issues_enabled"=>"1", > >> "merge_requests_enabled"=>"1", " > >> wiki_enabled"=>"1", "snippets_enabled"=>"0"}, "commit"=>"Save changes", > >> "id"=>"internal/myproject"} > >> Completed 500 Internal Server Error in 48ms > >> > >> NoMethodError (undefined method `import_status' for > >> #<Project:0x00000004440170>) > >> : > >> app/services/projects/update_service.rb:16:in `execute' > >> app/controllers/projects_controller.rb:32:in `update' > > > > > > > > Has anyone ever had this error? > > > > > > # gitlab-rake gitlab:check RAILS_ENV=production > > say: > >> > >> ... > >> > >> 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. > >> ... > > > > > > # gitlab-rake db:migrate RAILS_ENV=production > > say: > >> > >> == 20140122112253 CreateMergeRequestDiffs: migrating > >> ========================== > >> -- create_table(:merge_request_diffs) > >> rake aborted! > >> StandardError: An error has occurred, this and all later migrations > >> canceled: > >> > >> PG::Error: ERROR: relation "merge_request_diffs" already exists > >> : CREATE TABLE "merge_request_diffs" ("id" serial primary key, "state" > >> character > >> varying(255) DEFAULT 'collected' NOT NULL, "st_commits" text, > "st_diffs" > >> text, > >> "merge_request_id" integer NOT NULL, "created_at" timestamp, > "updated_at" > >> timest > >> amp) > >> ActiveRecord::StatementInvalid: PG::Error: ERROR: relation > >> "merge_request_diffs > >> " already exists > >> : CREATE TABLE "merge_request_diffs" ("id" serial primary key, "state" > >> character > >> varying(255) DEFAULT 'collected' NOT NULL, "st_commits" text, > "st_diffs" > >> text, > >> "merge_request_id" integer NOT NULL, "created_at" timestamp, > "updated_at" > >> timest > >> amp) > >> > >> PG::Error: ERROR: relation "merge_request_diffs" already exists > >> > >> Tasks: TOP => db:migrate > > > > > > > > Did I crashed my database, or it can be recovered? > > > > Thanks in advance, cheers, > > Wolfy > > > > -- > > 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 [email protected] <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/gitlabhq/6ac9834d-66b1-4892-99a9-5da4fb8fc8ce%40googlegroups.com. > > > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/06760321-b4a7-440f-9439-f1f930740ca8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
