mr.VVoo
mr.VVoo

Reputation: 2270

GitLab 5.0 produces Error 500 on Project settings page after creating new Project

Last week i updated to GitLab 5.0. All previous existing projects are working fine when trying to edit them.

Today i created a new one and everything also seemed to work fine. Then i wanted to add a member to my project and checked the settings page and everything i got was An Internal Server Error (500).

The only log i've found was in production.log:

Completed 500 Internal Server Error in 95ms

ActionView::Template::Error (undefined method `heads' for nil:NilClass):
    36:                   .input
    37:                     = f.text_area :description, placeholder: "awesome project", class: "span5", rows: 3, maxlength: 250
    38: 
    39:                 - unless @repository.heads.empty?
    40:                   .clearfix
    41:                     = f.label :default_branch, "Default Branch"
    42:                     .input= f.select(:default_branch, @repository.heads.map(&:name), {}, style: "width:210px;")
  app/views/projects/_form.html.haml:39:in `block in _app_views_projects__form_html_haml__2678582515483350008_62614560'
  app/views/projects/_form.html.haml:17:in `_app_views_projects__form_html_haml__2678582515483350008_62614560'
  app/views/projects/edit.html.haml:6:in `_app_views_projects_edit_html_haml___3552883863573912945_62197460'

But what does this mean?

I already tried to recreate the project but this leads to the same error. My Gitlab installation is a default one except that i'm using unicorn with Apache Proxy instead of nginx.

UPDATE: In the meantime i figured out that the repo wasn't created. The clarifies the error message but why is the repository not created?

Upvotes: 3

Views: 2171

Answers (2)

VonC
VonC

Reputation: 1328522

There was a recent similar bug a month ago.

Sorry, I think sidekiq was down... I've restart gitlab and nginx -> Now it works.

so:


In this case, sidekiq was down, but a complete restart of the server itself was necessary for the setting page of the project to be available again.

Upvotes: 3

Adrian
Adrian

Reputation: 2388

We encountered a similer problem with wrong permissions.

You should check the permissions of /home/git/repositories. Maybe the git process is not allowed to create folders/files in there.

Upvotes: 1

Related Questions