Apache in an AWS Instance not starting
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I had an instance with AWS, decided to upgrade the plan of that instance and now my instance is not working properly with 2 sites that I had.
I detached the static IP from the old instance and put it on the new instance.
It should be working fine? Unfortunately, it’s not.
The static IP address used to give me the default Bitnami congratulation page. But now it gives me Apache2 Ubuntu Default Page.
I use this command to attempt to restart apache2:
~$ sudo apachectl restart
It gave me this error message:
httpd not running, trying to start
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address [::]:80
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Edit: Also the domain name I had pointed to this static IP address is not resolving. (The static IP is pointed to the new instances already.)
networking server apache2 amazon-ec2 aws
edited Feb 28 at 7:47
Melebius
5,11852041
asked Feb 25 at 8:57
peter-cspeter-cs
63
add a comment |
I had an instance with AWS, decided to upgrade the plan of that instance and now my instance is not working properly with 2 sites that I had.
I detached the static IP from the old instance and put it on the new instance.
It should be working fine? Unfortunately, it’s not.
The static IP address used to give me the default Bitnami congratulation page. But now it gives me Apache2 Ubuntu Default Page.
I use this command to attempt to restart apache2:
~$ sudo apachectl restart
It gave me this error message:
httpd not running, trying to start
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address [::]:80
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Edit: Also the domain name I had pointed to this static IP address is not resolving. (The static IP is pointed to the new instances already.)
networking server apache2 amazon-ec2 aws
edited Feb 28 at 7:47
Melebius
5,11852041
asked Feb 25 at 8:57
peter-cspeter-cs
63
add a comment |
I had an instance with AWS, decided to upgrade the plan of that instance and now my instance is not working properly with 2 sites that I had.
I detached the static IP from the old instance and put it on the new instance.
It should be working fine? Unfortunately, it’s not.
The static IP address used to give me the default Bitnami congratulation page. But now it gives me Apache2 Ubuntu Default Page.
I use this command to attempt to restart apache2:
~$ sudo apachectl restart
It gave me this error message:
httpd not running, trying to start
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address [::]:80
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Edit: Also the domain name I had pointed to this static IP address is not resolving. (The static IP is pointed to the new instances already.)
networking server apache2 amazon-ec2 aws
edited Feb 28 at 7:47
Melebius
5,11852041
asked Feb 25 at 8:57
peter-cspeter-cs
63
I had an instance with AWS, decided to upgrade the plan of that instance and now my instance is not working properly with 2 sites that I had.
I detached the static IP from the old instance and put it on the new instance.
It should be working fine? Unfortunately, it’s not.
The static IP address used to give me the default Bitnami congratulation page. But now it gives me Apache2 Ubuntu Default Page.
I use this command to attempt to restart apache2:
~$ sudo apachectl restart
It gave me this error message:
httpd not running, trying to start
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address [::]:80
(98)Address already in use: AH00073: make_sock: unable to listen for connections on address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Edit: Also the domain name I had pointed to this static IP address is not resolving. (The static IP is pointed to the new instances already.)
networking server apache2 amazon-ec2 aws
networking server apache2 amazon-ec2 aws
edited Feb 28 at 7:47
Melebius
5,11852041
asked Feb 25 at 8:57
peter-cspeter-cs
63
edited Feb 28 at 7:47
Melebius
5,11852041
asked Feb 25 at 8:57
peter-cspeter-cs
63
edited Feb 28 at 7:47
Melebius
5,11852041
edited Feb 28 at 7:47
Melebius
5,11852041
edited Feb 28 at 7:47
Melebius
5,11852041
5,11852041
asked Feb 25 at 8:57
peter-cspeter-cs
63
asked Feb 25 at 8:57
peter-cspeter-cs
63
asked Feb 25 at 8:57
peter-cspeter-cs
63
63
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
service nginx stop
and try now. I am guessing that you have installed the nginx which is using the port 80 and that is why the apache cannot work.
As for the domain you have to point this to the new IP..
answered Feb 25 at 10:44
AlpyAlpy
37516
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
add a comment |
You can check which process is listening at the port 80 using the command netstat:
sudo netstat -tlpn | grep :80
In my case, it’s apache2.
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11164/apache2
If you find a different process is using it (such as nginx as suggested by another answer), stop the process using the command kill <PID> or service <name> stop.
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
I did what you suggested this what I got.tcp6 0 0 :::80 :::* LISTEN 1491/apache2
– peter-cs
Feb 25 at 12:48
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
edited my question, I used~S sudo apachectl restart
– peter-cs
Feb 25 at 23:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1121044%2fapache-in-an-aws-instance-not-starting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
service nginx stop
and try now. I am guessing that you have installed the nginx which is using the port 80 and that is why the apache cannot work.
As for the domain you have to point this to the new IP..
answered Feb 25 at 10:44
AlpyAlpy
37516
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
add a comment |
service nginx stop
and try now. I am guessing that you have installed the nginx which is using the port 80 and that is why the apache cannot work.
As for the domain you have to point this to the new IP..
answered Feb 25 at 10:44
AlpyAlpy
37516
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
add a comment |
service nginx stop
and try now. I am guessing that you have installed the nginx which is using the port 80 and that is why the apache cannot work.
As for the domain you have to point this to the new IP..
answered Feb 25 at 10:44
AlpyAlpy
37516
service nginx stop
and try now. I am guessing that you have installed the nginx which is using the port 80 and that is why the apache cannot work.
As for the domain you have to point this to the new IP..
answered Feb 25 at 10:44
AlpyAlpy
37516
answered Feb 25 at 10:44
AlpyAlpy
37516
answered Feb 25 at 10:44
AlpyAlpy
37516
answered Feb 25 at 10:44
AlpyAlpy
37516
37516
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
add a comment |
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
not sure, the domain is pointed at the static ip. its the same ip for the new instance. I'm not sure about nginx, i just created an instance of the snapshot from my other instance that I attempted to upgrade.
– peter-cs
Feb 25 at 12:45
add a comment |
You can check which process is listening at the port 80 using the command netstat:
sudo netstat -tlpn | grep :80
In my case, it’s apache2.
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11164/apache2
If you find a different process is using it (such as nginx as suggested by another answer), stop the process using the command kill <PID> or service <name> stop.
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
I did what you suggested this what I got.tcp6 0 0 :::80 :::* LISTEN 1491/apache2
– peter-cs
Feb 25 at 12:48
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
edited my question, I used~S sudo apachectl restart
– peter-cs
Feb 25 at 23:21
add a comment |
You can check which process is listening at the port 80 using the command netstat:
sudo netstat -tlpn | grep :80
In my case, it’s apache2.
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11164/apache2
If you find a different process is using it (such as nginx as suggested by another answer), stop the process using the command kill <PID> or service <name> stop.
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
I did what you suggested this what I got.tcp6 0 0 :::80 :::* LISTEN 1491/apache2
– peter-cs
Feb 25 at 12:48
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
edited my question, I used~S sudo apachectl restart
– peter-cs
Feb 25 at 23:21
add a comment |
You can check which process is listening at the port 80 using the command netstat:
sudo netstat -tlpn | grep :80
In my case, it’s apache2.
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11164/apache2
If you find a different process is using it (such as nginx as suggested by another answer), stop the process using the command kill <PID> or service <name> stop.
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
You can check which process is listening at the port 80 using the command netstat:
sudo netstat -tlpn | grep :80
In my case, it’s apache2.
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11164/apache2
If you find a different process is using it (such as nginx as suggested by another answer), stop the process using the command kill <PID> or service <name> stop.
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
answered Feb 25 at 12:21
MelebiusMelebius
5,11852041
5,11852041
I did what you suggested this what I got.tcp6 0 0 :::80 :::* LISTEN 1491/apache2
– peter-cs
Feb 25 at 12:48
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
edited my question, I used~S sudo apachectl restart
– peter-cs
Feb 25 at 23:21
add a comment |
I did what you suggested this what I got.tcp6 0 0 :::80 :::* LISTEN 1491/apache2
– peter-cs
Feb 25 at 12:48
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
edited my question, I used~S sudo apachectl restart
– peter-cs
Feb 25 at 23:21
I did what you suggested this what I got.
tcp6 0 0 :::80 :::* LISTEN 1491/apache2– peter-cs
Feb 25 at 12:48
I did what you suggested this what I got.
tcp6 0 0 :::80 :::* LISTEN 1491/apache2– peter-cs
Feb 25 at 12:48
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
It means Apache is running and waiting for IPv6 connections. Could you edit your question with details on how you tried to restart Apache (exact command)?
– Melebius
Feb 25 at 13:00
edited my question, I used
~S sudo apachectl restart– peter-cs
Feb 25 at 23:21
edited my question, I used
~S sudo apachectl restart– peter-cs
Feb 25 at 23:21
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1121044%2fapache-in-an-aws-instance-not-starting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
