[opensuse] SuSE 9.3: apache2 error_log unreadable - contains multitudes of "APPLYING include_path" entries
We are running SuSE Linux 9.3 with Apache 2 and PHP5. Apache is set up with 4 virtual hosts, all of which have their PHP include paths set in the vhost.conf of vhost-ssl.conf files, like this: php_value include_path "/my/include/path" We're getting this kind of messages in Apache error_log, over and over again, which makes the log unreadable: Getting include_path= Creating new config (0x6d6a08) for (null) Merge dir (0x5c16b8) (0x6e7b98) APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. Why is this happening? How do we fix this? Thank you, Alex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aleksandra Bednarek escribió:
We are running SuSE Linux 9.3 with Apache 2 and PHP5.
9.3 is out of support. APPLYING (include_path)(.
Why is this happening? How do we fix this?
with that old stuff many things can happend. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aleksandra Bednarek wrote:
We are running SuSE Linux 9.3 with Apache 2 and PHP5. Apache is set up with 4 virtual hosts, all of which have their PHP include paths set in the vhost.conf of vhost-ssl.conf files, like this:
php_value include_path "/my/include/path"
We're getting this kind of messages in Apache error_log, over and over again, which makes the log unreadable:
Getting include_path= Creating new config (0x6d6a08) for (null) Merge dir (0x5c16b8) (0x6e7b98) APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(. APPLYING (include_path)(.
Why is this happening? How do we fix this?
Thank you, Alex
Use grep -v <text to exclude> <log file name> to filter out the stuff you do not want which should make log more readable ... Do not know why it is happening or any idea for a cure, but the above is a quick kludge which will keep you going until you find one... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHOW2aasN0sSnLmgIRAjAEAJ4z5MTLNjBE2D+ZYa8TtASu0uDspQCeNPI8 vf1f6yqujdcpQ2/D8+CqpSA= =DF/t -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aleksandra Bednarek escribió: (.
Why is this happening?
Look, I will explain you ;) you are seeing mod_php5 debug loglevel information, that is written when the module starts applying the PHP.ini configuration you want, as long as you dont see "...FAILED" there is nothing to worry about .. How do we fix this? as long you are running the packages shipped with 9.3 you cant, seems there was a compile time bug where PHP was built with --enable-debug that's the reason why you seeing those messages. If you upgrade to 10.3 the messages will go away ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Aleksandra Bednarek -
Cristian Rodríguez -
G T Smith