[RESOLVED] LSWS 4.0.13 - Signal 9's gone... Signal 15's new

[mistwang]

We are still working on it.

In the mean time, you can try our wswatch.sh script. Update /usr/local/lsws/bin/wswatch.sh with bellow shell script.

#!/bin/sh

BASE_DIR=`dirname "$0"`
cd "$BASE_DIR"
BASE_DIR=`pwd`


while [ "1" -eq "1" ]; do

ERR=1
if [ -f /tmp/lshttpd/lshttpd.pid ]; then
    kill -0 `cat /tmp/lshttpd/lshttpd.pid` 2>/dev/null
    ERR=$?
fi

if [ $ERR -ne 0 ]; then
    sleep 2
    if [ -f /tmp/lshttpd/lshttpd.pid ]; then
        kill -0 `cat /tmp/lshttpd/lshttpd.pid` 2>/dev/null
        ERR=$?
    fi
fi

if [ $ERR -ne 0 ]; then
    ./lshttpd
    D=`date`
    echo "$D: LSWS stopped, start LSWS." >> $BASE_DIR/../logs/error.log
fi
sleep 2

done

and edit lsws/bin/lswsctrl script, uncomment

WSWATCH=1

at the beginning of the file. do

./lswsctrl stop
./lswsctrl start

It will start lshttpd in 2 seconds if cPanel kills off LSWS.

[aww]

okay, thanks, just did the changes and will watch this weekend to see if it helps

my lsws location is under /opt/lsws btw, I guess you changed the default over time

[anewday]

Originally Posted by aww

okay, thanks, just did the changes and will watch this weekend to see if it helps

my lsws location is under /opt/lsws btw, I guess you changed the default over time

How did it go?

[aww]

Originally Posted by anewday

How did it go?

Oh sorry for the lack of updates, the above workaround works perfect, no more emails about signal 15s

[aww]

Actually, you know what - with the 4.0.15 it's back

Every few hours or so

At [12/Jul/2010:01:11:02 -0400], web server with pid=18064 received unexpected signal=15, no core file is created.

At [12/Jul/2010:03:09:57 -0400], web server with pid=15548 received unexpected signal=15, no core file is created.

At [12/Jul/2010:05:08:50 -0400], web server with pid=11271 received unexpected signal=15, no core file is created.

At [12/Jul/2010:09:06:40 -0400], web server with pid=24521 received unexpected signal=15, no core file is created.

Would the upgrade have clobbered the old wswatch.sh or lsws/bin/lswsctrl ?

[MikeDVB]

Originally Posted by aww

Actually, you know what - with the 4.0.15 it's back

Every few hours or so


Would the upgrade have clobbered the old wswatch.sh or lsws/bin/lswsctrl ?

The newest .15 disabled wswatch by default as it was causing issues on cPanel servers when editing the httpd.conf (or at least, that's what it said in my support ticket).

[aww]

I really hope they find a workaround for this soon, the sheer number of times it's happening is worrying me.

Why is cpanel so anti-non-apache?

[mistwang]

Please download and try 4.0.16 release package, it should take care of the signal 9 issue. Will announce it tomorrow.

[aww]

Ah, I noticed the new date on 4.0.16 yesterday and gave it a try and sure enough it did indeed stop the problem.

Thank you!

[aww]

I spoke too soon.

Getting Signal 15's every 2 hours now on 4.0.16