trouble with display_errors

sing1ejack

I'm having some trouble getting the php errors to display in the browser.

I have set display_errors = On in /etc/php.ini When i did:

updatedb

locate php.ini

the only one that came up was /etc/php.ini and phpinfo() shows /etc/php.ini as the .ini file.

So I searched around in httpd.conf and the string "php" didn't show up once so I'm guessing that's where the problem is. I saw the thread posted here and tried to follow along, but it didn't work. I attached my copies of httpd.conf (my changes are at the bottom) and php.ini. I'd love a little help on this.

sing1ejack

You should ignore the php.ini file in that zip archive. I replaced my old php.ini file with a fresh copy of "php.ini-recommended", changed display_errors = On, and that's what is in the zip archive. But I just found out that when I'm using the new php.ini file I get a whole bunch of warnings about not being able to find .so files.

Luckily I saved the old php.ini file and just replaced it. So I guess that proves that I'm working with the right php.ini file, huh? Here's the good version:

bradgrafelman

So are you back to using the first php.ini file?

If so, your problem is that you added a line towards the beginning of the .ini file. The display_errors directive is already specified later in that document - you can't just add a line and expect PHP to know which one to use. In fact, PHP will, as it appears, use the last configuration that it was told. In the first .ini file you attached above, the last line containing display_errors is line #374, which turns display_errors Off.

Long story short: Don't simply add new lines to the php.ini file to alter a directive; search the file for that directive and edit it's previous value.

sing1ejack

Thanks, yeah that was the problem. I'm an idiot. I saw the example that was commented out & assumed that I was just supposed to put a new line above it.

And somewhere in there I created another problem for myself. Now when I run anything from the commandline ( the program <?php phpinfo(); ?> for example) I get all these warnings:

PHP Warning:  PHP Startup: Unable to load dynamic library './ldap.so' - ./ldap.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library './mbstring.so' - ./mbstring.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library './mysql.so' - ./mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library './mysqli.so' - ./mysqli.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library './pdo.so' - ./pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library './pdo_mysql.so' - ./pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library './pdo_sqlite.so' - ./pdo_sqlite.so: cannot open shared object file: No such file or directory in Unknown on line 0

I must have screwed something up somewhere, but I don't know what would cause this. Any ideas? It seems like it has to be in the php.ini since I replaced the httpd.conf I was tinkering with with the origional.

sing1ejack

or maybe a permissions problem?

bradgrafelman

Looks like you've never installed the libraries for those modules, so you can't possibly load them. Comment out their lines in your php.ini file - look for all of the "extension=" lines and put a semicolon before the ones that are failing (or that you don't need).

sing1ejack

Hm, strange. I've been working from the command line for several days and today, after messing with these config files, is the first time these warnings have come up. And in the directory /usr/lib/php/modules/ every one of these files seems to exist (mysql.so, mysqli.so, etc). They are all owned by root - I assume that's not a problem though.

Furthermore I don't see any lines in the php.ini file that look like "extension=mysql.so". It doesn't even look like the php.ini file is looking in the right directory:

; Directory in which the loadable extensions (modules) reside.
extension_dir = "./"

But I tried setting the directory to "/usr/lib/php/modules" and that didn't seem to help. Do I need to restart httpd every time I make a change to php.ini or not? And could I be recieving these warnings because I'm not loading them in the php.ini file? .. guess I just don't understand what's going on.

bradgrafelman

sing1ejack wrote:
Do I need to restart httpd every time I make a change to php.ini or not?

Yes - every single change.

sing1ejack wrote:
And could I be recieving these warnings because I'm not loading them in the php.ini file?

No, these messages are telling you PHP tried to load the modules but couldn't.

sing1ejack

Hm, further down in php.ini it says

;;;;
; Note: packaged extension modules are now loaded via the .ini files
; found in the directory /etc/php.d; these are loaded by default.
;;;;

And sure enough, there's an .ini file for each module in /etc/php.d/. That explains why there aren't any "extension=module.extension" lines in php.ini. But it doesn't explain why these extensions aren't being loaded. What exactly does "loaded by default" mean? Because if it's ordained by php.ini I may have screwed it up, if not then it should still be working shouldn't it?