Problem With white page site's

Discussion in 'Install/Configuration' started by 3245, Mar 26, 2013.

  1. 3245

    3245 Member

    Hello
    i install litespeed, do building match PHP, and set port 0, than switch to litespeed, now when i open any site on server, i see white page.
    when switch to apache, it is good.

    my control panel: cpanel
    in easyphp when i do rebuild apache, end time i see SuPHP in compiler.
    version php in consol litespeed is 5.2.9 but at easyphp i see 5.3.22
    Install Path Prefix in litespeed is opt/lsws/lsphp5

    you think what is problem?:mad:
  2. webizen

    webizen New Member

    Did you see any error in building matching PHP? It is recommend that EasyApache Integration be enabled in WHM/LSWS plugin and run EasyApache afterwards. This way, every time you run EasyApache, matching PHP will be built for LSWS automatically.

    There are two ways to verify PHP in lsws:

    1. From command line
    /usr/local/lsws/fcgi-bin/lsphp5 -v

    2. Create a phpinfo php (with content "<?php phpinfo(); ?>"), then point your browser to that page.

    BTW, suPHP is not supported in LSWS.
  3. 3245

    3245 Member

    Thank you for respond.
    for first test i do this:
    1- run /usr/local/lsws/fcgi-bin/lsphp5 -v in ssh
    then do test, also have problem page white.
    2- i attache file php info
    --
    SuPHP is not support? so i must set which?

    Regards

    Attached Files:

  4. webizen

    webizen New Member

    Please show a screenshot of '/usr/.../lsphp5 -v'? Does that match with apache php? The phpinfo page you attached is from Apache. Please show a phpinfo served from LSWS.

    suPHP is not supported in LSWS because LSPHP (PHP + LSAPI) is a much better choice. No need to support it. See details below:

    http://www.litespeedtech.com/php-litespeed-sapi.html
  5. 3245

    3245 Member

    screen shot of command:
    [​IMG]

    how i can move of Suphp to other with you support? your suggestion is which? 4 or 5?
    how i can move to 4 or 5?

    i attach phpinfo from litespeed.

    Attached Files:

  6. webizen

    webizen New Member

    Try the followings:
    1. Remove /opt/xml2 (ie, 'mv /opt/xml2 /opt/xml2.bak' from command line)
    2. Enable EasyApache Integration in WHM=>LiteSpeed Web Server
    3. Run EasyApache again.
  7. 3245

    3245 Member

    also have problem
    when i do build match php in LIteSpeed, i see this error at start:

    PHP:
    ==============================================
    Start building PHP 5.3.22 with LSAPI
    ==============================================
    Wed Mar 27 01:21:39 AFT 2013

    Changing to build directory 
    /home/cpeasyapache/ls.src
    Detected php build directory 
    for cPanel /home/cpeasyapache/src/php-5.3.22
    Same source code will be copied over

    Query lastest LSAPI version
    6.1
    php
    -litespeed-6.1.tgz already downloaded, use the saved copy
    Extracting LSAPI archive
    tar -xzf php-litespeed-6.1.tgz

    Finished gathering all the source code

    Generating configuration script
    Forcing buildconf
    buildconf
    checking installation...
    buildconfautoconf version 2.59 (ok)
    Can't figure out your VCS, not cleaning.
    rebuilding configure
    rebuilding main/php_config.h.in
    autoheader: WARNING: Using auxiliary files such as `acconfig.h'
    , `config.h.bot'
    autoheader: WARNING: and 
    `config.h.top', to define templates for `config.h.in'
    autoheaderWARNINGis deprecated and discouraged.
    autoheader
    autoheaderWARNINGUsing the third argument of `AC_DEFINE' and
    autoheader: WARNING: 
    `AC_DEFINE_UNQUOTED' allows to define a template without
    autoheader: WARNING: `acconfig.h'
    :
    autoheader
    autoheaderWARNING:   AC_DEFINE([NEED_FUNC_MAIN], 1,
    autoheader:         [Define if function `main' is needed.])
    autoheader: 
    autoheader: WARNING: More sophisticated templates can also be produced, see the
    autoheader: WARNING: documentation.
    Configuring PHP build (2-3 minutes)
    checking for egrep... grep -E
    checking for a sed that does not truncate output... /bin/sed
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking target system type... x86_64-unknown-linux-gnu
    checking for cc... cc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables... 
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether cc accepts -g... yes
    checking for cc option to accept ANSI C... none needed
    checking how to run the C preprocessor... cc -E
    checking for icc... no
    checking for suncc... no
    checking whether cc understands -c and -o together... yes
    checking how to run the C preprocessor... cc -E
    checking for AIX... no
    checking whether ln -s works... yes
    checking for system library directory... lib64
    checking whether to enable runpaths... yes
    checking if compiler supports -R... no
    checking if compiler supports -Wl,-rpath,... yes
    checking for gawk... gawk
    checking for bison... bison -y
    checking for bison version... 2.3 (ok)
    checking for re2c... re2c
    checking for re2c version... 0.13.5 (ok)
    checking whether to enable computed goto gcc extension with re2c... no
    checking whether to force non-PIC code in shared modules... no
    checking whether /dev/urandom exists... yes
    checking for pthreads_cflags... -pthread
    checking for pthreads_lib... 

    Configuring SAPI modules
    checking for AOLserver support... no
    checking for Apache 1.x module support via DSO through APXS... no
    checking for Apache 1.x module support... no
    checking whether to enable Apache charset compatibility option... no
    checking for Apache 2.0 filter-module support via DSO through APXS... no
    checking for Apache 2.0 handler-module support via DSO through APXS... no
    checking for Apache 1.x (hooks) module support via DSO through APXS... no
    checking for Apache 1.x (hooks) module support... no
    checking whether to enable Apache charset compatibility option... no
    checking for Caudium support... no
    checking for CLI build... yes
    checking for Continuity support... no
    checking for embedded SAPI library support... no
    checking for FPM build... no
    checking for Zeus ISAPI support... no
    checking for LiteSpeed support... yes
    checking for Milter support... no
    checking for NSAPI support... no
    checking for PHTTPD support... no
    checking for Pi3Web support... no
    checking whether Roxen module is build using ZTS... no
    checking for Roxen/Pike support... 
    checking for thttpd... no
    checking for TUX... no
    checking for webjames... no
    checking for chosen SAPI module... litespeed

  8. webizen

    webizen New Member

    The warnings (NOT errors) are no harm. There is _NO_ error (so it should be OK). The other SAPI modules are purposely ignored because they are not related to Litespeed SAPI module and of no use for building matching PHP binary.
  9. 3245

    3245 Member

    what is your suggestion for resolve this problem?
  10. webizen

    webizen New Member

    not sure what you mean 'this problem'. There is no problem as explained before.
  11. 3245

    3245 Member

    Also i have this problem, Please help Me:(:mad::mad::mad:

Share This Page