• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Unit httpd.service has failed

seabiscuit

New Pleskian
Hi,
Can someone guide me on this? Thanks...

***** problem report *****
Warning: start service httpd failed

/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.

file: /usr/local/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 137
code: 0

Please resolve the errors in web server configuration templates and generate the file again.

-- Unit httpd.service has begun starting up.
Jan 14 19:36:53 serveraddress httpd[17947]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Jan 14 19:36:53 serveraddress httpd[17947]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Jan 14 19:36:53 serveraddress httpd[17947]: no listening sockets available, shutting down
Jan 14 19:36:53 serveraddress httpd[17947]: AH00015: Unable to open logs
Jan 14 19:36:53 serveraddress systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jan 14 19:36:53 serveraddress systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit httpd.service has failed.

Also the error log:
[Thu Jan 14 16:25:09.335079 2021] [mpm_event:notice] [pid 24402:tid 140564366694528] AH00492: caught SIGWINCH, shutting down gracefully
 
Hi....
I resolved it following this after reading countless posts: Unable to start apache on Plesk for Linux: (98)Address already in use: make_sock: could not bind to address [::]:443

I just applied the 5th step.

My question now is that before stop/restarting the nginx,
"netstat -tulpn | grep :443" and "netstat -tulpn | grep :80" returned " 0.0.0.0:* LISTEN 13498/nginx: worker"

Afterwards both commands returned " 0.0.0.0:* LISTEN 2194/nginx: master"

I just wanna use nginx as proxy. Does this cause a problem?

And the ultimate question is why all this happpend at the first place. I didnt do anything special to put myself in such a situation.

Any feedback would be appreciated. Thanks
 
Back
Top