Apache error to start [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
-5
down vote
favorite
I'm trying to start apache2 and it gives me this error:
root@kali:~# service apache2 start
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details
The status shows:
# systemctl status apache2.service
The journal log shows:
# journalctl -xe .....
networking systemd apache-httpd kali-linux
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 21:45
bader alzhrani
1114
closed as unclear what you're asking by Jeff Schaller, SatÃ…Â Katsura, Kusalananda, peterh, sebasth Oct 11 '17 at 16:35
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
-5
down vote
favorite
I'm trying to start apache2 and it gives me this error:
root@kali:~# service apache2 start
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details
The status shows:
# systemctl status apache2.service
The journal log shows:
# journalctl -xe .....
networking systemd apache-httpd kali-linux
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 21:45
bader alzhrani
1114
closed as unclear what you're asking by Jeff Schaller, SatÃ…Â Katsura, Kusalananda, peterh, sebasth Oct 11 '17 at 16:35
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
What's already listening on port 80? Use netstat or lsof to find that out
– thrig
Oct 10 '17 at 21:47
2
Please, don't post images of text.
– Kusalananda
Oct 10 '17 at 21:49
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
– bader alzhrani
Oct 10 '17 at 22:07
Did you see that part about the Apache error log?
– Jeff Schaller
Oct 10 '17 at 22:40
Switch your screenshots to text copy-paste and you will get my reopen vote.
– peterh
Oct 11 '17 at 15:58
add a comment |Â
up vote
-5
down vote
favorite
up vote
-5
down vote
favorite
I'm trying to start apache2 and it gives me this error:
root@kali:~# service apache2 start
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details
The status shows:
# systemctl status apache2.service
The journal log shows:
# journalctl -xe .....
networking systemd apache-httpd kali-linux
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 21:45
bader alzhrani
1114
I'm trying to start apache2 and it gives me this error:
root@kali:~# service apache2 start
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details
The status shows:
# systemctl status apache2.service
The journal log shows:
# journalctl -xe .....
networking systemd apache-httpd kali-linux
networking systemd apache-httpd kali-linux
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 21:45
bader alzhrani
1114
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
asked Oct 10 '17 at 21:45
bader alzhrani
1114
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
edited Oct 10 '17 at 22:40
Jeff Schaller
32.3k849109
32.3k849109
asked Oct 10 '17 at 21:45
bader alzhrani
1114
asked Oct 10 '17 at 21:45
bader alzhrani
1114
asked Oct 10 '17 at 21:45
bader alzhrani
1114
1114
closed as unclear what you're asking by Jeff Schaller, SatÃ…Â Katsura, Kusalananda, peterh, sebasth Oct 11 '17 at 16:35
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Jeff Schaller, SatÃ…Â Katsura, Kusalananda, peterh, sebasth Oct 11 '17 at 16:35
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
What's already listening on port 80? Use netstat or lsof to find that out
– thrig
Oct 10 '17 at 21:47
2
Please, don't post images of text.
– Kusalananda
Oct 10 '17 at 21:49
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
– bader alzhrani
Oct 10 '17 at 22:07
Did you see that part about the Apache error log?
– Jeff Schaller
Oct 10 '17 at 22:40
Switch your screenshots to text copy-paste and you will get my reopen vote.
– peterh
Oct 11 '17 at 15:58
add a comment |Â
What's already listening on port 80? Use netstat or lsof to find that out
– thrig
Oct 10 '17 at 21:47
2
Please, don't post images of text.
– Kusalananda
Oct 10 '17 at 21:49
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
– bader alzhrani
Oct 10 '17 at 22:07
Did you see that part about the Apache error log?
– Jeff Schaller
Oct 10 '17 at 22:40
Switch your screenshots to text copy-paste and you will get my reopen vote.
– peterh
Oct 11 '17 at 15:58
What's already listening on port 80? Use netstat or lsof to find that out
– thrig
Oct 10 '17 at 21:47
What's already listening on port 80? Use netstat or lsof to find that out
– thrig
Oct 10 '17 at 21:47
2
2
Please, don't post images of text.
– Kusalananda
Oct 10 '17 at 21:49
Please, don't post images of text.
– Kusalananda
Oct 10 '17 at 21:49
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
– bader alzhrani
Oct 10 '17 at 22:07
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
– bader alzhrani
Oct 10 '17 at 22:07
Did you see that part about the Apache error log?
– Jeff Schaller
Oct 10 '17 at 22:40
Did you see that part about the Apache error log?
– Jeff Schaller
Oct 10 '17 at 22:40
Switch your screenshots to text copy-paste and you will get my reopen vote.
– peterh
Oct 11 '17 at 15:58
Switch your screenshots to text copy-paste and you will get my reopen vote.
– peterh
Oct 11 '17 at 15:58
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
You have some other process already listening on port 80. Based on your netstat command output from your comment above -
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
It looks like some python script is acting as a webserver. Re-run the command to get the current process id (the 222620 in this example) and then run cat /proc/NUMBER/commandline on it to see what script was actually called, or look for it in the output of top, ps and similar tools.
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
You have some other process already listening on port 80. Based on your netstat command output from your comment above -
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
It looks like some python script is acting as a webserver. Re-run the command to get the current process id (the 222620 in this example) and then run cat /proc/NUMBER/commandline on it to see what script was actually called, or look for it in the output of top, ps and similar tools.
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
add a comment |Â
up vote
0
down vote
accepted
You have some other process already listening on port 80. Based on your netstat command output from your comment above -
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
It looks like some python script is acting as a webserver. Re-run the command to get the current process id (the 222620 in this example) and then run cat /proc/NUMBER/commandline on it to see what script was actually called, or look for it in the output of top, ps and similar tools.
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
You have some other process already listening on port 80. Based on your netstat command output from your comment above -
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
It looks like some python script is acting as a webserver. Re-run the command to get the current process id (the 222620 in this example) and then run cat /proc/NUMBER/commandline on it to see what script was actually called, or look for it in the output of top, ps and similar tools.
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
You have some other process already listening on port 80. Based on your netstat command output from your comment above -
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
It looks like some python script is acting as a webserver. Re-run the command to get the current process id (the 222620 in this example) and then run cat /proc/NUMBER/commandline on it to see what script was actually called, or look for it in the output of top, ps and similar tools.
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
answered Oct 11 '17 at 2:37
ivanivan
3,1721313
3,1721313
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
add a comment |Â
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
i kill the proccess the work on port 80 and apache2 going to start +1 thankx
– bader alzhrani
Oct 11 '17 at 10:19
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
So who is down voting and why?
– ivanivan
Oct 11 '17 at 18:16
add a comment |Â
What's already listening on port 80? Use netstat or lsof to find that out
– thrig
Oct 10 '17 at 21:47
2
Please, don't post images of text.
– Kusalananda
Oct 10 '17 at 21:49
root@kali:~# netstat -plnt | grep ':80' tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22620/python3
– bader alzhrani
Oct 10 '17 at 22:07
Did you see that part about the Apache error log?
– Jeff Schaller
Oct 10 '17 at 22:40
Switch your screenshots to text copy-paste and you will get my reopen vote.
– peterh
Oct 11 '17 at 15:58