Verifying New Installation
Verifying New Installation
I have successfully installed NAGIOS XI. I am not able to connect using the URL http://<server_address>/nagiosxi to finalize the installation. Page not found is the error. I have searched and unable to find a document describing the starting of the application server.
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Verifying New Installation
Hello @jjk94,
Since this is your first post and I'd like to thank you for choosing Nagios! We're happy to have you in the community. It ought to come up, let's check a few things.
1. What is the operating system you installed on and was this a clean install (anything else running on the server)?
2. Are you able to successfully ping the server from your workstation?
3. Is Apache and the Nagios process running?
4. Are you able to access the Nagios Core interface?
Since this is your first post and I'd like to thank you for choosing Nagios! We're happy to have you in the community. It ought to come up, let's check a few things.
1. What is the operating system you installed on and was this a clean install (anything else running on the server)?
2. Are you able to successfully ping the server from your workstation?
Code: Select all
ping <ip address>
Code: Select all
systemctl status httpd
systemctl status nagios
Code: Select all
http://<ip-address>/nagios
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Verifying New Installation
systemctl status httpd - Not Running
I did start and can access the redhat apache default page
systemctl status Nagios
● nagios.service - Nagios Core 4.4.5
Loaded: loaded (/usr/lib/systemd/system/nagios.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-02-20 14:15:28 EST; 1h 3min ago
Docs: https://www.nagios.org/documentation
Process: 6532 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=1/FAILURE)
Feb 20 14:15:28 HOSTNAME nagios[6532]: Check your configuration file(s) to ensure that they contain valid
Feb 20 14:15:28 HOSTNAME nagios[6532]: directives and data definitions. If you are upgrading from a previous
Feb 20 14:15:28 HOSTNAME nagios[6532]: version of Nagios, you should be aware that some variables/definitions
Feb 20 14:15:28 HOSTNAME nagios[6532]: may have been removed or modified in this version. Make sure to read
Feb 20 14:15:28 HOSTNAME nagios[6532]: the HTML documentation regarding the config files, as well as the
Feb 20 14:15:28 HOSTNAME nagios[6532]: 'Whats New' section to find out what has changed.
Feb 20 14:15:28 HOSTNAME systemd[1]: nagios.service: control process exited, code=exited status=1
Feb 20 14:15:28 HOSTNAME systemd[1]: Failed to start Nagios Core 4.4.5.
Feb 20 14:15:28 HOSTNAME systemd[1]: Unit nagios.service entered failed state.
Feb 20 14:15:28 HOSTNAME systemd[1]: nagios.service failed.
I did start and can access the redhat apache default page
systemctl status Nagios
● nagios.service - Nagios Core 4.4.5
Loaded: loaded (/usr/lib/systemd/system/nagios.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-02-20 14:15:28 EST; 1h 3min ago
Docs: https://www.nagios.org/documentation
Process: 6532 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=1/FAILURE)
Feb 20 14:15:28 HOSTNAME nagios[6532]: Check your configuration file(s) to ensure that they contain valid
Feb 20 14:15:28 HOSTNAME nagios[6532]: directives and data definitions. If you are upgrading from a previous
Feb 20 14:15:28 HOSTNAME nagios[6532]: version of Nagios, you should be aware that some variables/definitions
Feb 20 14:15:28 HOSTNAME nagios[6532]: may have been removed or modified in this version. Make sure to read
Feb 20 14:15:28 HOSTNAME nagios[6532]: the HTML documentation regarding the config files, as well as the
Feb 20 14:15:28 HOSTNAME nagios[6532]: 'Whats New' section to find out what has changed.
Feb 20 14:15:28 HOSTNAME systemd[1]: nagios.service: control process exited, code=exited status=1
Feb 20 14:15:28 HOSTNAME systemd[1]: Failed to start Nagios Core 4.4.5.
Feb 20 14:15:28 HOSTNAME systemd[1]: Unit nagios.service entered failed state.
Feb 20 14:15:28 HOSTNAME systemd[1]: nagios.service failed.
Re: Verifying New Installation
uninstalled. reinstalled using /tmp/rpms as the install directory. Default server config does not allow execution from /tmp. Once access was set . installed without errors.
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Verifying New Installation
Hi Jack,
Thanks for the update!
If you have any other questions, feel free to open another post.
Thanks for the update!
If you have any other questions, feel free to open another post.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!