[Not Resolved] LSWS 4.1 - Spinlock

Discussion in 'Bug Reports' started by MikeDVB, Apr 23, 2011.

  1. bbb177

    bbb177 New Member

    Yes, and it doesn't work, the server still "hangs". As far as I know my hosting sent bug reports to you, so you should have detailed knowledge how to reproduce it.
  2. jackc

    jackc New Member

    I'm seeing the same problem too, with the latest 4.1.10, didn't have this problem before with heavier server load and older version of lsws, really weird.
    when the problem occured litespeed is using 100 percent cpu. also seeing possibly memory leak, litespeed is using alot more memory than usual over time.

    some strace below

    epoll_ctl(7, EPOLL_CTL_DEL, 59, {0, {u32=59, u64=59}}) = 0
    close(59) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 78, {0, {u32=78, u64=78}}) = 0
    close(78) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 115, {0, {u32=115, u64=115}}) = 0
    close(115) = 0
    recvfrom(136, 0x7fff2ba1daef, 1, 2, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
    epoll_ctl(7, EPOLL_CTL_DEL, 174, {0, {u32=174, u64=174}}) = 0
    close(174) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 175, {0, {u32=175, u64=175}}) = 0
    close(175) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 256, {0, {u32=256, u64=256}}) = 0
    close(256) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 265, {0, {u32=265, u64=265}}) = 0
    close(265) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 266, {0, {u32=266, u64=266}}) = 0
    close(266) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 268, {0, {u32=268, u64=268}}) = 0
    close(268) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 272, {0, {u32=272, u64=272}}) = 0
    close(272) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 278, {0, {u32=278, u64=278}}) = 0
    close(278) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 279, {0, {u32=279, u64=279}}) = 0
    close(279) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 288, {0, {u32=288, u64=288}}) = 0
    close(288) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 393, {0, {u32=393, u64=393}}) = 0
    close(393) = 0
    epoll_ctl(7, EPOLL_CTL_DEL, 425, {0, {u32=425, u64=425}}) = 0
    close(425) = 0
  3. mistwang

    mistwang LiteSpeed Staff

    which version of LSWS were you using? If you switch back to the older version, will the problem disappear?

Share This Page