- Plesk 12.5 for Linux
- Plesk Onyx for Linux
Apache and nginx (if enabled) web-servers are running fine and their configuration is successful:
# apachectl -t
# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Webserver Configuration Troubleshooter shows any of the following error messages:
when checking configuration in Webserver Configurations Troubleshooter:
PLESK_INFO: In some cases, extra webserver configuration files remaining after removing domains might cause conflicts with webserver configuration rebuild process.
PLESK_INFO: There is an extra configuration with id 6 belongs to the missed domain with id 1
when rebuilding domain configuration and the process fails:
PLESK_ERROR: Error: Can not reconfigure web server configurations: Unable to execute httpdmng: Domain with name '' does not exist
PLESK_ERROR: Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server
A similar to the below error message appears on the Home page in Plesk
PLESK_ERROR: New configuration files for the Apache web server were not created due to the errors in configuration templates: ...
PLESK_ERROR: WARNING! Some problems are found during start service apache2(see log file: /var/log/plesk/rc_actions.log) Continue... /opt/psa/admin/sbin/pleskrc execution failed:
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
INFO: Service: Some problems are found during attempt to graceful service httpd - control script does not exist or is not executable (see log file: /var/log/plesk/rc_actions.log)
Plesk Administrator may receive an email with one of the error messages above.
The following command returns a non-empty result when running via SSH:
# plesk db "select c.id, c.objectId as 'domain_id' from Configurations c left join domains d on c.objectId=d.id where c.objectType in ('domain', 'nginxDomain') and d.id is null;"
The issue with web-server configuration has been previously fixed, but the Plesk database still contains records about non-existent configuration files or old error messages.
Open Webserver Configuration Troubleshooter at Tools & Settings in Plesk Onyx 17.8 and from the Extensions menu in Plesk 17.5/17.0/12.5.
Note: If the Webserver Configuration Troubleshooter component is not installed, install it using this KB article.
Click on the button, then set Status to "Error" from the drop-down menu.
The list of broken configuration files will appear. Select all, then click Rebuild > Selected.
If configuration files could not be repaired, select them and click Remove.
Click Check configuration to make sure there is no broken configuration left.