New Install - unable to install

[bosecorp]

I am doing a fresh installation, and I am getting this error

tried the steps on the following link ==>

https://support.nagios.com/kb/article/e ... tions.html

but that doesnt seem to work


[root@usvanagiospxi2 nagiosxi]# ./fullinstall
Your system $PATH does not include /sbin and /usr/sbin. This is usually the result of installing GNOME rather than creating a clean system.
Adding /sbin and /usr/sbin to $PATH.
========================
Nagios XI Full Installer
========================

This script will do a complete install of Nagios XI by executing all necessary sub-scripts.

IMPORTANT: This script should only be used on a 'clean' install of CentOS or RedHat. Do NOT use this on a system that has been tasked with other purposes or has an existing
install of Nagios Core. To create such a clean install you should have selected ONLY the 'Base' package in the OS installer.
Do you want to continue? [Y/n] Y
Proceeding with installation...
Checking MySQL credentials...
MySQL not yet installed - that's okay.
Running './0-repos'...
Configuring Repos...
Passed New Subscription Check
package centos-release is not installed
Unable to locate SystemId file. Is this system registered?
ERROR: Please add the 'Optional' channel to your Red Hat systems subscriptions.
You can do so in the Redhat Network web interface or using the rhn-channel command.
or, install the yum-utils package and use the following command:
yum-config-manager --enable rhel-7-server-optional-rpms
RESULT=1

===================
INSTALLATION ERROR!
===================
Installation step failed - exiting.
Check for error messages in the install log (install.log).

If you require assistance in resolving the issue, please include install.log
in your communications with Nagios XI technical support.

The script that failed was: './0-repos'

[cdienger]

The script is failing at:

Code: Select all

yum repolist all | grep optional-rpms | grep -qF enabled

What is the output of:

Code: Select all

yum repolist all

?

[bosecorp]

I got that working. I was able to install Nagios. I did a restore, but the problem I am seeing now is that the monitoring engine doesn't seem to be running

everything seems green.

I am using Mod_gearman, and mod_gearmand is running including the worker.

I dont see jobs running.

I tried disableling mod_gearman module from the nagios.cfg but I see the same result. So mod_gearman doesnt seem to be creating the problem

[scottwilkerson]

What data are you seeing in the nagios.log when you restart the nagios service?

[bosecorp]

No Errors

what I notice is that when I stop and start nagios. I see stuff flowing. I see JOBs running, but then all stops. but again, everything seems to be running, and I dont see anything on the logs. i.e. nagios.log, mysql, ewtc



[1504809807] Caught SIGTERM, shutting down...
[1504809819] Caught SIGTERM, shutting down...
[1504810126] Nagios 4.2.4 starting... (PID=27300)
[1504810126] Local time is Thu Sep 07 14:48:46 EDT 2017
[1504810126] LOG VERSION: 2.0
[1504810126] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1504810126] qh: core query handler registered
[1504810126] nerd: Channel hostchecks registered successfully
[1504810126] nerd: Channel servicechecks registered successfully
[1504810126] nerd: Channel opathchecks registered successfully
[1504810126] nerd: Fully initialized and ready to rock!
[1504810126] wproc: Successfully registered manager as @wproc with query handler
[1504810126] wproc: Registry request: name=Core Worker 27302;pid=27302
[1504810126] wproc: Registry request: name=Core Worker 27303;pid=27303
[1504810126] wproc: Registry request: name=Core Worker 27304;pid=27304
[1504810126] wproc: Registry request: name=Core Worker 27305;pid=27305
[1504810126] mod_gearman: initialized version 2.1.1 (libgearman 0.33)
[1504810126] Event broker module '/usr/lib64/mod_gearman2/mod_gearman2.o' initialized successfully.
[1504810126] mod_gearman: initialized version 2.1.1 (libgearman 0.33)
[1504810126] Event broker module '/usr/lib64/mod_gearman2/mod_gearman2.o' initialized successfully.
[1504810126] ndomod: NDOMOD 2.1.2 (11-14-2016) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
[1504810126] ndomod: Successfully connected to data sink. 0 queued items to flush.
[1504810126] ndomod registered for process data
[1504810126] ndomod registered for log data'
[1504810126] ndomod registered for system command data'
[1504810126] ndomod registered for event handler data'
[1504810126] ndomod registered for notification data'
[1504810126] ndomod registered for comment data'
[1504810126] ndomod registered for downtime data'
[1504810126] ndomod registered for flapping data'
[1504810126] ndomod registered for program status data'
[1504810126] ndomod registered for host status data'
[1504810126] ndomod registered for service status data'
[1504810126] ndomod registered for adaptive program data'
[1504810126] ndomod registered for adaptive host data'
[1504810126] ndomod registered for adaptive service data'
[1504810126] ndomod registered for external command data'
[1504810126] ndomod registered for aggregated status data'
[1504810126] ndomod registered for retention data'
[1504810126] ndomod registered for contact data'
[1504810126] ndomod registered for contact notification data'
[1504810126] ndomod registered for acknowledgement data'
[1504810126] ndomod registered for state change data'
[1504810126] ndomod registered for contact status data'
[1504810126] ndomod registered for adaptive contact data'
[1504810126] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.

[scottwilkerson]

[1504810126] mod_gearman: initialized version 2.1.1 (libgearman 0.33)
[1504810126] Event broker module '/usr/lib64/mod_gearman2/mod_gearman2.o' initialized successfully.
[1504810126] mod_gearman: initialized version 2.1.1 (libgearman 0.33)
[1504810126] Event broker module '/usr/lib64/mod_gearman2/mod_gearman2.o' initialized successfully.

This is odd that this is happening twice. can you share your nagios.cfg ?

[bosecorp]

good catch

I had these lines twice. at the top and bottom

broker_module=/usr/lib64/mod_gearman2/mod_gearman2.o config=/etc/mod_gearman2/module.conf eventhandler=no

removed the line, but unfortunately I still see the issue

restarting Nagios seems to help for few minutes. I see jobs running in garman_top2, then after few minutes everything stops.

[scottwilkerson]

Is it possible to comment out the other mod_gearman line and run the checks locally to verify it's not a problem with your version of mod_gearman?

[bosecorp]

I tried that already. that was one of the first things a I did

[scottwilkerson]

I tried that already. that was one of the first things a I did

I meant so neither are running, just Nagios Core with no mod_gearman

Also can you post the output of the following

Code: Select all

ps -ef|grep bin/nagios