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

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

  • Report abuse

  • New issue

  • Report abuse

Unicorn not longer serving js files in 7.3

Closed

Unicorn not longer serving js files in 7.3

Created by: onknows

It doesn't seem that unicorn is working in 7.3. I have a GitLab 7.0 on Ubuntu and a Gitlab 7.3 on CentOS 6.5.

On the CentOS 6.5 machine I am unable to load any js files. The site waits for the javascript and then after 60 seconds (configured in unicorn.rb) is produces message (failed) net::ERR_EMPTY_RESPONSE in the network tab in Chrome. I think this means that there is no response.

When I do the same on the Ubuntu machine with 7.0 I get a response immediately. No delay.

Unicorn error log does not show alot of information. There is just the timeout info E, [2014-10-06T16:48:41.044751 #7189] ERROR -- : worker=2 PID:7616 timeout (61s > 60s), killing E, [2014-10-06T16:48:41.068234 #7189] ERROR -- : reaped #<Process::Status: pid 7616 SIGKILL (signal 9)> worker=2 I, [2014-10-06T16:48:41.074890 #7715 (closed)] INFO -- : worker=2 ready

Other types of files such as css files load fine.

As I understand unicorn is simple. It does one thing and tries to do it well. So there is not a lot of configuration to play around with to get this working.

This should just work, like on my Ubuntu machine. Why is this no longer working?

Would it not be better to use Phusion Passenger? That is proven technology.

Linked issues
...

    Related merge requests

    • 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: