4.1.1 Build 3 -- include_path error?

Discussion in 'Bug Reports' started by DraCoola, Jun 23, 2011.

  1. DraCoola

    DraCoola Well-Known Member

    using this build since yesterday and were throwing out errors like these on wordpress and joomla (as far as i currently know) :

    happened on most scripts, anyway.
    which are suddenly asking for /home/username/php

    i have done rebuild matching php (5.2.17) with LSAPI and continue with easyapache but still no luck.
    and also done force reinstall lsws 4.1.1.
    i am back to v4.1 for this moment in order to remove those errors.
  2. mistwang

    mistwang LiteSpeed Staff

    Can you please check phpinfo() page with 4.1 and 4.1.1, compare "include_path" configuration.
    Also Please check Apache httpd.conf see if there is any configuration with value "/home/username/php". it has to come from somewhere, LSWS wont add something by itself.
  3. DraCoola

    DraCoola Well-Known Member

    phpinfo() from 4.1 and 4.1.1 are using the same configuration from /usr/local/lib/php.ini
    so they both are using the same :

    include_path = ".:/usr/lib/php:/usr/local/lib/php" 
    i even replaced php.ini with php.ini from my another plain apache server (suphp) just to make sure.
    and also search httpd.conf from "phpinidir" or any of "/home/username/php" entries but found nothing there.

    downgrade from 4.1.1 to 4.1 just fix it self from this error include_path :confused:
    Last edited: Jun 23, 2011
  4. mistwang

    mistwang LiteSpeed Staff

    maybe we need to login and take a look.
  5. DraCoola

    DraCoola Well-Known Member

    pm sent, george.
    thanks before :)

    by the way using 4.1 makes mod security on WHM cannot produce the logs.
    but 4.1.1 does work for mod security logs on WHM interface.
    unfortunatelly, 4.1.1 did php "include_path" errors.
  6. mistwang

    mistwang LiteSpeed Staff

    those bad include_path configuration is from
    Is there any WHM option to get rid of those files? Path configuration in those files are wrong.
  7. DraCoola

    DraCoola Well-Known Member

    Glad that you are finally found the problem, george. Thank you for investigate.
    So this means lsws below 4.1.1 doesn't read those include file from httpd.conf?
    Because the file was on there since year 2010 :

    -rw-r-----   1 root root   839 Dec 20  2010 cp_php_magic_include_path.conf
    I don't have an idea about from where the conf files has created.
    WHM does not have an option to remove those files.
    But I will find that way somewhere from google.

    So it is safe to just remove those bad files in order to use 4.1.1 without include_path errors?
  8. mistwang

    mistwang LiteSpeed Staff

    4.1 read configuration in section of
    <IfModule concurrent_php.c>

    while 4.1.1 read configuration in section of
    <IfModule !concurrent_php.c>

    php4_admin_value and php5_admin_value are ignored, so 4.1 does not set include_path.

    Yes, I think it is safe to remove those files.
  9. DraCoola

    DraCoola Well-Known Member

    So I have to mass remove for many files of cp_php_magic_include_path.conf from all of my servers.
    Because most accounts are just have it while I grep that.

    I hope can soon find for which software that has responsible for creating those files.
    So I can disable that immediately.

    Thank you for assist, george!
    Last edited: Jun 25, 2011
  10. DraCoola

    DraCoola Well-Known Member

  11. DraCoola

    DraCoola Well-Known Member

    UPDATE :

    PEAR and it's php application packages can still use after disable Cpanel php magic.
    But users must manually edit/add their script with :

    ini_set("include_path", '/home/username/php:' . ini_get("include_path")  );
    This will sometimes hard to explain to wordpress/joomla newbie-user that want to use *for an example* smtp mail function from their site.

    Is there any possible way for lsws to not read Include "/usr/local/apache/conf/userdata/std/2/*.conf" on httpd.conf?
  12. mistwang

    mistwang LiteSpeed Staff

    I think you can update cpanel vhost template, not to do that by default.
    4.1 and earlier release does not apply include_path configuration in those files anyway, I think it is safe to remove all of them.

Share This Page