schedule downtime issue

[slater86]

Hi All,

I can replicate this issue ever since upgrading to Nagios XI 5.2.3 (upgraded over 5.2.2).

I can no longer apply downtime to a specific host or service though the NagiosXI front-end using the following methods:
* By going to the downtime area and selecting a host/service (as shown in sitaonair's screenshot earlier)
* By going directly to the host/service and selecting downtime.

Buttons all appear and fields can be filled out but pushing "submit" just closes the window.
Notably, these dialogs were added in a recent build. They used to be forms from Nagios Core poking through.

I can also confirm that adding downtime through the Nagios Core front-end works as expected.

Mass acknowledge downtime and reoccurring downtime through NagiosXI front-end still work fine.

This has started happening on a fresh (not restored) 2 month old build and on the 5 year old build that the new one is replacing soon.
Happy to provide configs if required.

--Matt

Both Build Details:
Linux Distribution and version? CentOS release 6.7 (Final) x64
VMware Image or Manual Install of XI? Manual Install
No special configurations on system.

Mod Edit: I have split your topic from this one: https://support.nagios.com/forum/viewto ... 2&start=10
In the future please start your own topic and link to the referenced one so we can keep users' issues separate

[lmiltchev]

Are you having issues with one, many or all users?

Go to Admin->Manage Users->Edit, and show a screenshot of the "Security Settings" section for the "problem" user.

Is this a "local" or "AD/LDAP" user?

Do you see any errors in the apache error log?

Code: Select all

tail -200 /var/log/httpd/error_log

[slater86]

Hi lmiltchev,

Users are all local (not AD) and all have the issue.

Nagios Permissions.png

There are no related errors in the apache log and I can see the request going through in the access log with valid credentials

tail - /var/log/httpd/access_log |grep "Nagios XI Curl Request"
"POST /nagiosxi/includes/components/nagioscore/ui/cmd.php?username=validusername&ticket=abcdef12345abcdef12345abcdef12345abcdef12345abcdef12345abcdef12 HTTP/1.1" 200 1763 "-" "Nagios XI Curl Request"

Issues appear to be related to the post args in the following function:
/usr/local/nagiosxi/html/includes/components/xicore/downtime.php
function do_submit_downtime()

They clear the sanity checks but then fail while being posted to:
/usr/local/nagiosxi/html/includes/components/nagioscore/ui/cmd.php

Unfortunately I can't find an older version of downtime.php to diff against.

[rkennedy]

Are you forcing SSL at all?

Can you post your nagios configuration file for us to look at?

[ssax]

In addition to what rkennedy posted:

Every time I've seen this it's always been related to SSL (self-signed certificate) or if the Program URL/External URL have a hostname that is not resolvable (adding to /etc/hosts usually fixes it).

Do your Program URL and/or External URL have a resolvable hostname in Admin > System Settings?

Are you using a self-signed SSL certificate?

Please post your /etc/httpd/conf.d/nagiosxi.conf and your /etc/httpd/conf/httpd.conf.

Thank you

[slater86]

Hi Guys,

As requested:

* Contents of nagiosxi.conf
* Contents of httpd.conf
* Settings for the Program URL/External URL
* Forward and Reverse lookup from the server (left my server names/addresses in for completeness).

Server does not use SSL yet.
Have a certificate signed by RapidSSL/Geotrust is to be installed in about a weeks time but so far no SSL config has been touch (all defaults).
This is not a production server yet.

Existing production server does use SSL with above certificate. This is used as a apache2 reverse proxy from the internet.
Both servers broke immediately upon applying 5.2.3.

[root@daihatsu ~]# cat /etc/httpd/conf.d/nagiosxi.conf
<Directory "/usr/local/nagiosxi/html">
# SSLRequireSSL
Options None
AllowOverride None
Order allow,deny
Allow from all
# Order deny,allow
# Deny from all
# Allow from 127.0.0.1
# AuthName "Nagios XI"
# AuthType Basic
# AuthUserFile /usr/local/nagiosxi/etc/htpasswd.users
# Require valid-user
Require all granted
</Directory>

Alias /nagiosxi "/usr/local/nagiosxi/html"

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule nagiosxi/api/v1/(.*)$ /usr/local/nagiosxi/html/api/v1/index.php?request=$1 [QSA,NC,L]
</IfModule>

[root@daihatsu ~]# cat /etc/httpd/conf/httpd.conf
#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
Include conf.modules.d/*.conf

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User apache
Group apache

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
#
ServerAdmin root@localhost

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName http://www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
AllowOverride none
Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
AllowOverride None
# Allow open access:
Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied
</Files>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common

<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
#CustomLog "logs/access_log" common

#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

</IfModule>

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>

<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /etc/mime.types

#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

# For type maps (negotiated resources):
#AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
</IfModule>

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
MIMEMagicFile conf/magic
</IfModule>

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf

Nagios System Settings.png

[root@daihatsu ~]# nslookup daihatsu
;; Truncated, retrying in TCP mode.
Server: xxx.xxx.xxx.xxx
Address: xxx.xxx.xxx.xxx#53

Name: daihatsu.pcu.local
Address: 10.10.97.251

[root@daihatsu ~]# nslookup 10.10.97.251
Server: xxx.xxx.xxx.xxx
Address: xxx.xxx.xxx.xxx#53

251.97.10.10.in-addr.arpa name = daihatsu.pcu.local.

[root@daihatsu ~]#

[slater86]

Mod Edit: I have split your topic from this one: https://support.nagios.com/forum/viewto ... 2&start=10
In the future please start your own topic and link to the referenced one so we can keep users' issues separate

Just noticed the comment on the top advising the thread was split. Apologies tmcdonald, I had originally created a new topic as you suggested https://support.nagios.com/forum/viewto ... =6&t=36752 but thought it best to close as it was a duplicate discussion on the same topic. I'm new here and have not yet learned the local etiquette on forum discussion vs specific questions.

Apologies if I offended anyone and/or highjacked the thread.

[rkennedy]

No problem, thanks for understanding.

I don't see anything that stands out too much, what version of apache are you running?

Code: Select all

apachectl -v

Just to make sure, as you describe your reverse proxy situation for SSL, is this how it's setup inbound? - internet -> reverse proxy -> nagios? Does Nagios use a proxy going ountbound?

[slater86]

New server is running Apache 2.4.6
[root@daihatsu ~]# apachectl -v
Server version: Apache/2.4.6 (CentOS)
Server built: Nov 19 2015 21:43:13

Old server (with the reverse proxy) is running Apache 2.2.15
[root@OldServer ~]# apachectl -v
Server version: Apache/2.2.15 (Unix)
Server built: Dec 15 2015 15:50:14

Neither server have an outgoing proxy set either at Linux (system level) or in the NagiosXI CCM
The reverse proxy is only used for afterhours remote phone access (to expose cgi-bin to thirdparty app "aNag") and is not used for the NagiosXI frontend.

[tgriep]

Can you login as root on the XI server, run the following commands and post the output?

Code: Select all

echo 'select * from nagios_scheduleddowntime ;' | mysql  -t -pnagiosxi nagios
echo 'desc nagios_scheduleddowntime ;' | mysql  -t -pnagiosxi nagios
tail -50 /var/log/mysqld.log

Thanks