I asked Doug to give me troubleshooting problems so he simulated one that he gives to interviewees at BYU that are applying for the System Administrator position. He didn't tell me what it would be till it was set up and most of the class he was working with another student that was practicing setting up VLANs and what he was doing took the whole network down because of what a student before him did somehow. But he got it set up so I could do it in the last half hour of class. He said they usually give interviewees ten to fifteen minutes and they get a username and a password and the IP address of a website that is malfunctioning, and they get to use the internet to troubleshoot.
So it was set up and he gave me a username and a password for administrative access to the web server he just set up for me, and the IP address of a website, and it didn't occur to me to go to the website, he said it was down. I just immediately set out to SSH into it and in the middle of trying to do this, the network went down again from VLAN problems. After another fifteen minutes or so, I finally got to see if I could SSH into it, which I did successfully.
He had told me that the website was down and they didn't know why and that it was using Apache to deliver web pages. I immediately thought of that scene in The Social Network when Mark told Edwardo that he needed to buy a Linux box running Apache with a MySQL backend. I looked it up many years ago and had very little idea of what he was talking about except that I knew what Linux was. But now because of this, I was aware that Apache had something to do with delivering the website to users.
SO when he mentioned Apache and said the site wasn't loading, I immediately suspected Apache. I went to ChatGPT to see if this could be resolved with it's help:
To ChatGPT - how to check if apache is running? I am ssh-ed into a web server. It runs linux.
ChatGPT - sudo systemctl status apache2
admin@skibidi-slicers:~$ sudo systemctl status apache2
[sudo] password for admin:
○ apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2024-11-05 03:26:15 UTC; 18min ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 24655 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
Process: 24920 ExecStop=/usr/sbin/apachectl graceful-stop (code=exited, status=0/SUCCESS)
Main PID: 24666 (code=exited, status=0/SUCCESS)
CPU: 564ms
Nov 05 02:07:10 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
Nov 05 02:07:10 skibidi-slicers apachectl[24665]: AH00558: apache2: Could not reliably determine the server's fully qua>
Nov 05 02:07:10 skibidi-slicers systemd[1]: Started The Apache HTTP Server.
Nov 05 03:26:05 skibidi-slicers systemd[1]: Stopping The Apache HTTP Server...
Nov 05 03:26:05 skibidi-slicers apachectl[24922]: AH00558: apache2: Could not reliably determine the server's fully qua>
Nov 05 03:26:15 skibidi-slicers systemd[1]: apache2.service: Deactivated successfully.
Nov 05 03:26:15 skibidi-slicers systemd[1]: Stopped The Apache HTTP Server.
ChatGPT said that it was started and later stopped. I wondered if perhaps Apache just wasn't running or someone turned it off or if there was some error, so I decided to start it. I asked ChatGPT how to start it.
ChatGPT - sudo systemctl start apache2
admin@skibidi-slicers:~$ sudo systemctl start apache2
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details.
I was about to try and figure out why it was stopping, and was going to ask ChatGPT how to check but Doug pointed out the above highlighted response and thought I would just go with that.
admin@skibidi-slicers:~$ sudo journalctl -xeu apache2.service
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qua>
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to add>
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to add>
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 20229 and the job result is failed.
ESCOC
check HTTP Server...
execution
pache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' di>
is already in use: AH00072: make_sock: could not bind to address [::]:80
is already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
ng sockets available, shutting down
unable to open logs
art' failed.
error log may have more information.
Control process exited, code=exited, status=1/FAILURE
as exited.
1.
Failed with result 'exit-code'.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qua>
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to add>
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to add>
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
lines 36-64/77 85%
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOC
P Server...
n
Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to s>
dy in use: AH00072: make_sock: could not bind to address [::]:80
dy in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
ets available, shutting down
o open logs
iled.
log may have more information.
l process exited, code=exited, status=1/FAILURE
ed.
with result 'exit-code'.
ult 'exit-code'.
che HTTP Server.
.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOC
P Server...
n
Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to s>
dy in use: AH00072: make_sock: could not bind to address [::]:80
dy in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
ets available, shutting down
o open logs
iled.
log may have more information.
l process exited, code=exited, status=1/FAILURE
ed.
with result 'exit-code'.
ult 'exit-code'.
che HTTP Server.
.
ESCOC
ame, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
ESCOC
ppress this message
ESCOC
ESCOD
ppress this message
ESCOD
ame, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
ESCOD
P Server...
n
Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to s>
dy in use: AH00072: make_sock: could not bind to address [::]:80
dy in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
ets available, shutting down
o open logs
iled.
log may have more information.
l process exited, code=exited, status=1/FAILURE
ed.
with result 'exit-code'.
ult 'exit-code'.
che HTTP Server.
.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
ESCOC
P Server...
n
Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to s>
dy in use: AH00072: make_sock: could not bind to address [::]:80
dy in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
ets available, shutting down
o open logs
iled.
log may have more information.
l process exited, code=exited, status=1/FAILURE
ed.
with result 'exit-code'.
ult 'exit-code'.
che HTTP Server.
.
ESCOD
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit apache2.service has finished.
░░
░░ The job identifier is 19786 and the job result is done.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 20229.
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00558: apache2: Could not reliably determine the server's fully qualified domain >
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: no listening sockets available, shutting down
Nov 05 03:46:41 skibidi-slicers apachectl[25117]: AH00015: Unable to open logs
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: Action 'start' failed.
Nov 05 03:46:41 skibidi-slicers apachectl[25114]: The Apache error log may have more information.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 05 03:46:41 skibidi-slicers systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Nov 05 03:46:41 skibidi-slicers systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
At this point I had not understood that "is already in use: AH00072: make_sock: could not bind to address [::]:80 is already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80" was referring to ports. It said sockets and I didn't know. I had asked ChatGPT about the output the server gave me and it gave two answers, but one of them talked about port 80 already being in use and I thought, oh, HTTP is already in use. I remembered back when I had made a Pi Hole and Pi VPN and to access it, there was a web interface. And from my understanding, this used port 80. And then one of my next projects was to create a self hosted password manager. But one of the snags I ran into was that to access it, I would need to host my own website. And this couldn't be done because I was already hostin a website basically so I could access my Pi Hole through the web interface. So if that was going to be solved, Doug had the idea ot try and use a free domain. I ultimately ended up scrapping the project for other reasons but I remembered this, that it couldn't host more than one site from one public IP address.
I asked ChathGPT how to see what all was running on port 80 and entered in one of its responses.
admin@skibidi-slicers:~$ sudo lsof -i :80
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nginx 24974 root 6u IPv4 251337 0t0 TCP *:http (LISTEN)
nginx 24974 root 7u IPv6 251338 0t0 TCP *:http (LISTEN)
nginx 24975 www-data 6u IPv4 251337 0t0 TCP *:http (LISTEN)
nginx 24975 www-data 7u IPv6 251338 0t0 TCP *:http (LISTEN)
nginx 24976 www-data 6u IPv4 251337 0t0 TCP *:http (LISTEN)
nginx 24976 www-data 7u IPv6 251338 0t0 TCP *:http (LISTEN)
nginx 24977 www-data 6u IPv4 251337 0t0 TCP *:http (LISTEN)
nginx 24977 www-data 7u IPv6 251338 0t0 TCP *:http (LISTEN)
nginx 24978 www-data 6u IPv4 251337 0t0 TCP *:http (LISTEN)
nginx 24978 www-data 7u IPv6 251338 0t0 TCP *:http (LISTEN)
I went to ChtGPT to learn what NGINX was. One of the many things it said was that "Nginx (pronounced "engine-ex") is a high-performance web server and reverse proxy server that is also used for load balancing, HTTP caching, and serving static files. It was created by Igor Sysoev and first released in 2004. Nginx is known for its ability to handle a large number of concurrent connections efficiently, making it popular for high-traffic websites."
My conclusion here was not that it was an alternative to Apache, but rather I concluded that NGINX was an important part of either Apache or something that worked with Apache. And I formed the conclusion that it was important, after all we likely do want the processes its running and so if I just end the process and start Apache, I might just be causing another problem in order to solve one, like robbing Peter to pay Paul. I told Doug my conclusion that one option is to end NGINX, but I suspect that NGINX was actually important and when he asked me what it does, I said it's a high performance web server that runs many tasks at the same time. And he corrected me that basically its an alternative to Apache. And I realized, oh, so since we want Apache to run, we need to kill NGINX since only one thing can run over port 80 at a time. I asked ChatGPT how to stop it, and Chat GPT said how to stop it, and I asked how to start Apache again and it also suggested I run a status check on it after I had run the command to start it which I did:
admin@skibidi-slicers:~$ sudo systemctl stop nginx
admin@skibidi-slicers:~$ sudo systemctl start apache2
admin@skibidi-slicers:~$ sudo systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-11-05 04:01:59 UTC; 7s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 25143 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
Main PID: 25147 (apache2)
Tasks: 55 (limit: 4563)
Memory: 5.0M
CPU: 103ms
CGroup: /system.slice/apache2.service
├─25147 /usr/sbin/apache2 -k start
├─25148 /usr/sbin/apache2 -k start
└─25149 /usr/sbin/apache2 -k start
Problem solved. He told me that there were a lot of people that took far more than the ten minutes I took and may who didn't even solve it. But there were people who solved it faster than me. I asked if employers would care if I used ChatGPT and he said no, as long as you don't rely on it to tell you what everything means, you should try to understand the outputs yourself as much as you can or else you're just using it as a crutch. I said but he had given me a few nudges here and there. I suppose I can expect that on the job, that I can receive nudges from co-workers and stuff and he said yes, especially if you're a junior sys. admin. And I asked, so basically I got like a B on my test ad he said yes.
This has been Truncat3d 00000000111100010100110______________end of line