server stopped suddenly...

Discussion in 'Bug Reports' started by Fed, Dec 31, 2003.

  1. Fed

    Fed New Member


    i have been testing litespeed for two weeks and all this time it was very-very nice, thank you!
    but today it stopped suddenly, and i never could start it again :(
    when starting, it works four minutes, than stops with this lines in errorlog:

    2003-12-31 14:58:42.829 [ERROR] HttpListener::start(): Can't listen at address *:7080: Address already in use!
    2003-12-31 14:58:42.829 [ERROR] HttpServer::addListener(*:7080) failed to create new listener
    2003-12-31 14:58:42.829 [ERROR] [config:admin:listener:adminListener] failed to start listener on address *:7080!
    2003-12-31 14:58:42.829 [ERROR] [config:admin:listener] No listener is available for admin virtual host!
    2003-12-31 14:58:42.829 [ERROR] Fatal error in configuration, exit!

    why? what does it mean? i didn't touch it!
    please help.
  2. mistwang

    mistwang LiteSpeed Staff


    Thank you for trying our product.

    Are you testing the standard edition?
    Looks like TCP port 7080 is still occupied by another process. Before you try to start the server again, make sure all "lshttpd" processes are gone.

    Do "ps -ef | grep lshttpd", kill all processes listed, use "kill -9 <pid>" if it wont exit.

    make sure 7080 is not used by other application, use the following command as root:
    "lsof | grep 7080"
    You can change the port used by lshttpd by changing the value of <address> in lsws/admin/conf/admin_config.xml.

    If you are still experiencing the sudden stop, please set "debug level" to "high" and send error.log.* to

    Please keep us posted with your experience.

  3. Fed

    Fed New Member


    thank you for your reply!
    yes, its a standard edition.
    i have found out the problem: my access.log file reached 2G and that was why lshttpd stopped.
    so its working again!
    and looks nice 8)

    i have one suggestion:
    i'd like to add "charset" line to the httpd's header; like this:
    Content-Type: text/html; charset=windows-1251
    it would be very fine!

    do you plan this in future releases?
    thank you.
  4. mistwang

    mistwang LiteSpeed Staff

    Please tell me more about this, I want to have this issue addressed.
    lshttpd should rotate the log file automatically when the size limit is reached, it failed to do so? Or you set the size limit bigger than 2G?
    Or there is no enough disk space left?

    Next release will allow you to add that in the MIME definition file. By doing so, Content-Type of all static html page will be affected. Not sure if it is what you'd like?

    Support for multi-languages is low priority on our current to do list. :)

    Best Regards.
  5. Fed

    Fed New Member

    logfile size was default (10M) and there is more than 10G of free space, but you are right: lshttpd did not rotate it ...
    error log was rotated each time when server reloaded, but access log was not rotated (it became more than 200M for 24h) even after reload and restart.

    and what about dynamic pages :)

    i mean something like "DefaultCharset" directive in Apache server. for example, my Apache httpd does return this header when i telnet host 80 and request HEAD:
    Server: Apache
    X-Powered-By: PHP/4.3.3
    Connection: close
    Content-Type: text/html; charset=windows-1251

    and this helpes me in some situations.

    i have one more problem and this one is more harmful :(
    when server's load is high i often get error 503:

    503 Service Unavailable
    The server is temporarily busy, try again later!

    and there are 2 peculiarities about it:
    1) only PHP scripts are affected; perl and other cgis and static files are served fine.
    2) as usual, when i get error 503 for my php pages, admin interface works fine and even fast! why? it is written in php as i can see...

    i tried different values for max connections, max cgi instances, but had no success...
    how could this be resolved?

    thank you.
  6. mistwang

    mistwang LiteSpeed Staff

    Ok, it is fixed, thank you for pointing it out.

    I suppose it should be generated dynamically. :)

    I guess you mean "AddDefaultCharset".
    Ok, we can add this feature in future release.

    We just fixed a bug that could cause trouble for busy site, if you interested, you can try the new release. I will send you a PM regarding it.

    And another possibility is the "initial timeout" of your PHP FCGI configuration is lower than the maximum time needed for PHP to process certain kind of request. Please increase it if you do have such kind of PHP script.

    And you can decrease "retry timeout" to let lshttpd retry the problematic Fast CGI application more quickly.

    Best Regards.

Share This Page