Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
@onegative, As far as the white screen error goes, I'd recommend increasing the settings in the /etc/php.ini file.
If you send me the existing INI file, I will be able to suggest what to use instead.
And while this command is running try to access the scheduled downtime page and let me know if you see any errors in the console beside that entry in the access log.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
@onegative, I noticed that your Nagios related sudoers entries are in a custom file inside the /etc/sudoers.d/ directory.
But in the main /etc/sudoers file you commented out the includedir statement:
This is a special thing within the sudoers file...it does not mean comment as most people perceive...please observe below...
#includedir /etc/sudoers.d
Other special characters and reserved words: The pound sign (`#') is used to indicate a comment (unless it is part of a #include directive or unless it occurs in the context of a user name and is followed by one or more digits, in which case it is treated as a uid). Both the comment character and any text after it, up to the end of the line, are ignored.
As shown below the apache user has the following sudo entries available:
# sudo -lU apache Matching Defaults entries for apache on dcom-nagiosxi-p1:
!visiblepw, always_set_home, env_reset, env_keep="COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR LS_COLORS", env_keep+="MAIL PS1 PS2 QTDIR
USERNAME LANG LC_ADDRESS LC_CTYPE", env_keep+="LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES", env_keep+="LC_MONETARY LC_NAME
LC_NUMERIC LC_PAPER LC_TELEPHONE", env_keep+="LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY",
secure_path=/usr/local/bin\:/sbin\:/bin\:/usr/sbin\:/usr/bin, !requiretty
User apache may run the following commands on dcom-nagiosxi-p1:
(root) NOPASSWD: /usr/bin/tail * /var/log/messages
(root) NOPASSWD: /usr/bin/tail * /var/log/httpd/error_log
(root) NOPASSWD: /usr/bin/tail * /var/log/mariadb/mariadb.log
(root) NOPASSWD: /usr/bin/php /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php *
(root) NOPASSWD: /usr/local/nagiosxi/html/includes/components/profile/getprofile.sh
(root) NOPASSWD: /etc/init.d/snmptt restart
(root) NOPASSWD: /usr/local/nagiosxi/scripts/repair_databases.sh
(root) NOPASSWD: /usr/local/nagiosxi/scripts/manage_services.sh *
@onegative, I haven't seen this issue happening during the upgrades to XI 5.6.2. It could be that Nagios tried to insert this entry to the /etc/sudoers file and then the entry got deleted. Or maybe you didn't click yes when the upgrade script asked about updating the sudoers entries. It's hard to tell at this point.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.