{"id":6103,"date":"2021-02-08T17:39:28","date_gmt":"2021-02-08T12:09:28","guid":{"rendered":"https:\/\/www.skynats.com\/?p=6103"},"modified":"2024-12-06T17:38:12","modified_gmt":"2024-12-06T12:08:12","slug":"fix-plesk-error-new-files-configuration-for-apache-web-server","status":"publish","type":"post","link":"https:\/\/www.skynats.com\/blog\/fix-plesk-error-new-files-configuration-for-apache-web-server\/","title":{"rendered":"Error: New files of configuration for Apache web server in Plesk"},"content":{"rendered":"\n

We often encounter the Error: New files of configuration for Apache web server in Plesk<\/strong> when accessing the home page of the Plesk control panel. This error can arise due to various reasons, such as the Mailman package not being installed, PHP memory issues, or APS database-related errors. These factors can interfere with the proper functioning of the web server and control panel.<\/p>\n\n\n\n

We handle Plesk errors for our clients by using our Plesk management plan. Our technical team expert will handle and fix the error on behalf of you which is caused due to some following reason. You can check out our Plesk <\/span>management plan<\/span><\/a> for further assistance.<\/p>\n\n\n\n

While accessing the Plesk you will be receiving the below popup message. <\/p>\n\n\n\n

Error:<\/strong> New files of configuration for Apache web server in Plesk were not built due to errors in configuration templates. The detailed error message was e-mailed to you, so please check the mail, fix the error, and click here to retry generating configuration.<\/p>\n\n\n\n

Follow the below steps to fix the issue.<\/p>\n\n\n\n

    \n
  1. Mailman package is not installed<\/strong><\/li>\n<\/ol>\n\n\n\n

    While reconfiguring the domain, you will be experiencing the following error.<\/p>\n\n\n\n

    # \/usr\/local\/psa\/admin\/sbin\/httpdmng --reconfigure-all<\/code><\/pre>\n\n\n\n
    No valid mailman bindir detected<\/p>\n\n\n\n
     In this case, the error is due to the mailman package missing.<\/p>\n\n\n\n
    Follow the below steps to fix this issue<\/strong>.<\/p>\n\n\n\n
    First of all, you need to download and install the mailman package from http:\/\/autoinstall.plesk.com<\/a><\/p>\n\n\n\n
    After that remove all entries from the configuration table of the ‘psa’ database and follow the commands below.<\/p>\n\n\n\n
    mysql -uadmin -p`cat \/etc\/psa\/.psa.shadow` psa -e\"delete from Configurations\"<\/code><\/pre>\n\n\n\n
    Then remove all ‘Include’ records from the configuration files and all the contents from the directory below.<\/p>\n\n\n\n
    # sed -i \/Include\/d \/usr\/local\/psa\/admin\/conf\/ip_vhosts_bootstrap.conf&& sed -i \/Include\/d \/usr\/local\/psa\/admin\/conf\/vhosts_bootstrap.conf&& sed -i \/include\/d \/usr\/local\/psa\/admin\/conf\/nginx_vhosts_bootstrap.conf&& sed -i \/Include\/d \/usr\/local\/psa\/admin\/conf\/webmail_horde_bootstrap.conf&& sed -i \/Include\/d \/usr\/local\/psa\/admin\/conf\/webmail_atmail_bootstrap.conf&& sed -i \/Include\/d \/etc\/httpd\/conf.d\/zz010_psa_httpd.conf&& rm -f \/usr\/local\/psa\/admin\/conf\/generated\/*<\/code><\/pre>\n\n\n\n
    Finally, you can reconfigure and try to fix the issues. <\/p>\n\n\n\n
    \/usr\/local\/psa\/admin\/bin\/httpdmng --reconfigure-all<\/code><\/pre>\n\n\n\n
    Aps database-related error.<\/strong><\/p>\n\n\n\n
    Ensure its DB-related error and follow the below steps.  Run the following commands to check the reason behind the error.<\/p>\n\n\n\n
    mysql -uadmin -p`cat \/etc\/psa\/.psa.shadow ` psa -Nse\"select * from Configurations where status='error' G\"<\/code><\/pre>\n\n\n\n
    Follow the below steps to fix the error.
    First, login into MYSQL and connect to the psa database by using the following commands.<\/p>\n\n\n\n
    # mysql -uadmin -p`cat \/etc\/psa\/.psa.shadow`\nmysql> connect psa<\/code><\/pre>\n\n\n\n
    Then run the below query to find the objectIDs with an error status.<\/p>\n\n\n\n
    mysql> select objectId from Configurations where status='error';\n+----------+\n| objectId |\n+----------+\n| 8 |\n+----------+\n1 row in set (0.00 sec)<\/code><\/pre>\n\n\n\n
    From the above result you will get the objectId that will find out the domain by using the ID. <\/pre>\n\n\n\n
    mysql> select id,name,parentDomainId from domains where id=8;\n+----+------------------+----------------+\n| id | name | parentDomainId |\n+----+------------------+----------------+\n| 8 | test.com | 0 |\n+----+------------------+----------------+\n1 row in set (0.00 sec)<\/code><\/pre>\n\n\n\n
    We will get the subscription ID for the specified domain.<\/p>\n\n\n\n
    mysql> select id, object_id from Subscriptions where object_id=8\n+----+-----------+\n| id | object_id |\n+----+-----------+\n| 5 | 8 |\n+----+-----------+\n1 row in set (0.00 sec)<\/code><\/pre>\n\n\n\n
    Later check the subscription has entries in the APS context table.<\/p>\n\n\n\n
     mysql> SELECT `apsContexts`.* FROM `apsContexts` AS `apsContexts` WHERE (`pleskType` = 'hosting' AND `pleskId` =8 );\n+----+-----------+---------+-------+----------------+\n| id | pleskType | pleskId | ssl | subscriptionId |\n+----+-----------+---------+-------+----------------+\n| 5 | hosting | 8 | false | 0 |\n+----+-----------+---------+-------+----------------+\n1 row in set (0.00 sec)<\/code><\/pre>\n\n\n\n
     As you can see the subscription ID to be different from the Plesk ID.<\/p>\n\n\n\n
    mysql> update apsContexts set subscriptionId=5 where pleskId=8;\nQuery OK, 1 row affected (0.01 sec)\nRows matched: 1 Changed: 1 Warnings: 0<\/code><\/pre>\n\n\n\n
    Finally, you can reconfigure and then fix the issues.<\/p>\n\n\n\n
    \/usr\/local\/psa\/admin\/bin\/httpdmng --reconfigure-all<\/code><\/pre>\n\n\n\n
    PHP Memory issue<\/strong><\/p>\n\n\n\n
     You can check the PHP memory issue in the ‘\/var\/log\/sw-cp-server\/error_log’<\/p>\n\n\n\n
    \u00a0<\/strong>cat \/var\/log\/sw-cp-server\/error_log<\/pre>\n\n\n\n
    PHP Fatal error: allowed memory size of 134217728 bytes exhausted (tried to allocate 7680 bytes)<\/strong><\/pre>\n\n\n\n
    The error is due to the Plesk PHP memory limit.<\/p>\n\n\n\n
    Follow the steps to solve the issue.<\/strong><\/p>\n\n\n\n
    Try to set the Php memory _limit” parameter in”\/usr\/local\/psa\/admin\/conf\/php.ini” into a high value than the current one.<\/p>\n\n\n\n
    Try to remove the old error messages (non-existent configuration files) via the Plesk interface or through the SSH connection.<\/p>\n\n\n\n
    Follow the steps to remove the old error via the Plesk interface:<\/strong><\/p>\n\n\n\n