Nagios Support Forum

Yes, but my apologies.

Duplicate ticket. Please close this one, thank you.

The issue is being worked on ticket: https://support.nagios.com/forum/viewto ... 11&start=0

SYSTEM: *Linux Distribution and version? 2.6.18-404.el5 *32 or 64bit? 32 *VMware Image or Manual Install of XI? VMWare Image *Are there special configurations on your system, ie; is Gnome installed? Are you using a proxy? Are you using SSL? SSL ISSUE: When loading the the NagiosXi login page via a ...

That fixed it thank you!

btw, I installed the NagiosXi2014 in our dev box to test it out, and it looks great!

Thank you for all you do,
Eddie

System Info Linux Distribution and version? *Linux fwapp003.wvus.org 2.6.18-371.4.1.el5PAE #1 SMP Thu Jan 30 06:51:58 EST 2014 i686 i686 i386 GNU/Linux CentOS release 5.10 (Final) 32 or 64bit? 32 bit VMware Image or Manual Install of XI? VMware Image Are there specials configurations on your system...

Did you check which log filled up the most? the /var/log/httpd/error.log Also, what is on line 93, as the error.log was full of the following error (We cannot see it, as the coreuiproxy.inc.php is encrypted): PHP Warning: feof(): supplied argument is not a valid stream resource in /usr/local/nagiosx...

Echoed out all Apache error logs Purged /usr/local/nagvis/var/nagvis-audit.log Configured new cronjob for 6am daily to purge echo > /usr/local/nagvis/var/nagvis-audit.log Checked perms on /usr/local/nagiosxi/html/images/locale/.htaccess - file doesn't exist Created file - touch /usr/local/nagiosxi/...

Thanks, but what error would have caused this log file to fill up?

System Info Linux Distribution and version? *Linux fwapp003.wvus.org 2.6.18-371.4.1.el5PAE #1 SMP Thu Jan 30 06:51:58 EST 2014 i686 i686 i386 GNU/Linux CentOS release 5.10 (Final) 32 or 64bit? 32 bit VMware Image or Manual Install of XI? VMware Image Are there specials configurations on your system...

I am having the same issue and I've followed all the outlined steps to remove "ghosts...".

Resolved during a Nagios Support gotomeeting by Mike, as we were working on a high critical issue and made sure this was not related.

It was permissions issue related.