Log is filled with errors

Discussion in 'Bug Reports' started by debilistic, Oct 12, 2007.

  1. debilistic

    debilistic New Member

    New LiteSpeed installation, log started getting filled with errors like below:

    2007-10-12 06:19:53.060 ERROR Failed to generate the real time report!
    2007-10-12 06:19:55.060 ERROR Failed to generate the real time report!
    2007-10-12 06:19:56.978 ERROR Failed to generate the status report!
    2007-10-12 06:20:04.524 ERROR Failed to generate the real time report!
    2007-10-12 06:20:05.843 NOTICE [AutoRestarter] child process with pid=11647 received signal=11, a core file is created!
    2007-10-12 06:20:06.087 ERROR Failed to generate the real time report!
    2007-10-12 06:20:08.088 ERROR Failed to generate the real time report!
    2007-10-12 06:20:10.090 ERROR Failed to generate the real time report!
    2007-10-12 06:34:10.659 NOTICE [AutoRestarter] child process with pid=15996 received signal=11, a core file is created!
    2007-10-12 06:39:55.036 NOTICE [AutoRestarter] child process with pid=28661 received signal=11, a core file is created!
    2007-10-12 06:52:40.430 NOTICE [AutoRestarter] child process with pid=7237 received signal=11, a core file is created!
    2007-10-12 06:55:04.094 NOTICE [AutoRestarter] child process with pid=11834 received signal=11, a core file is created!
    2007-10-12 06:58:02.841 NOTICE [AutoRestarter] child process with pid=19675 received signal=11, a core file is created!

    Was going to run a production on this but this feels really uncomfortable, if even an empty system with one listener is behaving like this. Maybe a misconfiguration? Why no indication of what the problem is? The listener is working fine.
  2. mistwang

    mistwang LiteSpeed Staff

    What is your OS? Using VPS? Our server is very reliable, maybe something special for your installation.

    Maybe you installed LSWS into your home directory, but the server run as another user, so the server failed to create the report. Just install it to /opt or /usr/local, it should be fine.
  3. debilistic

    debilistic New Member

    OS is linux. Installed in /usr/local/lsws...

    Very obscure web server I must tell you. Right now, it just does not start with no indication in the log files or in console on what's wrong. The only process running from the web server is lscgid. The only log created after "/etc/init.d/lsws start" is:

    # cat error.log
    2007-10-19 13:58:36.134 [NOTICE] Loading LiteSpeed/3.2.3 Standard ...
    2007-10-19 13:58:36.238 [NOTICE] [ADMIN] server socket: 127.0.0.1:7071
    2007-10-19 13:58:36.238 [NOTICE] Loading configuration from /usr/local/lsws/conf/httpd_config.xml ...
    2007-10-19 13:58:36.239 [INFO] old priority: 0, new priority: 0
    2007-10-19 13:58:36.239 [INFO] [config:server:basic] For better obscurity, server version number is hidden in the response header.
    2007-10-19 13:58:36.243 [NOTICE] The maximum number of file descriptor limit is set to 1024.


    after that, silence. no ports open, no processes running. how to troubleshoot this?
  4. mistwang

    mistwang LiteSpeed Staff

    Are you using the 32bit package on 64bit Linux?
    Is that possible for our staff member to take a look at it?
  5. debilistic

    debilistic New Member

    no, 32b on 32bit linux. what would your staff need, root access? then probably no... :(
  6. mistwang

    mistwang LiteSpeed Staff

    How about send the output of the following command to us?
    Code:
    cd lsws/bin
    strace ./lshttpd -d
  7. debilistic

    debilistic New Member

    let me know where to send it? last few lines:
    Code:
    brk(0x829e000)                          = 0x829e000
    open("/usr/local/lsws/logs/PoolRank.access.log", O_WRONLY|O_APPEND|O_CREAT, 0644) = 12
    fstat64(12, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
    fcntl64(12, F_SETFD, FD_CLOEXEC)        = 0
    stat64("/usr/local/lsws/share/autoindex/", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
    readlink("/usr", 0xbfff8c91, 4094)      = -1 EINVAL (Invalid argument)
    readlink("/usr/local", 0xbfff8c91, 4094) = -1 EINVAL (Invalid argument)
    readlink("/usr/local/lsws", 0xbfff8c91, 4094) = -1 EINVAL (Invalid argument)
    readlink("/usr/local/lsws/share", 0xbfff8c91, 4094) = -1 EINVAL (Invalid argument)
    readlink("/usr/local/lsws/share/autoindex", 0xbfff8c91, 4094) = -1 EINVAL (Invalid argument)
    access("/usr/local/lsws/share/autoindex/", F_OK) = 0
    access("/home/poolrank/production/pool/", F_OK) = 0
    access("/home/poolrank/production/pool/public/", F_OK) = 0
    stat64("/home/poolrank/production/pool/public/", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
    readlink("/home", 0xbfff7d51, 4094)     = -1 EINVAL (Invalid argument)
    readlink("/home/poolrank", 0xbfff7d51, 4094) = -1 EINVAL (Invalid argument)
    readlink("/home/poolrank/production", 0xbfff7d51, 4094) = -1 EINVAL (Invalid argument)
    readlink("/home/poolrank/production/pool", 0xbfff7d51, 4094) = -1 EINVAL (Invalid argument)
    readlink("/home/poolrank/production/pool/public", 0xbfff7d51, 4094) = -1 EINVAL (Invalid argument)
    access("/home/poolrank/production/pool/public/", F_OK) = 0
    --- SIGSEGV (Segmentation fault) ---
    +++ killed by SIGSEGV +++
    
  8. mistwang

    mistwang LiteSpeed Staff

    Can you email us the core files under /tmp/lshttpd/bak_cores/ for analysis?


    If you are using enterprise, please copy bin/lshttpd.dbg binary in the installation package over to where lshttpd was installed to. The core file created with that binary is useful.

Share This Page