Nagios Support Forum

This happens on all hosts and services. For instance, we have host SPLP65 and service Printer Status (attached). When I try to use the "commit" button to acknowledge the problem, it just brings me to that blank screen. If I go to the email alert and click on the link, I can acknowledge it. Not all service problems and hosts are configured to send alerts though.

So far we haven't had any problems with immediate checks. They succeed every time.

When you try to acknowledge a problem from the GUI, are you logged in as nagiosadmin or another user? What are the user's security settings (Admin->Manage Users->Edit)?

I'm logged in as myself, but we have tried from every user account setup including the nagios admin. All of them show the same results.

Chris, if you are a customer, please send an email referencing this thread to [email protected]. We may want to set up a remote session to look at this issue in particular in your environment. If you are evaluating XI, let me know and we will look into other options for you.

We are a customer, but we didn't renew email support for XI. We did purchase the following though :

XIMAINT-UNLIMITED
XI-ENT-RENEW-1Y
NA-UNL-MSP-1Y

We do have email support for our Nagios Network Analyzer though. When I tried to email it was automatically rejected.

Thanks,
Chris

We setup a remote through a pm and patched core 4.0.6 with the potential fix, it was not successful. An internal bug report has been filed and he was asked to open a bug report on tracker.nagios.org as well.

OP, once you have created the bug report on tracker, post a link to it here for future reference.

Thanks again for your help. Here is a link to the issue on tracker.nagios.org.

http://tracker.nagios.org/view.php?id=621

Had a thread on the customer support forum with the same issue, which was determined has been fixed in the latest version of Core and will be in the 2014R1.2 release of XI (coming out shortly), if you need an immediate fix, it is as follows:

scottwilkerson wrote:Ok, here is a short list of steps to upgrade to Core 4.0.7 on XI 20141.1 before the next XI release, this assumes you have the old installation directory in /tmp/nagiosxi

Code: Select all

cd /tmp/nagiosxi/subcomponents/nagioscore/
wget http://sourceforge.net/projects/nagios/files/nagios-4.x/nagios-4.0.7/nagios-4.0.7.tar.gz/download -O nagios-4.0.7.tar.gz

Then edit line 5 of /tmp/nagiosxi/subcomponents/nagioscore/upgrade to read

Code: Select all

pkgname="nagios-4.0.7"

Then, edit /tmp/nagiosxi/subcomponents/nagioscore/apply-patches to only contain the following (removing about 5 lines)

Code: Select all

#!/bin/sh -e

pkgname="$1"

# Apply our patches
echo "Applying Nagios XI patches to Nagios Core..."


# Custom CGIs
cp patches/cgi/*.c "$pkgname/cgi"

# Makefile mods for Custom CGIs
patch "$pkgname/cgi/Makefile.in" < patches/cgi-makefile.patch

Then, from in the /tmp/nagiosxi/subcomponents/nagioscore/ directory

Code: Select all

./upgrade

Has this been resolved? I am seeing the same type of issues however it seems to be related to only 1 user and he is a Nagios Administrator and uses this account to acknowledge alerts as well as configure.

@chadleggett: What Core and XI versions are you using?