5.1.6

Discussion in 'General' started by bobykus, Jun 9, 2016.

  1. bobykus

    bobykus Well-Known Member

    Here we go, right after update 5.1.5 > 5.1.6

    root 4487 4.4 0.4 106488 81624 ? SN 11:23 0:25 litespeed (lshttpd)
    root 4488 0.0 0.0 6156 484 ? SN 11:23 0:00 \_ httpd (lscgid)
    httpd 7424 1.7 0.0 0 0 ? ZN 11:26 0:07 \_ [litespeed] <defunct>
    root 14495 0.0 0.0 108176 1396 ? SN 11:31 0:00 \_ sh -c gdb --batch --command=/usr/local/lsws//admin/misc/gdb-bt /usr/local/lsws//bin/litespeed /tmp/lshttpd/core* >> /tmp/m-rfugy5
    root 14496 0.4 0.2 225632 46840 ? SN 11:31 0:00 \_ gdb --batch --command=/usr/local/lsws//admin/misc/gdb-bt /usr/local/lsws//bin/litespeed /tmp/lshttpd/core.5780 /tmp/lshttpd/core.7424


    :(((
     
  2. bobykus

    bobykus Well-Known Member

    cat /etc/issue
    CentOS release 6.8 (Final)
    Kernel \r on an \m

    uname -a
    Linux 2.6.32-642.1.1.el6.x86_64 #1 SMP Tue May 31 21:57:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
     
  3. Varial

    Varial Member

    I got a flood of emails saying that Litespeed was restarted immediately after upgrading. Occurred on all my servers running LiteSpeed (using CloudLinux 7). I downgraded back to 5.1.5 to resolve the issue.

    At [08/Jun/2016:16:17:11 -0600], web server with pid=38533 received unexpected signal=6, a core file has been created. A new instance of web server will be started automatically!
     
  4. mistwang

    mistwang LiteSpeed Staff

    Please forward us bug report emails.
     
  5. mistwang

    mistwang LiteSpeed Staff

    Please update to latest build of 5.1.6, should be fixed.
    /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.6
     
    bobykus likes this.
  6. bobykus

    bobykus Well-Known Member

    Works now, Thank you!
     
  7. bobykus

    bobykus Well-Known Member

    Uf... still crashing time after time

    Jun 14 14:36:43 host kernel: litespeed[1260]: segfault at 4a ip 000000000047816c sp 00007ffd9e7d7930 error 4 in lshttpd.5.1.6[400000+545000]
    Jun 14 14:36:43 host kernel: litespeed[1259]: segfault at 4a ip 000000000047816c sp 00007ffd9e7d7930 error 4 in lshttpd.5.1.6[400000+545000]
     
  8. mistwang

    mistwang LiteSpeed Staff

    Please send us bug report email and core file.
     
  9. bobykus

    bobykus Well-Known Member

    It does not generate any core, at least there is nothing in /tmp/lshttpd/
     
  10. mistwang

    mistwang LiteSpeed Staff

    Maybe it is due to the vps detection code, we intentionally do that in a child process forked, it wont affect normal service.
     
  11. bobykus

    bobykus Well-Known Member

    yes, may be. i created a ticket
     

Share This Page