Resolved Cannot restart web server apache is down!

[GermanMazza]

Hi, how can I resolve this? I cannot find precise information about this error:
***** is my server name, the configuration files where generated again but issue persist. Configuration troubleshooter does not load, keeps loading forever

New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: Apache is down, start it instead of graceful httpd stop failed 7 /usr/sbin/httpd processes are killed Apache is down, start it instead of graceful INFO: [Wed Aug 19 09:01:04 EEST 2020]: Service: httpd, Action: stop Trying to stop service httpd... attempt to stop service httpd - service doesn't exist (missing unit file or not executable control script) Jul 21 05:56:41 *****.com.ar systemd[1]: Stopped The Apache HTTP Server. Jul 21 05:56:41 *****.com.ar systemd[1]: Starting The Apache HTTP Server... Jul 21 05:57:23 *****.com.ar systemd[1]: Started The Apache HTTP Server. Jul 21 05:58:53 *****.com.ar systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL Jul 21 05:58:53 *****.com.ar systemd[1]: Unit httpd.service entered failed state. Jul 21 05:58:53 *****.com.ar systemd[1]: httpd.service failed. Jul 21 05:59:36 *****.com.ar systemd[1]: httpd.service holdoff time over, scheduling restart. Jul 21 06:00:21 *****.com.ar systemd[1]: Stopped The Apache HTTP Server. Jul 21 06:00:21 *****.com.ar systemd[1]: Starting The Apache HTTP Server... Jul 21 06:01:07 *****.com.ar systemd[1]: Started The Apache HTTP Server. ***** problem report ***** Warning: stop service httpd failed /usr/local/psa/admin/sbin/pleskrc execution failed: Failed to list unit files: Connection timed out httpd stop failed 6 /usr/sbin/httpd processes are killed INFO: [Wed Aug 19 09:03:03 EEST 2020]: Service: httpd, Action: start Trying to start service httpd... attempt to start service httpd - service doesn't exist (missing unit file or not executable control script) Jul 21 05:56:41 *****.com.ar systemd[1]: Stopped The Apache HTTP Server. Jul 21 05:56:41 *****.com.ar systemd[1]: Starting The Apache HTTP Server... Jul 21 05:57:23 *****.com.ar systemd[1]: Started The Apache HTTP Server. Jul 21 05:58:53 *****.com.ar systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL Jul 21 05:58:53 *****.com.ar systemd[1]: Unit httpd.service entered failed state. Jul 21 05:58:53 *****.com.ar systemd[1]: httpd.service failed. Jul 21 05:59:36 *****.com.ar systemd[1]: httpd.service holdoff time over, scheduling restart. Jul 21 06:00:21 *****.com.ar systemd[1]: Stopped The Apache HTTP Server. Jul 21 06:00:21 *****.com.ar systemd[1]: Starting The Apache HTTP Server... Jul 21 06:01:07 *****.com.ar systemd[1]: Started The Apache HTTP Server. ***** problem report ***** Warning: start service httpd failed /usr/local/psa/admin/sbin/pleskrc execution failed: Failed to list unit files: Connection timed out . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files. See the details in Configuration Troubleshooter

 

[GermanMazza]

Now the error message is updated after trying to re build the broken configuration files:

New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: Apache is down, start it instead of graceful httpd stop failed 7 /usr/sbin/httpd processes are killed Apache is down, start it instead of graceful INFO: [Wed Aug 19 16:40:29 EEST 2020]: Service: named-chroot, Action: status Jul 21 05:56:41 *****.com.ar systemd[1]: Stopped The Apache HTTP Server. Jul 21 05:56:41 *****.com.ar systemd[1]: Starting The Apache HTTP Server... Jul 21 05:57:23 *****.com.ar systemd[1]: Started The Apache HTTP Server. Jul 21 05:58:53 *****.com.ar systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL Jul 21 05:58:53 *****.com.ar systemd[1]: Unit httpd.service entered failed state. Jul 21 05:58:53 *****.com.ar systemd[1]: httpd.service failed. Jul 21 05:59:36 *****.com.ar systemd[1]: httpd.service holdoff time over, scheduling restart. Jul 21 06:00:21 *****.com.ar systemd[1]: Stopped The Apache HTTP Server. Jul 21 06:00:21 *****.com.ar systemd[1]: Starting The Apache HTTP Server... Jul 21 06:01:07 *****.com.ar systemd[1]: Started The Apache HTTP Server. ***** problem report ***** Warning: stop service httpd failed /usr/local/psa/admin/sbin/pleskrc execution failed: Failed to list unit files: Connection timed out httpd stop failed 7 /usr/sbin/httpd processes are killed INFO: [Wed Aug 19 16:43:01 EEST 2020]: Service: pc-remote, Action: status /usr/local/psa/admin/sbin/pleskrc execution failed: Failed to list unit files: Connection timed out . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files. See the details in Configuration Troubleshooter

 

[moswak]

Failed to list unit files: Connection timed out

could be this bug

Plesk fails to restart services: control script doesn't exist or isn't executable

Applicable to: Plesk for Linux Symptoms The following error is shown in Plesk UI: PLESK_ERROR: New configuration flies for the Apache web server were not created due to the errors in configura...

support.plesk.com

 

[GermanMazza]

I'm gonna check right now.
Is it wise to update from plesk 18.0.27 to 18.0.29 with this error?

 

[moswak]

I would fix the error first and then do the update

 

[GermanMazza]

Ok! I've fixed the issue. Did this kb article solution: Plesk fails to restart services: control script doesn't exist or isn't executable
Then applied plesk repair web **** (to all webs)
Then applied plesk reapir all several times.
I had to do this several times before the server was back to normal