Shell function within PHP works on Apache but not Litespeed

Discussion in 'Install/Configuration' started by MarkPW, Apr 13, 2013.

  1. MarkPW

    MarkPW New Member

    I'm trying to run a java command within PHP through Litespeed but continually receive an error. However, the same script running on Apache returns the expected result.

    Litespeed and Apache have identical PHP builds: 5.3.23.
    Tried PHP suexec setting off and running as user

    The script:
    PHP:
    <?php

    passthru
    ('/usr/java/jdk1.7.0_17/bin/java -Xms20m -Xmx64m -version 2>&1');

    ?>
    Litespeed output:
    Code:
    *** glibc detected *** /usr/java/jdk1.7.0_17/bin/java: double free or corruption (!prev): 0x00007f171c011630 *** *** glibc detected *** /usr/java/jdk1.7.0_17/bin/java: double free or corruption (fasttop): 0x00007f171c009ee0 *** *** glibc detected *** /usr/java/jdk1.7.0_17/bin/java: double free or corruption (!prev): 0x00007f171c011630 ***
    Apache output:
    Code:
    java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
    If I execute the script on command line (/usr/local/lsws/lsphp5/bin/php) it works fine.

    I am desperate to get this resolved and would appreciate any help.
  2. NiteWave

    NiteWave Administrator

    please try raise the
    Memory Soft Limit (bytes)
    Memory Hard Limit (bytes)
    of lsphp5 in admin console
  3. NiteWave

    NiteWave Administrator

    Thanks, in particular, raised which limit? memory, CPU or process ?
  4. MarkPW

    MarkPW New Member

    In Security tab, I set memory soft limit and hard limit to 0 and in lsphp5 the soft and hard limit to 1384M.

    Will I face any issues having the config like this? On my old server from which I am migrating, settings were 250M soft and 300M hard memory limit and I had no problems executing the above shell command.

    Thanks
  5. NiteWave

    NiteWave Administrator

    those limits are to prevent bad processes to consume too many memory. if your server runs well without those limit, should be ok.

    maybe java version etc different on old and new server?
    /usr/java/jdk1.7.0_17/bin/java

    how about your migrating progress ? is the high io issue gone on the new server?

Share This Page