You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1482: Investigate problems with Unicorn's worker_processes option

Kind bug
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

I've got it set to 4 but only 1 child gets spawned. It's seems to be getting ignored.

I can manually cause others to be spawned by sending a SIGTTIN.

Comments

  1. Greg Hurrell

    A case of PEBKAC, I had:

    worker_processes = 4

    Instead of the needed:

    worker_processes 4

    This is one of the downsides of the love-affair with Ruby DSLs. Instead of a syntax error for a mistake like that you just get a silent no-op.

  2. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu