Mike Cote

Are those the httpd access_logs? All I see there are the 500 errors: [10/Mar/2020:14:46:34 -0400] "GET /nagiosql-3.4.1/index.php HTTP/1.1" 500 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0" [10/Mar/2020:14:47:04 -0400] "GET /nagiosql-3.4.1/index.php HTTP/1.1" 500 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0" [10/Mar/2020:14:47:04 -0400] "GET /nagiosql-3.4.1/index.php HTTP/1.1" 500 - "-" "Mozilla/5.0 (Windows NT 10.0;...

Yeah, we're looking good. Thanks again for following up and thanks again for your help, Martin

Sorry for the triple-post, but I think it definitely had to do with pear as you suggested in another thread. I ended up enabling error outputs in the browser and saw a failure for pear. I installed Pear and it now seems to be running with a timezone warning. Sorry for the trouble and than you for the help

Sorry for the double post, but I'm also able to see sub folders from a web browser. For example, my base path ('/var/www/html/nagiosql-3.4.1/') shows a blank page in the web browser, but if I manually head to one of the sub-folders (e.g. /config/), I'll see the directory and file index via the browser. It looks to be that way for other folders, as well (exceptions being the admin and base folders). Permissions look the same on each folder and files within, though.

I took a look at the log, but didn't see anything that looked specific to this being blocked. Not knowing a whole lot about selinux (or linux in general), I disabled selinux as a test (selinux status is currently disabled). It looks like the blank pages still pop with it disabled. Is there anywhere else I can check for this sort of behavior?

First off, I'm a CentOS and Linux noob, so I'm pretty blind when working on the system. I had installed and have been running Nagios 4.4.2 with NagiosQL 3.4.0 and all was well until a batch of CentOS updates I ran yesterday. Now when I open the NagiosQL page, I just get a blank screen in Firefox or an HTTP 500 error in Chrome. NAgios itself seems to be running fine, though. I saw a couple other similar posts here where it was suggested that we make sure pear is installed (I did that) and that Apache...