Redirect to default page after create new accounts

[EsWeB]

Hi,
Recently i have installed LiteSpeed in two of my servers, the problem I have is that when a new account is created it don´t works and when try to access to the website the visitor is redirected to the default page (domain/cgi-sys/defaultwebpage.cgi)
I use CloudLinux + WHM/Cpanel + LiteSpeed

Hope someone can help me.

I have searched the forum and other forums and haven´t find information about this issue.

*sorry for my poor english

 

[mistwang]

Are you using Enterprise edition?
standard edition wont work with more than 5 vhosts in the httpd.conf.

 

[EsWeB]

Yes, I´m using LSWS Enterprise

Regards

 

[mistwang]

Does restarting LSWS fixes it?

 

[EsWeB]

:-O yes!
I restarted LSWS and now the site resolves correctly.
What can be wrong? I have the same issue in both servers.

 

[mistwang]

Do you have any of the checkbox for "httpd" unchecked under "Service Configuration"->"Service Manager"?

 

[EsWeB]

nop, both are checked

 

[mistwang]

Maybe you were not using the Apache binary wrapper mode?
http://www.litespeedtech.com/docs/webserver/config/general#autoReloadApacheConf

 

[EsWeB]

Hi,
Yes I´m using apache binary wrapper in the config.
"Auto Reload On Changes - Use Apache binary wrapper"

 

[EsWeB]

Hi again,
after upgrade to 4.2.9 some days ago one of my servers works correctly, but the other has the same problem, if a new account is created in that server I have to restart litespeed, if is not restarted the site don´t works, the same situation occur if a user creates a subdomain.
i´m using the same configuration in both servers and I have installed litespeed the same way in both...

 

[NiteWave]

for the problem server, can you switch to apache, see if same issue ?

 

[EsWeB]

If I switch to apache the server works correctly, it is just a problem when I use litespeed, the changes are not auto-reloaded but I´m using apache binary wrapper in the config

 

[NiteWave]

can you check content of "Apache binary wrapper"?
#file /usr/local/apache/bin/httpd
#vi /usr/local/apache/bin/httpd

 

[EsWeB]

ooopss sorry NiteWave I haven´t received notification of your reply.
this is the content of /usr/local/apache/bin/httpd
#!/bin/sh

ARGS="$@"
ARG1="$1"

LSWS_HOME=/usr/local/lsws
APACHE_BIN=/usr/local/apache/bin/httpd

CTRL_APACHE=0

APACHE=/usr/local/apache/bin/httpd_ls_bak


LSWS=$LSWS_HOME/bin/lswsctrl
PARAM_LOG=$LSWS_HOME/logs/ap_cmd_param.log
APACHE_STATE=$LSWS_HOME/admin/cgid/apache_state

ulimit -v unlimited

if [ ! -f $LSWS ]; then
mv $APACHE $APACHE_BIN
$APACHE_BIN $ARGS
exit $?
fi

echo "`date`: $@" >> $PARAM_LOG

if [ "x$ARG1" = 'x-DSSL' ]; then
shift
ARG1=$1
fi

if [ "x$ARG1" = 'x' ]; then
$LSWS restart

elif [ "x$ARG1" = 'x-k' ]; then
ARG2=$2
case $ARG2 in
start|startssl|sslstart|start-SSL)
echo "START" > $APACHE_STATE
$LSWS restart
ERR=$?
if [ "x$CTRL_APACHE" = "x1" ]; then
$APACHE $ARGS
fi
exit $ERR
;;
stop|graceful-stop)
# never stop LSWS here, use "service lsws stop" instead
# have to stop lsws or make cPanel belive apache is stopped,
# otherwise cpanel will send signal "9"
$LSWS stophttpd
if [ "x$CTRL_APACHE" == "x1" ]; then
$APACHE $ARGS
else
echo ""
fi
;;
restart|graceful)
echo "START" > $APACHE_STATE
$LSWS restart
;;
*)
$APACHE $ARGS
esac
else
if [ "x$ARG1" = "xuninstall" ]; then
if [ "x$CTRL_APACHE" = "x0" ]; then
$LSWS stop
sleep 1
fi
mv $APACHE $APACHE_BIN
$APACHE_BIN
elif [ "x$ARG1" = "xinstall" ]; then
if [ "x$CTRL_APACHE" = "x0" ]; then
killall `basename $APACHE_BIN`
fi
echo "START" > $APACHE_STATE
$LSWS start
else
$APACHE $ARGS
fi
fi

ERROR=$?
exit $ERROR

 

[mistwang]

try

/usr/local/lsws/bin/lshttpd -v

if it shows Standard, you may need to do

echo "4.2.11-ent" > /usr/local/lsws/autoupdate/release
/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.11

 

[EsWeB]

# /usr/local/lsws/bin/lshttpd -v
LiteSpeed/4.2.10 Enterprise

 

[mistwang]

Can you please check /usr/local/cpanel/logs/safeapacherestart_log, see if anything log after adding an account?

 

[EsWeB]

that log file has only entries like:
[2014-05-13 19:34:02 -0500] info [safeapacherestart] Restart elapsed seconds: 69
[2014-05-13 21:31:07 -0500] info [safeapacherestart] Restart elapsed seconds: 2
[2014-05-14 04:22:55 -0500] info [safeapacherestart] Restart elapsed seconds: 2
[2014-05-14 04:31:25 -0500] info [safeapacherestart] Restart elapsed seconds: 1
[2014-05-14 04:57:06 -0500] info [safeapacherestart] Restart elapsed seconds: 1
[2014-05-14 05:22:17 -0500] info [safeapacherestart] Restart elapsed seconds: 1
[2014-05-14 07:02:36 -0500] info [safeapacherestart] Restart elapsed seconds: 1
[2014-05-14 07:23:05 -0500] info [safeapacherestart] Restart elapsed seconds: 1
[2014-05-14 09:11:41 -0500] info [Cpanel::HttpUtils::ApRestart] Unable to locate httpd processes in ps output. Restart forced.
[2014-05-14 09:12:51 -0500] info [safeapacherestart] Forced restart elapsed seconds: 70
[2014-05-14 10:18:08 -0500] info [safeapacherestart] Restart elapsed seconds: 5
[2014-05-14 12:47:52 -0500] info [safeapacherestart] Restart elapsed seconds: 2

the last line is when i created a new account in the server.

 

[mistwang]

It means that cPanel restarts the server successfully, LSWS should be restarted by that time.
You can check
/usr/local/lsws/logs/lsrestart.log and ap_cmd_param.log

The timestamp of last restart should matches.

Maybe browser cached the cPanel default page, uses wget or curl to test the new account, or clear browser cache.

 

[EsWeB]

lsrestart.log:
Tue Apr 29 04:20:00 CDT 2014
start, LSWS running: 1
Mon May 5 17:27:18 CDT 2014
restart, LSWS running: 1
Tue May 13 19:52:39 CDT 2014
restart, LSWS running: 0
Wed May 14 09:00:23 CDT 2014
stop, LSWS running: 1
Wed May 14 09:01:54 CDT 2014
restart, LSWS running: 0
Wed May 14 09:10:33 CDT 2014
stop, LSWS running: 1
Wed May 14 09:13:02 CDT 2014
restart, LSWS running: 0

ap_cmd_param.log:
Wed May 14 08:59:44 CDT 2014: -v
Wed May 14 09:20:33 CDT 2014: -v
Wed May 14 09:23:38 CDT 2014: -S
Wed May 14 09:29:24 CDT 2014: -v
Wed May 14 09:42:23 CDT 2014: -v
Wed May 14 09:50:12 CDT 2014: -v
Wed May 14 10:04:06 CDT 2014: -v
Wed May 14 10:08:58 CDT 2014: -v
Wed May 14 10:09:20 CDT 2014: -v
Wed May 14 10:18:07 CDT 2014: graceful
Wed May 14 10:50:12 CDT 2014: -v
Wed May 14 11:50:08 CDT 2014: -v
Wed May 14 12:47:31 CDT 2014: -l
Wed May 14 12:47:31 CDT 2014: -V
Wed May 14 12:47:31 CDT 2014: -v
Wed May 14 12:47:51 CDT 2014: graceful
Wed May 14 12:50:09 CDT 2014: -v
Wed May 14 12:54:53 CDT 2014: graceful
Wed May 14 12:58:30 CDT 2014: -v
Wed May 14 13:50:04 CDT 2014: -v

is not a problem of cache, this happens too when a user creates a subdomain, I have to restart Litespeed manually, after that the subdomain resolves correctly.