Hello, installing apache server on a raspberry pi and not sure what is going on. Im new to Linux and i have no clue how to troubleshoot this. This is what pops up when im trying to install apache server on my Raspberry. I did try to uninstall it and install it again and it just repeats. Please help!!
Thank you.

Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apache2, action "restart" failed.
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2023-06-21 18:19:51 EDT; 24ms ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 3269 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

Jun 21 18:19:51 deephole apachectl[3269]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
Jun 21 18:19:51 deephole apachectl[3269]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Jun 21 18:19:51 deephole apachectl[3269]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Jun 21 18:19:51 deephole apachectl[3269]: no listening sockets available, shutting down
Jun 21 18:19:51 deephole apachectl[3269]: AH00015: Unable to open logs
Jun 21 18:19:51 deephole apachectl[3269]: Action 'start' failed.
Jun 21 18:19:51 deephole apachectl[3269]: The Apache error log may have more information.
Jun 21 18:19:51 deephole systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Jun 21 18:19:51 deephole systemd[1]: apache2.service: Failed with result 'exit-code'.
Jun 21 18:19:51 deephole systemd[1]: Failed to start The Apache HTTP Server.

Hi,
There is already a webserver running and listening on port 80, so apache cannot uses it.

You can run the following command to see what process uses port 80 and its PID, so you can kill it and try to start apache:
Regards

installing Apache shouldn't be an issue it is setting it up that requires reading the documentation, and as far as the other post about port 80 if it is being used by someone else then you have to resign it if you want Apache using port 80 or you're always going to run into issues with the other always wanting to use it too. so give Apache a different port if need be or visa versa.