PHP cgi wrapper created with wrong paths

Discussion in 'General' started by Norman, Nov 17, 2010.

  1. Norman

    Norman Member HowtoForge Supporter

    I'm having an issue with PHP cgi wrapper created with the wrong paths.
    It creates "client\[client_id\]" in the path instead of "client1".

    Running latest version.
    Tried switching between FastCGI to MODPHP and then back. No luck.
    For now I've edited the path manually to have the client1 instead of above. Any fix for this, or cause of it?


    Code:
    #!/bin/sh
    PHPRC="/etc/php5/cgi/"
    export PHPRC
    PHP_DOCUMENT_ROOT="/var/www/clients/client1/web1"
    export PHP_DOCUMENT_ROOT
    # The variable PHP_FCGI_CHILDREN is onyl useful for lighty or nginx as apache
    # mod_fcgi will control the number of childs themself and never use the additional processes.
    # PHP_FCGI_CHILDREN=8
    # export PHP_FCGI_CHILDREN
    PHP_FCGI_MAX_REQUESTS=5000
    export PHP_FCGI_MAX_REQUESTS
    exec /usr/bin/php-cgi \
     -d open_basedir="/var/www/clients/client\[client_id\]/web1/web:/var/www/clients/client\[client_id\]/web1/tmp:/var/www/domain.com/web:/srv/www/domain.com/web$
    -d upload_tmp_dir=/var/www/clients/client1/web1/tmp \
    -d session.save_path=/var/www/clients/client1/web1/tmp \
     $1
     
  2. falko

    falko Super Moderator ISPConfig Developer

    What's your ISPConfig version?
     
  3. Norman

    Norman Member HowtoForge Supporter

    Latest version.
    Although the this problem appeared in an older.

    But the newer didnt fix it.
     
  4. falko

    falko Super Moderator ISPConfig Developer

    I've added this to our bugtracker.
     
  5. Norman

    Norman Member HowtoForge Supporter

    It seems to only affect our oldest sites on this server


    /var/www/php-fcgi-scripts/web1/.php-fcgi-starter

    has the wrong paths added after apache configuration changes through ISPconfig

    but /var/www/php-fcgi-scripts/web15/.php-fcgi-starter
    is created properly even when they are the same client.

    Hope this helps in finding the issue :) probably something from an old ISPconfig version that still lingers in a database or something.
     

Share This Page