Litespeed dies on restart

Discussion in 'Ruby/Rails' started by djsodom, Sep 5, 2006.

  1. djsodom

    djsodom Active Member

    I'm having the same exact issues as this user had:

    Except I'm on a intel Mac.

    I'm following Bob Silva's screencast step for step here:

    Litespeed starts perfectly when I initially install it, but when I add the rails vhost, it dies and then I can't restart it via command line. The error I get is:

    steve-odoms-computer:/srv/www steveodom$ /usr/local/lsws/bin/lswsctrl startCan't determine the Home of LiteSpeed Web Server, exit!
    [ERROR] Failed to start lshttpd!

    The error.log shows:

    2006-09-05 10:18:33.365 [NOTICE] Loading LiteSpeed/2.2 Standard ...
    2006-09-05 10:18:33.369 [NOTICE] [ADMIN] server socket:
    2006-09-05 10:18:33.369 [NOTICE] Loading configuration from /usr/local/lsws/conf/httpd_config.xml ...
    2006-09-05 10:18:33.371 [NOTICE] Recovering server socket: [*:80]
    2006-09-05 10:18:33.371 [NOTICE] Recovering server socket: [*:81]
    2006-09-05 10:18:33.371 [INFO] old priority: 0, new priority: 0
    2006-09-05 10:18:33.371 [INFO] [config:server:basic] For better obscurity, server version number is hidden in the response header.
    2006-09-05 10:18:33.408 [ERROR] [config:server:listener] missing <listenerList>
    2006-09-05 10:18:33.408 [WARN] [config:server:listener] No listener is available for normal virtual host!
    2006-09-05 10:18:33.408 [NOTICE] The maximum number of file descriptor limit is set to 12288.

    I've repeated the install process from scratch 3 times to make sure I wasn't leaving something out

    What else can I try?

  2. xing

    xing LiteSpeed Staff


    You must start the web server as a user that has "root" privilege. Once started, litespeed will automatically downgrade to the configured user level.

    Use "sudo lswsctrl start" to start the server if you are not root.
    Last edited: Sep 5, 2006

Share This Page