Skip to content

GitLab

  • Menu
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
  • #2547

Closed
Open
Created Jan 10, 2013 by Administrator@rootOwner

Crash on several pages

Created by: ahti

I have recently set up gitlab 4.0 on a Debian server.

When I try to access admin/users, admin/groups [dashboard | someproject]/[issues | merge_requests] the page shows up blank when using Unicorn directly, or a 502 Bad Gateway is reported with Nginx.

The log files show something about a segfault. I've included an excerpt from unicorn.stderr.log that was produces by opening one of the pages. The logs for the other pages differ only in details. This is the error produces by dashboard/issues.

The other logs seem to contain no relevant information, production.log has entries like this:

Started GET "/admin/users" for 82.83.138.100 at 2013-01-10 15:51:01 +0100
Processing by Admin::UsersController#index as HTML

No completion message is printed for this page.

This is the system information as printed by gitlab:env:info

System information
System:         Debian 6.0.5
Current User:   gitlab
Using RVM:      no
Ruby Version:   1.9.3p362
Gem Version:    1.8.23
Bundler Version:1.2.3
Rake Version:   10.0.3

GitLab information
Version:        4.0.0
Revision:       c9ae412
Directory:      /home/gitlab/gitlab
DB Adapter:     mysql2
URL:            http://cronosx.de:38725
HTTP Clone URL: http://cronosx.de:38725/some-project.git
SSH Clone URL:  [email protected]:some-project.git
Using LDAP:     no
Using Omniauth: no

Gitolite information
Version:        v3.2-gitlab-patched-0-g2d29cf7
Admin URI:      git@localhost:gitolite-admin
Admin Key:      gitlab
Repositories:   /home/git/repositories/
Hooks:          /home/git/.gitolite/hooks/
Git:            /usr/bin/git

Running gitlab:check reports no errors except an outdated init script (although the newest one from master is incompatible with an install of 4-0-stable).

Assignee
Assign to
Time tracking