Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #7618

Closed
Open
Created 10 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Gitlab Crashes when clicking merge requests (error 500)

Closed

Gitlab Crashes when clicking merge requests (error 500)

Created by: spuder

When a user attempts to make a merge request, gitlab returns an error 500

Looking at the log, it shows the following error

Started POST "/main/builder/merge_requests" for 127.0.0.1 at 2014-08-27 11:25:23 -0600
Processing by Projects::MergeRequestsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"xxxxxxxxxxx", "merge_request"=>{"title"=>"Develop", "description"=>"testing merge requests", "assignee_id"=>"", "milestone_id"=>"", "source_project_id"=>"79", "target_project_id"=>"79", "target_branch"=>"master", "source_branch"=>"develop"}, "project_id"=>"main/builder"}
Completed 500 Internal Server Error in 760ms

RuntimeError (expected SCALAR, SEQUENCE-START, MAPPING-START, or ALIAS):
  app/models/merge_request_diff.rb:146:in `reload_diffs'
  app/models/merge_request_diff.rb:44:in `reload_content'
  app/services/merge_requests/create_service.rb:9:in `execute'
  app/controllers/projects/merge_requests_controller.rb:96:in `create'
  app/controllers/application_controller.rb:59:in `set_current_user_for_thread'

This is reproducable everytime, It only happens on 1 project.

I won't paste the output of the rake tests, however everything looks correct.

cd /home/git/gitlab/ && sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
cd /home/git/gitlab/ && sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

I've verified that the repositories directory is clean, the gitlab-satellites directory is clean.

Running gitlab 6.9. What else can I check?

root@gitlab:/home/git/gitlab# sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

System information
System:     Ubuntu 12.04
Current User:   git
Using RVM:  no
Ruby Version:   1.9.3p0
Gem Version:    2.4.1
Bundler Version:1.5.3
Rake Version:   10.3.1
Sidekiq Version:2.17.0

GitLab information
Version:    6.9.2
Revision:   8759577
Directory:  /home/git/gitlab
DB Adapter: mysql2
URL:        https://gitlab.foobar.com
HTTP Clone URL: https://gitlab.foobar.com/some-project.git
SSH Clone URL:  git@gitlab.foobar.com:some-project.git
Using LDAP: yes
Using Omniauth: no

GitLab Shell
Version:    1.9.4
Repositories:   /home/git/repositories/
Hooks:      /home/git/gitlab-shell/hooks/
Git:        /usr/bin/git

Linked issues
0


  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
Assign to
Milestone
No milestone
None
None
Time tracking
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
participants
Reference:

Menu

Projects Groups Snippets
Help