I’m working on a PHP5-FPM/Nginx setup.
For some reason, there are certain errors that PHP5-FPM doesn’t seem to want to log. Specifically, it seems there are two files that it just doesn’t want to have errors in. I’m sure that I am including those files (I can fix the error, it works, make an error, it breaks). However, for some reason both Nginx’s error log (which usually reports it) and php5-fpm’s error log both remain silent.
Any ideas? This is going to get very aggravating trying to build something without being able to find it’s errors.
Thanks.
So, I’ve been testing even more. As a test I added:
ini_set('display_errors', 'On');
error_reporting(E_ALL);
to the top of my first page. I then made a mistake in the file in question (various types of mistake, mostly misspelling tokens), and it still didn’t show anything (though it did stop sending a 500 error).
The files in question are testing pretty deep (I think they are 3-5 requires down), so I thought maybe that was causing some weird reporting issue. However, I included one of the pages on like my first line of the file directly and it still didn’t give me any errors… any ideas?
EDIT: Correction, it does show the error (I just forgot to upload the file). However, with it in it’s original spot that same file doesn’t show an error, but does cause one…
… wow I’m dumb. =p
On one of the include statements, I had @ to suppress errors. Apparently that suppressed ALL errors, not just errors generated by the include itself.
Is that the correct behavior though? I thought @ should just cause it to suppress the errors related to the include itself… not ALL errors generated after the include.