Issue with DNS Resolution after update to 5.7.2

[rferebee]

Good morning team,

I updated my Nagios XI test server to version 5.7.2 this morning and I'm having issues with DNS Resolution service checks since completing the update. The error I'm seeing is:

Code: Select all

DNS CRITICAL - query type of -querytype=A was not found for XXX.XXX.XXX.XXX

The checks are using the built-in DNS query that's part of the wizard. I tried switching them over to the 'check_xi_service_dnsquery' check, but I'm seeing the same error.

I'm not seeing anything in the forums, so I thought I'd reach out. Thank you.

[rferebee]

I'm also getting an 'Uknown' error for the Nagios XI Daemons and Nagios XI Jobs service checks after the update.

One says 'No daemon information found' and the other says 'No job information found'.

[rferebee]

Did any of the default ports change that XI uses in this new version? I'm seeing over 1000 service checks that are critical because connection to port 12489 is refused.

[jbrunkow]

What version of the plugin are you running? You may want to update the plugin as well as XI.

Code: Select all

/usr/local/nagios/libexec/check_dns -V

What happens if you try to run the check from the command line? That may yield additional information that we can use to determine what is going on.

Code: Select all

/usr/local/nagios/libexec/check_dns -H XXX.XXX.XXX.XXX

It never hurts to send ( PM ) us a profile either! We can find lots of information about your system in there. You can download the profile by navigating to System Profile under System Config on the left pane > and clicking the Download Profile button on that page.

[benjaminsmith]

Hi @referbee,

In addition to Justin's reply. I have a few more things to add.

Regarding the error for Nagios XI Daemons and Nagios XI Jobs, I would recommend re-running the Nagios XI wizard and let me know if the issue is corrected.

There was a minor change in the check_dns syntax in the updated version of the Nagios Plugins. If you can post the full check command I can confirm this. Additionally, the following thread has some information about the change.

Reverse DNS stopped working after upgrade to 5.7

The default ports were not cheanged, is your firewall blocking 12489?

Code: Select all

 sudo nmap -sT -O localhost

Benjamin

[rferebee]

Well, it sort of seems like something with ports changed.

Here's the necessary port list we've had for XI for the past 4-5 years:

139, 1248, 5666, ICMP (TCP)

I'll get you a profile so you can take a look.

[rferebee]

I re-ran the Nagios XI wizard per your suggestion and the checks won't even work. They're just stuck on pending (even after trying to force them to run). The dates are weird to. It's listing 1970 as the last check-in date.

[jbrunkow]

I second that you should scan the host, just to verify that the ports are accessible from the Nagios XI instance.

Code: Select all

sudo nmap -sT -O localhost

I should also mention that someone else who got the same error, found that it was related to a version of openssl. Can you check that your openssl version is up to date?

Code: Select all

openssl version

Please add a comment to this post after you have sent me the profile to raise it in the queue.

I re-ran the Nagios XI wizard per your suggestion and the checks won't even work. They're just stuck on pending (even after trying to force them to run). The dates are weird to. It's listing 1970 as the last check-in date.

We have a release coming out later today or tomorrow, please try to upgrade to correct this error. As always, we recommend upgrading on a test instance first before making any changes to your production system and taking a backup/snapshot beforehand.

Upgrading Nagios XI

[rferebee]

This is what I got with the nmap scan:

Code: Select all

Starting Nmap 6.47 ( http://nmap.org ) at 2020-09-03 15:16 PDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000095s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 992 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
25/tcp   open  smtp
80/tcp   open  http
111/tcp  open  rpcbind
443/tcp  open  https
631/tcp  open  ipp
3306/tcp open  mysql
5432/tcp open  postgresql
Device type: general purpose
Running: Linux 3.X
OS CPE: cpe:/o:linux:linux_kernel:3
OS details: Linux 3.7 - 3.15
Network Distance: 0 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 1.98 seconds

[jbrunkow]

I don't see port 12489 on the list of open ports. Can you open that one on your firewall?