1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Plesk 10.4.4 httpd.include problem after MU30

Discussion in 'Plesk 10.x for Linux Issues, Fixes, How-To' started by chris_cross, May 12, 2012.

  1. chris_cross

    chris_cross New Pleskian

    22
    73%
    Joined:
    Mar 4, 2007
    Messages:
    15
    Likes Received:
    0
    Hi there,

    I had a working installation of Plesk 10.4.4 running Debian 6.
    After the micro update #30 I hat to realize, that web server configuration tool (/usr/local/psa/admin/bin/httpdmng --reconfigure-all) does not work any more.

    There have been different errors revealing basically, that path information does not match.

    e.g.:
    Syntax error on line 52 of /var/www/vhosts/domain.de/conf/13368257930.86481000_httpd.include:
    SSLCertificateFile: file '/var/certificates/certPn979YK' does not exist or is empty

    The cert files are located in /usr/local/psa/var/cerficates not in /var/...
    Even by deleting the .include files they are generated with the wrong path again.
    Same thing for the httpd.include files /admin/conf/generated/... that are physically on /opt/psa/conf/generated/...
    I tried to fix it by pointing to the original folders using sym links. Never the less the latest error revealed:

    So somehow the update forgot about the install paths of plesk.

    Is there a possibility of switching back to the last working micro update? Or has anybody an idea, how to fix it?

    Thanks in advance

    Chris
     
  2. chris_cross

    chris_cross New Pleskian

    22
    73%
    Joined:
    Mar 4, 2007
    Messages:
    15
    Likes Received:
    0
    I fixed the httpd.include problems, by disabling FastCGI support.
    As a result of the update php/fastcgi does not work any more.

    Additionally logrotation fails as well as the backup manager.
    The backup issue is a thing that worries me most.

    The backup.xml files are marked "green" / readable or "red".
    If "green" by clicking it reveals errors like this:
    The file plesk mentioned exists physically on the server and contains the structure of a regular backup (mail users, domains, certificates etc)

    If "red":
    I am rather frustrated that a working system is screwed by a minor update.
     
    Last edited: May 14, 2012
  3. chris_cross

    chris_cross New Pleskian

    22
    73%
    Joined:
    Mar 4, 2007
    Messages:
    15
    Likes Received:
    0
    found the error with the backup manager.

    Plesk creates an invalid backup.xml file. The data (tgz) part is correct.

    The xml file is missing an close of the </Envelope> tag.

    I manually added the tag and the file was readable via the interface.

    Can anybody tell me where I can find the file/function that builds the xml template?
     
  4. dash

    dash Regular Pleskian Staff Member

    28
    40%
    Joined:
    Sep 26, 2007
    Messages:
    204
    Likes Received:
    47
    Hi,
    As I can see the problem is that fastcgi wrapper path is missed in generated apache configs.
    Please try to perform the following checks:
    1) /usr/local/psa/admin/sbin/serverconf -l|grep CGI_PHP_BIN
    (or /opt/psa/... in case of Debian system)
    The command should return full path to cgi_wrapper
    The file should exists:
    # ls -l /var/www/cgi-bin/cgi_wrapper/cgi_wrapper
    -rwxr-xr-x 1 root root 3688 Nov 1 2011 /var/www/cgi-bin/cgi_wrapper/cgi_wrapper

    2) mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e "select value from ServiceNodeProperties where name like '%CGI_PHP_BIN%'";
    Should return the same value

    3) If result on previous step (2) is not correct try to resync server configuration in Plesk database:
    mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e "delete from ServiceNodeProperties where name='server.configuration.synced'"

    4) Try to reconfigure web server:
    /usr/local/psa/admin/bin/httpdmng --reconfigure-all

    P.S. At the moment I see no reasons to think the issue is related to MU#30
     
  5. chris_cross

    chris_cross New Pleskian

    22
    73%
    Joined:
    Mar 4, 2007
    Messages:
    15
    Likes Received:
    0
    First of all, thanks for your reply, dash.

    The wrapper exists under the expected path

    as well as in the database

    all domains are synced (i did that after disabling fcgi for all domains)

    Yesterday evening I restarted the whole server.
    I just tried to activate fcgi for one domain and build the apache config via /usr/local/psa/admin/bin/httpdmng --reconfigure-domain my.domain.com.
    This worked without any problem. Maybe my recent changes of all abonnements or the restart did the trick.

    The backup issue still remains. Every backup will be written with a xml file with a missing </Envelope> tag. So the integrity check fails. This prevents backups to the ftp repository. By fixing the xml file manually, transfer to ftp repo works.
     
  6. dash

    dash Regular Pleskian Staff Member

    28
    40%
    Joined:
    Sep 26, 2007
    Messages:
    204
    Likes Received:
    47
    Looks like backup signing procedure failure.

    What are openssl and perl versions?
    dpkg -l | egrep 'perl-base|openssl'

    Try to execute the following command:
    /usr/local/psa/admin/sbin/backup_sign sign /var/lib/psa/dumps/<dump name>.xml

    where <dump_name> is one of your dumps.
    It should add signature to your dump and pass result to the output,
    but most probably it will fail. If so, what is error message?
     
  7. chris_cross

    chris_cross New Pleskian

    22
    73%
    Joined:
    Mar 4, 2007
    Messages:
    15
    Likes Received:
    0
    Thanks again, dash.

    Perl and OpenSSL should be up-to-date.

    The backup_sign script gave the decisive hint:

    So I created a server key by:
    Then I created a new backup (via web interface) with no errors.
    The XML now looks well formed and has signature and envelope. The backup file can be opened by Plesk and can be restored as far as it seems.

    Now that the local backup runs without errors, backing up into ftp repo works as well.

    Thanks a lot for your help!

    Chris
     
  8. dash

    dash Regular Pleskian Staff Member

    28
    40%
    Joined:
    Sep 26, 2007
    Messages:
    204
    Likes Received:
    47
    Very good

    Thanks for your detailed feedback!
     
Loading...