Nagios Support Forum

Hi,

We are evaluating Nagios XI and I and I have encountered a problem with the Core Configuration Manager. After I've made changes I click "Apply Configuration" and the https://usok1mon1.mn.us.syntegra.com/na ... config.php page comes up, displaying cascading dots forever.

However if I go into Write Config Files under Tools and perform all three steps, everything works as expected. So this is a work-around. But I'd like to understand why the "Apply Configuration" function is broken and get it fixed.

From my /etc/php.ini file, I have the following:
max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M ; Maximum amount of memory a script may consume

I have also changed the following line in the /usr/local/nagiosxi/html/config.inc.php file:
$cfg['use_https']=true; // determines whether cron jobs and other scripts will force the use of HTTPS instead of HTTP

Also, in Config Manager Settings, I have changed "Server Protocol" to "https".

Both Apache and Nagios have been restarted. But none of this has helped. I would welcome any advice about how to trouble-shoot this or correct it. Thanks in advance.

--
Jay Hill

Nagios XI version: 2012R1.3
manual install on Oracle Linux Server release 5.8 (A RHEL clone, much like CentOS), 64-bit
No Gnome, proxy required for Internet access, we are using SSL

When I go in to the Core Config Manager and click "Apply Configuration", a page comes up with cascading dots but it never finishes.

From our /etc/php.ini file:
max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M ; Maximum amount of memory a script may consume

I've modified the following line in /usr/local/nagiosxi/html/config.inc.php:
$cfg['use_https']=true; // determines whether cron jobs and other scripts will force the use of HTTPS instead of HTTP

Also, in Core Config Manager, under Config Manager Settings, I set Server Protocol to https.

I don't know enough about the inner workings of NagiosXI to diagnose this for myself. Any help would be appreciated.

--
Jay Hill

Lets first make sure you can verify your config, please run the following and let me know what it returns:
Also, can you tail your php error log file and display the output here?:
What browser are you applying configuration in? i.e firefox, internet explorer, google chrome etc..
Did you make any system changes directly prior to this issue?

Hi newby here

I seem to have this same issue:

Distro: Red Hat Enterprise Linux Server release 6.6 (Santiago)
Kernel: 2.6.32-504.3.3.el6.x86_64 x86_64
Memory: 8.06 GB
Current User:
Manufacturer: No Enclosure
Model: VMware Virtual Platform
Firmware Version: 6.00
Firmware Release Date: 04/14/2014
Number of CPU(s): 4
CPU Cache: 25600 KB
CPU Model: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz

Fresh Nagios XI 2014R2.3 install

Applying Configuration never finishes ........

no errors in nagios.log

mysql.log:
150112 13:47:49 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140930 14:23:17 mysqld_safe Starting mysqld daemon with databases from /opt/mysql
140930 14:24:17 InnoDB: Initializing buffer pool, size = 8.0M
140930 14:24:17 InnoDB: Completed initialization of buffer pool
140930 14:24:18 InnoDB: Started; log sequence number 0 44233
140930 14:24:18 [Note] Event Scheduler: Loaded 0 events
140930 14:24:18 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution

httpd/error_log:
[Tue Jan 13 09:15:43 2015] [error] [client 127.0.0.1] PHP Notice: Undefined index: ccm_language in /usr/local/nagiosxi/html/includes/components/ccm/includes/common_functions.inc.php on line 710
[Tue Jan 13 09:15:43 2015] [error] [client 127.0.0.1] PHP Notice: Undefined index: language in /usr/local/nagiosxi/html/includes/components/ccm/includes/common_functions.inc.php on line 710
[Tue Jan 13 09:25:17 2015] [notice] caught SIGTERM, shutting down
[Tue Jan 13 09:25:17 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 13 09:25:17 2015] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 13 09:25:17 2015] [notice] Digest: done
[Tue Jan 13 09:25:18 2015] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg shows:
Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check

ls -lart /usr/local/nagiosxi/html/includes/lang/locale/ shows:
total 868
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 zh_CN
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 en_US
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 es_ES
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 de_DE
-rw-r--r-- 1 nagios nagios 794 Jan 12 12:01 default.mo
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 pt_PT
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 fr_FR
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 ko_KR
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 ru_RU
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 ja_JP
-rw-r--r-- 1 nagios nagios 831402 Jan 12 12:01 default.pot
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 zh_TW
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 it_IT
drwxr-xr-x 13 nagios nagios 4096 Jan 12 12:01 .
drwxr-xr-x 3 nagios nagios 4096 Jan 12 12:01 ..

/etc/php.ini:
egrep "max_execution_time|max_input_time|memory_limit" /etc/php.ini
; max_input_time
max_execution_time = 60
max_input_time = 60
memory_limit = 256M


So I guess I've made a mistake somewhere along the lines. Anyone can point me in the right directions?

What you have shown here suggest that either crond isnt running or that the nagios user is expired

Can you run the following If it still doesn't work, please post back the output of the following Thanks

You are right (partially).

cron is running, thanks for the probe ... (nothing in any log file though)
however we are using LDAP and PAM so the issue is with security !

Here is the fix:

edit /etc/security/access.conf and add [/i][/b]

Also,
during install it would be wise to check if LDAP is being used.

Few things I had to do to get it installed properly. i.e. disable nslcd
and of course the dreaded proxy by pass, but all good now.

Thanks again for the nudge.

Cheers,
hw

Glad that helped you resolve the issue. I'll close this thread, but feel free to open a new one whenever the need strikes.