web console not responding after graceful restart

Discussion in 'Bug Reports' started by Clockwork, Jul 25, 2009.

  1. Clockwork

    Clockwork Member

    As described in the title. It's a brand new server, debian lenny 64bit.

    I'm using lsws 4.0.7.

    p.s. if I wait some minutes it's working again.

    This problem also only occurs if I use the web console to restart lsws.


    error.log:

    Last edited: Jul 26, 2009
  2. Clockwork

    Clockwork Member

    I've just added a part of my error.log.
  3. mistwang

    mistwang LiteSpeed Staff

    It could happen on a very busy server during graceful restart, the old server stop serving request for the admin console, while the new server process is not ready yet.
  4. Clockwork

    Clockwork Member

    I'm just setting up this new server, this means there are not visitors on it :)
  5. mistwang

    mistwang LiteSpeed Staff

    Maybe the best way to trouble shoot this is to PM me a temp root access to the test server. I could not reproduce it in our lab, must be something special in your environment.
  6. amaltemara

    amaltemara New Member

    Similar problem here...

    This seems to be happening to my server (4.0.9) as well... similar environment..

    New install of "Ubuntu 8.04.3 LTS"



    error.log:
    2009-08-05 00:14:32.784 [NOTICE] Your License key will expire in 34 days
    2009-08-05 00:14:32.784 [NOTICE] Loading LiteSpeed/4.0.9 Enterprise ...
    2009-08-05 00:14:32.985 [NOTICE] [ADMIN] server socket: uds://opt/lsws/admin/tmp/admin.sock.7905
    2009-08-05 00:14:32.985 [NOTICE] Loading configuration from /opt/lsws/conf/httpd_config.xml ...
    2009-08-05 00:14:32.986 [NOTICE] Recovering server socket: [64.15.147.55:80]
    2009-08-05 00:14:32.986 [NOTICE] Recovering server socket: [*:7080]
    2009-08-05 00:14:32.986 [NOTICE] [config] chroot is disabled.
    2009-08-05 00:14:32.986 [INFO] old priority: -19, new priority: -19
    2009-08-05 00:14:32.986 [INFO] [config:server:basic] For better obscurity, server version number is hidden in the response header.
    2009-08-05 00:14:32.987 [INFO] Start listen socket [/opt/lsws/admin/conf/.cgid.sock].
    2009-08-05 00:14:32.988 [NOTICE] The maximum number of file descriptor limit is set to 6000.
    2009-08-05 00:14:32.988 [NOTICE] [config:server:epsr:lsphp5]'Process Limit' probably is too low, adjust the limit to: 310.
    2009-08-05 00:14:32.988 [NOTICE] [config:server:epsr:lsphp4]'Process Limit' probably is too low, adjust the limit to: 310.
    2009-08-05 00:14:32.990 [NOTICE] lshttpd (24986) is ready
    2009-08-05 00:14:32.991 [NOTICE] [child: 24988] Successfully change current user to nobody
    2009-08-05 00:14:32.991 [NOTICE] [Child: 24988] Core dump is enabled.
    2009-08-05 00:14:32.991 [NOTICE] [Child: 24988] Setup swapping space...
    2009-08-05 00:14:32.991 [NOTICE] [Child: 24988] LiteSpeed/4.0.9 Enterprise starts successfully!
    2009-08-05 00:14:32.991 [NOTICE] [AutoRestarter] new child process with pid=24988 is forked!
    2009-08-05 00:14:32.992 [INFO] Stop listener *:7080.
    2009-08-05 00:14:32.992 [NOTICE] [child: 24989] Successfully change current user to nobody
    2009-08-05 00:14:32.992 [NOTICE] [Child: 24989] Core dump is enabled.
    2009-08-05 00:14:32.992 [NOTICE] [Child: 24989] Setup swapping space...
    2009-08-05 00:14:32.992 [NOTICE] [Child: 24989] LiteSpeed/4.0.9 Enterprise starts successfully!
    2009-08-05 00:14:32.992 [NOTICE] [AutoRestarter] new child process with pid=24989 is forked!
    2009-08-05 00:14:33.200 [NOTICE] [AutoUpdate] Checking for new releases...
    2009-08-05 00:14:33.452 [INFO] [AutoUpdate] No new update.
  7. mistwang

    mistwang LiteSpeed Staff

    You can try enable debug logging, we could not reproduce it in our lab. may need to check what happened on your server if possible.

Share This Page