Articles in this section

Webserver Configurations Troubleshooter detects extra configuration or shows a false positive report on the Home page

Kuzma Ivanov
Updated
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

  • One of the following messages might appear on Plesk Home:

    PLESK_ERROR: Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: ...

    PLESK_ERROR: Due to the following errors in the configuration templates, no new configuration files could be created for the Apache webserver: Can not restart web server: graceful restart failed, perform full restart httpd stop failed 9 / usr / sbin / httpd processes are killed

    PLESK_ERROR: Template processing failed: file = /usr/local/psa/admin/conf/templates/default/domainVhost.php, error = Template_Exception: No data. file: /usr/local/psa/admin/plib/Template/Processor.php line: 28 code: 0 Previous error: <...>

  • When opening Tools & Settings > Webserver Configurations Troubleshooter and filtering status by "Error", records with "File Path: N/A" or "Related domain: Deleted" are shown.
  • Webserver Configurations Troubleshooter shows one of the following messages:

    • When checking configurations:

      PLESK_INFO: There is an extra configuration with id X belongs to the missed domain with id Y

    • When rebuilding configurations:

      PLESK_ERROR: Error: Can not reconfigure web server configurations: Unable to execute httpdmng: Domain with name '' does not exist

  • Apache and nginx (if enabled) web-servers are up and running and their configuration is does not have any errors:

    # apachectl -t
    Syntax OK

    # nginx -t
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

Cause

The Plesk database contains records about non-existent configuration files or old error messages.

Resolution

Remove the old information via Plesk:

  1. Log in to Plesk.

  2. Go to Tools & Settings > Webserver Configurations Troubleshooter.

    Note: If Webserver Configurations Troubleshooter is not shown, install it using Plesk Installer.

  3. Click the mceclip1.png button > set Status search filter to Error from the drop-down menu:


    mceclip1.png
     

  4. The list of broken configuration files will appear. Select all, then click Rebuild > Selected.
  5. If configuration files could not be repaired, select them and click Remove.
  6. Click Check configuration to make sure there is no broken configuration left.

 

Removing the old information via SSH connection

 

  1. Connect to the Plesk server via SSH.

  2. Create a folder for temporary files:

    # mkdir -p /tmp/plesksupport

  3. Create a file with affected domains:

    # MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin psa -Ne"select name from domains where id in (select objectId from Configurations where status<>'ok')" > /tmp/plesksupport/domainlist.txt

  4. Reconfigure the affected domains:

    # cat /tmp/plesksupport/domainlist.txt | while read domain; do plesk repair web -y $domain; echo "$domain - success"; done

    # plesk repair web -server

  5. Remove broken configuration entries from the Plesk database:

    # plesk db "delete from Configurations where status <> 'ok'\G"

  6. Validate configuration files:

    # plesk repair web -validate-configuration

 

Was this article helpful?

Comments

1 comment
Date Votes
  • Avatar
    Luis

    I executed the described procedure and the plesk repair web -v -n still returns the same:

    (…)
Checking for extra configurations in database not owned by any object
 There is an extra configuration with id 1301 belongs to the missed  
 domain with id 349                                                  
 There is an extra configuration with id 1535 belongs to the missed  
 domain with id 400                                                  
 There is an extra configuration with id 1302 belongs to the missed  
 domain with id 349                                                  
 There is an extra configuration with id 1536 belongs to the missed  
 domain with id 400                                                  
 There is an extra configuration with id 2387 belongs to the missed  
 domain with id 400                                                  
 There are some unnecessary configurations in the database. Please   
  check https://support.plesk.com/hc/articles/213389789 for solution  [WARNING]

     

    0

Please sign in to leave a comment.