503 and log entry

Discussion in 'Ruby/Rails' started by thijs, Mar 12, 2008.

  1. thijs

    thijs New Member

    I've been having some trouble that some sites on one machine crash, Litespeed gives a 503 after that.

    I see these entries in the logs:

    lscgid: setuid(): Resource temporarily unavailable

    and

    fork() failed, please increase process limit: Resource temporarily unavailable

    What could be the cause of this?
  2. mistwang

    mistwang LiteSpeed Staff

    You need to increase the "Process soft/hard limit" under "Ruby Rails" tab.
  3. joost

    joost New Member

    I just wanted to share I had been getting lscgid: setuid(): Resource temporarily unavailable since upgrading from LiteSpeed 4.3.3 to 4.3.11, even if I did not get the fork() error.

    Increasing the limits solved the problem for me as well.

Share This Page