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
  • #6978

Closed
Open
Created May 15, 2014 by Administrator@rootOwner

unicorn timeout on each push (second or third try will sucess)

Created by: lippoliv

Hey there, this week I updated from 6.4.3 with the Update-Script to 6.8.1, also I updated the git-shell as mentioned in the Install-Advice.

But now I can't push anymore. I can push, but I have to do it two or three times, until it will work :/

I get an "Read timeout" on client side, server logs in unicorn.stderr.log:

I, [2014-05-14T11:30:30.320705 #12824]  INFO -- : worker=0 ready
E, [2014-05-15T06:35:36.320349 #3324] ERROR -- : worker=0 PID:12824 timeout (61s > 60s), killing
E, [2014-05-15T06:35:36.341969 #3324] ERROR -- : reaped #<Process::Status: pid 12824 SIGKILL (signal 9)> worker=0
I, [2014-05-15T06:35:36.349702 #25225]  INFO -- : worker=0 ready

My gitlab runs on an vps wich is definetly big enough, there is no high traffic on the gitlab-instance.

What can I do to fix it or is it an gitlab bug?

Regards, Oli

Assignee
Assign to
Time tracking