Nagios Support Forum

Whenever I run the apply config command through XI it will just sit there and spin and say that its waiting, when in reality it has errored out with a NAGIOSQL LOGIN FAILED error.

$ tail -F /usr/local/nagiosxi/var/cmdsubsys.log
..................................PROCESSING COMMAND ID 7196...
PROCESS COMMAND: CMD=17, DATA=
APPLYING NAGIOSCORE CONFIG...
CMDLINE=cd /usr/local/nagiosxi/scripts && ./reconfigure_nagios.sh
URL: http://localhost/nagiosxi/includes/components/ccm/
CMDLINE
--2017-09-26 15:01:36-- http://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://<hostname>/nagiosxi/includes/components/ccm/ [following]
--2017-09-26 15:01:36-- https://<hostname>/nagiosxi/includes/components/ccm/
Resolving <proxy info>
Connecting to <proxy info>... connected.
WARNING: cannot verify <hostname>’s certificate, issued by “<removed>”:
Self-signed certificate encountered.
Proxy request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “nagiosql.login”

0K .......... . 6.31M=0.002s

2017-09-26 15:01:36 (6.31 MB/s) - “nagiosql.login” saved [11455]

/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data 'submit=Login&hidelog=true&loginSubmitted=true&username=nagiosxi&password=n@gweb' -O nagiosql.loginNAGIOSQL LOGIN FAILED!
OUTPUT=/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data 'submit=Login&hidelog=true&loginSubmitted=true&username=nagiosxi&password=n@gweb' -O nagiosql.loginNAGIOSQL LOGIN FAILED!
RETURNCODE=2
........................
PROCESSED 1 COMMANDS
tail: /usr/local/nagiosxi/var/cmdsubsys.log: file truncated
............................................................

Any help to getting this resolved would be greatly appreciated!

run tail -f /usr/local/nagiosxi/var/cmdsubsys.log

then attempt to apply again, what is outputted?

Actually what you need is to add the no_proxy line described here to the /etc/wgetrc to stop the backend from attempting to go through a proxy
https://support.nagios.com/kb/article.php?id=147

Here is the output of /usr/local/nagiosxi/var/cmdsubsys.log

$ tail -f /usr/local/nagiosxi/var/cmdsubsys.log
...................................
PROCESSED 0 COMMANDS
tail: /usr/local/nagiosxi/var/cmdsubsys.log: file truncated
.
PROCESSED 0 COMMANDS
tail: /usr/local/nagiosxi/var/cmdsubsys.log: file truncated

I also added the hostname to the no_proxy and it did eliminate the proxy step but it is still failing.
Below is the output:

$ ./reconfigure_nagios.sh
URL: http://localhost/nagiosxi/includes/components/ccm/
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data 'submit=Login&hidelog=true&loginSubmitted=true&username=nagiosxi&password=n@gweb' -O nagiosql.login--2017-09-28 12:43:41-- http://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://<hostname>/nagiosxi/includes/components/ccm/ [following]
--2017-09-28 12:43:41-- https://<hostname>/nagiosxi/includes/components/ccm/
Resolving <hostname>...
Connecting to <hostname>:443... connected.
WARNING: cannot verify <hostname> certificate, issued by <removed>:
Self-signed certificate encountered.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “nagiosql.login”

[ <=> ] 11,455 --.-K/s in 0.009s

2017-09-28 12:43:42 (1.25 MB/s) - “nagiosql.login” saved [11455]

NAGIOSQL LOGIN FAILED!

This looks like you have a redirect in your httpd configuration files or something, all of these calls should be happening through localhost.

Can you zip up the files in /etc/httpd/conf.d and PM them to us to take a look at? Or you can send them in an email ticket to [email protected] and reference this thread.

Just wanted to update this thread, the problem was an incorrect redirect in the httpd.conf and is now resolved.