Forwarded to devs Apache will not start

[DRY411S]

User name: DRY411S

TITLE

Apache will not start

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

OS ‪CentOS Linux 7.7.1908 (Core)‬
Product Plesk Onyx
Version 17.8.11 Update #80, last updated on Jan 27, 2020 08:13 AM

Running on GCP, acquired through GCP Marketplace.

PROBLEM DESCRIPTION

Please see Issue - Can not restart web server / New configuration files for the Apache web server were not created. The error messages reported last August, are recurring since update #80 this morning.

STEPS TO REPRODUCE

Making practically ANY change to Apache config that causes the httpd service to be restarted causes failure.

ACTUAL RESULT

New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: INFO: [Mon Jan 27 18:05:30 UTC 2020]: Service: httpd, Action: start Trying to start service httpd... failed Jan 27 18:05:31 <myserver> systemd[1]: Starting The Apache HTTP Server... Jan 27 18:05:31 <myserver> systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE Jan 27 18:05:31 <myserver> kill[6487]: kill: cannot find process "" Jan 27 18:05:31 <myserver> systemd[1]: httpd.service: control process exited, code=exited status=1 Jan 27 18:05:31 <myserver> systemd[1]: Failed to start The Apache HTTP Server. Jan 27 18:05:31 <myserver> systemd[1]: Unit httpd.service entered failed state. Jan 27 18:05:31 <myserver> systemd[1]: httpd.service failed. WARNING! Some problems are found during start service httpd(see log file: /var/log/plesk/rc_actions.log) Continue... /usr/local/psa/admin/sbin/pleskrc execution failed: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. . 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

EXPECTED RESULT

No errors

ANY ADDITIONAL INFORMATION

/var/log/plesk/rc_actions.log

START pleskrc
INFO: [Mon Jan 27 18:05:28 UTC 2020]: Service: httpd, Action: start
Trying to start service httpd... failed
Jan 27 18:05:29 <myserver> systemd[1]: Starting The Apache HTTP Server...
Jan 27 18:05:29 <myserver> systemd[1]: httpd.service: main process exited, code=exited, status=1/FAI
LURE
Jan 27 18:05:29 <myserver> kill[6332]: kill: cannot find process ""
Jan 27 18:05:29 <myserver> systemd[1]: httpd.service: control process exited, code=exited status=1
Jan 27 18:05:29 <myserver> systemd[1]: Failed to start The Apache HTTP Server.
Jan 27 18:05:29 <myserver> systemd[1]: Unit httpd.service entered failed state.
Jan 27 18:05:29 <myserver> systemd[1]: httpd.service failed.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[DRY411S]

I have tried all the plesk repair web options. Configuration checking options says nothing is wrong, but Apache refuses to start.

 

[IgorG]

due to the errors in configuration templates

Are there any customized configuration templates on that server?

I think inspecting of /var/log/httpd/error.log or /var/log/plesk/panel.log could shed some light on the problem.

 

[DRY411S]

I have resolved this. I will post the cause later, it may help others. For the record, the cause was NOT by latest update #80, it was something I did, but I would argue that the error messages don't help getting to the root cause. Will post more later.

 

[DRY411S]

This issue was caused by me adding Apache and nginx directives via PLESK panel into the top level domain that is used by everybody who accesses PLESK for their domains.

I had added some SSLcertificate directives for a new certificate that I have acquired. The Let's Encrypt extension was already getting a different certificate, and PLESK automatically adding directives for that certificate. There were therefore duplicate certificate directives in the Apache httpd.conf files.

Removing the directives that I had added got rid of the issue.

This 'ticket' is resolved as far as I am concerned. Cause was user error.

 

[Monty]

Try this:

# plesk repair web -y