2 possible bugs in 2014

[snapon_admin]

I'm sure one of these is a bug, the other I might just be doing something wrong, but it also feels like a bug. So for the first one, I have set the option in performance settings to not auto run reports on page load (thank you for this!), but the problem is that if there is more than one page of reports, you cannot click on the arrow to go to the next page. As an example, we went to the State History report, filtered for the past 24 hours, and filtered for Critical alerts only. This report is 3 pages long. When I click next page at the bottom, it appears to launch the next page but doesn't fill (I assume per the do not auto load setting) and the page is blank. When I click update, it just updates the report and spits me back to page 1. As a work around, we are able to type a page number in the blank at the bottom of the page (page _2_ of 3) and have it go to that page.

Second issue, this one is with NNA integration. Our NNA server is setup to use SSL, and to force SSL. When not using SSL, and I put in all the settings in the NNA component (API key, IP address, etc.) and leave the Use SSL box unticked all works wonderfully. If I set the NNA server to use SSL, and check the SSL box in the component settings screen I get this:

Code: Select all

Failed connect to API. Check your connection to the host (using SSL?) and make sure your Nagios Network Analyzer is version 2014R1.5 or higher.

Whenever I try to use NNA in XI, whether it be the wizard or running reports. Interestingly enough, if I click Run Report even with that error, the report does run. only one of the 4 pie charts actually loads, but all of the tables fill and the report runs so I know it can at least sort of connect. So yeah, not sure if I'm doing something wrong or if this is also a bug, but it feels like a bug since I'm pretty sure everything is setup correctly. What do?

[lmiltchev]

I was able to recreate the first issue and filed an internal bug report (TASK ID 2853). I will be testing the second issue as soon as I can.

[snapon_admin]

Thanks much. I also submitted a bug report for the first issue in tracker, 539, if you want to reference that. I thought to add that after posting here. I haven't submitted a bug report on the second issue because I want to verify it's a bug and not (derp) "user error" first.

[lmiltchev]

On the second issue - can you describe what steps you took to force ssl on the NNA server?

[snapon_admin]

Edited the /etc/httpd/conf.d/nagiosna.conf file from

Code: Select all

<Directory "/var/www/html/nagiosna/www/">
 #SSLRequireSSL
   Options None
   AllowOverride None
   Order allow,deny
   Allow from all

</Directory>

to

Code: Select all

[code]
<Directory "/var/www/html/nagiosna/www/">
  SSLRequireSSL
   Options None
   AllowOverride None
   Order allow,deny
   Allow from all

</Directory>

[/code]

But I get the same issue even if force SSL is off. If http is allowed, and I check the use SSL box, it still gives me the same error, it's not only when SSL is forced.

[lmiltchev]

Actually, this worked fine for me (displaying graphs). There were some (other) issues with displaying the correct sources for the when you switch to the "second" NNA Server from the "NNA Server" drop-down menu (if you use more than one NNA server).

So, basically you configured SSL in NNA by following this document and uncommented the "#SSLRequireSSL" line in the "/etc/httpd/conf.d/nagiosna.conf" file, correct? Have you changed anything else?

[snapon_admin]

Yep, followed that documentation. This doesn't work whether #SSLRequireSSL is commented out or not.

[snapon_admin]

Figured out the second issue. In the component settings I had the IP address in the IP address/Hostname field. Switching that to the hostname instead corrected the issue for me. There's already a bug report on the reports issue so I think this one is safe to close up, thanks!