Start Apache on CentOS to report an error

system version is CentOS 7. Start Apache to report an error

[root@localhost wiki]-sharp service httpd start
Redirecting to /bin/systemctl start  httpd.service
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@localhost wiki]-sharp systemctl status httpd.service
 httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since  2018-10-26 11:32:58 CST; 11s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 43586 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 43584 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 43584 (code=exited, status=1/FAILURE)

10 26 11:32:58 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
10 26 11:32:58 localhost.localdomain httpd[43584]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
10 26 11:32:58 localhost.localdomain httpd[43584]: no listening sockets available, shutting down
10 26 11:32:58 localhost.localdomain httpd[43584]: AH00015: Unable to open logs
10 26 11:32:58 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
10 26 11:32:58 localhost.localdomain kill[43586]: kill: cannot find process ""
10 26 11:32:58 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1
10 26 11:32:58 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
10 26 11:32:58 localhost.localdomain systemd[1]: Unit httpd.service entered failed state.
10 26 11:32:58 localhost.localdomain systemd[1]: httpd.service failed.

the saying found on the Internet is that the port is occupied, and the solution is to find the occupied port and kill the corresponding process, and then restart httpd. But this method doesn"t work for me, because Zen Tao and SVN, have been deployed on the server before, and I checked that the application corresponding to this port is Nginx, and I can"t kill its corresponding process, so what should I do in this case?

Sep.21,2021

  1. first of all, I think it is necessary to evaluate whether there is sufficient reason to deploy Nginx and Apache at the same time. In other words, are there any requirements on Apache that Nginx can't do incidentally?
  2. if there must be a reason, since Nginx is the primary configuration, you need to change the setting of Apache. For example, if you used to listen for interface 80, you can now change it to 8080 or any unoccupied interface, so as to ensure that the two will not conflict.
  3. since Nginx receives requests at the previous level, you need to pick out the requests that should be given to Apache separately and replace them with the interface that Apache listens to. There are too many configurations of Nginx reverse generation on the Internet, so I won't repeat them.
Menu