AWS - Nagios Log Server
AWS - Nagios Log Server
Hello,
I set up a Nagios Log Server by following the Nagios documentation instructions. I have the EC2 Instance running in AWS correctly. I'm able to ping the public IP. The instructions say to finish the installation by going to the link <AWSIP>/nagioslogserver. There is no response when I try to access the server. Is it possible to open a ticket for this?
I set up a Nagios Log Server by following the Nagios documentation instructions. I have the EC2 Instance running in AWS correctly. I'm able to ping the public IP. The instructions say to finish the installation by going to the link <AWSIP>/nagioslogserver. There is no response when I try to access the server. Is it possible to open a ticket for this?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: AWS - Nagios Log Server
Did you add port 80 to the AWS security group?
Can you verify that httpd is running
also, it is important you wait about 20 minutes from launching the instance for the installation to complete
Can you verify that httpd is running
Code: Select all
systemctl status httpdRe: AWS - Nagios Log Server
Yes I did. I'm able to ping it and I'm able to SSH into the server. It's weird that I can't get to the web interface to finish the installation. Thank you for your response!
Re: AWS - Nagios Log Server
It's been up for days. I ran the command and I get - Unit httpd.service could not be found
Re: AWS - Nagios Log Server
I tried to start the service but it asks for a password. Is there a default password on this?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: AWS - Nagios Log Server
This is the doc you followed?
https://assets.nagios.com/downloads/nag ... -Cloud.pdf
If so, something must have now worked properly if you do not have a httpd.service, it would lead me to believe all the dependencies didn't get installed correctly
I would suggest shutting down this instance and starting a new one
https://assets.nagios.com/downloads/nag ... -Cloud.pdf
If so, something must have now worked properly if you do not have a httpd.service, it would lead me to believe all the dependencies didn't get installed correctly
I would suggest shutting down this instance and starting a new one
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: AWS - Nagios Log Server
You should be able to run the following without a passwordmneubauer wrote:I tried to start the service but it asks for a password. Is there a default password on this?
Code: Select all
sudo systemctl start httpdRe: AWS - Nagios Log Server
scottwilkerson wrote:You should be able to run the following without a passwordmneubauer wrote:I tried to start the service but it asks for a password. Is there a default password on this?Code: Select all
sudo systemctl start httpd
Ok I ran that and I get - Failed to start httpd.service: Unit not found.
I will try creating a new instance and see what happens.
Thanks for your help! I will let you know what happens.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: AWS - Nagios Log Server
Sounds goodmneubauer wrote:scottwilkerson wrote:You should be able to run the following without a passwordmneubauer wrote:I tried to start the service but it asks for a password. Is there a default password on this?Code: Select all
sudo systemctl start httpd
Ok I ran that and I get - Failed to start httpd.service: Unit not found.
I will try creating a new instance and see what happens.
Thanks for your help! I will let you know what happens.
Re: AWS - Nagios Log Server
Hello,
I deleted the old instance and created a new one following those instructions you posted. I'm still getting the same error on the service. Is that AMI build in AWS known to be updated and good?
I deleted the old instance and created a new one following those instructions you posted. I'm still getting the same error on the service. Is that AMI build in AWS known to be updated and good?