Nagios Support Forum

bosecorp wrote:close this post.

Correct me if I am wrong, but I was under the impression that this thread was opened by "emartine", not yourself.

@emartine:
Do you still need assistance?

so, I am not sure why it shows up as mine, meaning under my account or within my own posts

odd. Well I will leave the thread open for now until the OP gets back to us.

Here is the output. of the ./reconfigure_nagios.sh script.

./reconfigure_nagios.sh
URL: https://localhost/nagiosxi/includes/components/ccm/
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies https://loc alhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data 'sub mit=Login&hidelog=true&loginSubmitted=true&username=nagiosxi&password=8fm3rb' -O nagiosql.login--2015-03-20 14:00:08-- https://localhost/nagiosxi/includes/comp onents/ccm/
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:443... connected.
WARNING: cannot verify localhost’s certificate, issued by “/C=US/O=Internet2/OU= InCommon/CN=InCommon Server CA”:
Unable to locally verify the issuer’s authority.
WARNING: no certificate subject alternative name matches
requested host name “localhost”.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “nagiosql.login”

[ <=> ] 10,530 --.-K/s in 0.01s

2015-03-20 14:00:08 (847 KB/s) - “nagiosql.login” saved [10530]

LOGIN SUCCESSFUL!
IMPORTING CONFIG FILES...URL: https://localhost/nagiosxi/includes/components/ccm /
Array
(
)
SETUID ROOT OK
RESETTING PERMS
URL: https://localhost/nagiosxi/includes/components/ccm/
CMDLINE

<username and password have been omitted>

Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:443... connected.
WARNING: cannot verify localhost’s certificate, issued by “/C=US/O=Internet2/OU= InCommon/CN=InCommon Server CA”:
Unable to locally verify the issuer’s authority.
WARNING: no certificate subject alternative name matches
requested host name “localhost”.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “nagiosql.login”

[ <=> ] 10,530 --.-K/s in 0.01s

2015-03-20 14:00:09 (768 KB/s) - “nagiosql.login” saved [10530]

LOGIN SUCCESSFUL!
URL: https://localhost/nagiosxi/includes/components/ccm/
CMDLINE:
/usr/bin/wget --load-cookies=nagiosql.cookies https://localhost/nagiosxi/include s/components/ccm/ --no-check-certificate --post-data 'cmd=apply&type=writeConfig ' -O nagiosql.export.monitoring
--2015-03-20 14:00:09-- https://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:443... connected.
WARNING: cannot verify localhost’s certificate, issued by “/C=US/O=Internet2/OU= InCommon/CN=InCommon Server CA”:
Unable to locally verify the issuer’s authority.
WARNING: no certificate subject alternative name matches
requested host name “localhost”.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “nagiosql.export.monitoring”

[ <=> ] 13,386 17.8K/s in 0.7s

2015-03-20 14:00:10 (17.8 KB/s) - “nagiosql.export.monitoring” saved [13386]

WRITE CONFIGS SUCCESSFUL!
OUTPUT:
Nagios Core 4.0.8
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-12-2014
License: GPL

Website: http://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 68 services.
Checked 14 hosts.
Checked 5 host groups.
Checked 0 service groups.
Checked 16 contacts.
Checked 8 contact groups.
Checked 133 commands.
Checked 20 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 14 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 20 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
RET: 0
Running configuration check...done.
Stopping nagios: .done.
Starting nagios: done.

That output looks good.

The only way to make this fail is to reboot the server.
Can you do this when you have time to do it?
Reboot the server.
Wait a few minutes and see if all of the processes start.
If the nagios service doesn't start, can you run this and post back here? Then go ahead and start the nagios service.

I already had scheduled maintenance scheduled this week and I have maintenance already scheduled for next Thursday. I will see if I can do this three weeks out.

Let us know how it works out.