THL Posted April 15, 2013 Share Posted April 15, 2013 When I visit my xcache admin panel and select LIST PHP I get a list of repetitive errors, any suggestions as to what's causing this and a way to resolve it? Link to comment Share on other sites More sharing options...
Marcher Technologies Posted April 15, 2013 Share Posted April 15, 2013 You have PHP error reporting set to a development value, IPB does the same thing in certain areas at this time, please change the values to production, notices/warnings should not be output to screen revealing paths for the script kiddies on a live site. Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 How do I change this to production marcher? Link to comment Share on other sites More sharing options...
Marcher Technologies Posted April 15, 2013 Share Posted April 15, 2013 How do I change this to production marcher? php.ini. you likely have either: error_reporting = E_ALL | E_STRICT or, and more likely, the default: error_reporting = E_ALL & ~E_NOTICE and with it(also default): display_errors = On On production, it is recommended to use: error_reporting = E_ALL & ~E_DEPRECATED turning: display_errors = Off is also recommended, but should be remembered, as err fatal will white-screen, and you will need to change this to debug such an error. Reboot the server after making changes to php.ini Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 is also recommended, but should be remembered, as err fatal will white-screen, and you will need to change this to debug such an error. Reboot after making changes to php.ini Not sure what you mean by err fatal and changing marcher? Link to comment Share on other sites More sharing options...
Marcher Technologies Posted April 15, 2013 Share Posted April 15, 2013 Not sure what you mean by err fatal and changing marcher? Generally, it should not happen on production. Smacks of one not checking the code/testing. If it comes down to it, what it means is that if you get a blank white page with that set to Off, a fatal error occurred, PHP has 'stopped' executing at that point on that page and to actually get the real error, that's going to need to be turned back On. Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 This is the error setup on my php.inj ; Error handling and logging ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; error_reporting is a bit-field. Or each number up to get desired error ; reporting level ; E_ALL - All errors and warnings ; E_ERROR - fatal run-time errors ; E_WARNING - run-time warnings (non-fatal errors) ; E_PARSE - compile-time parse errors ; E_NOTICE - run-time notices (these are warnings which often result ; from a bug in your code, but it's possible that it was ; intentional (e.g., using an uninitialized variable and ; relying on the fact it's automatically initialized to an ; empty string) ; E_CORE_ERROR - fatal errors that occur during PHP's initial startup ; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's ; initial startup ; E_COMPILE_ERROR - fatal compile-time errors ; E_COMPILE_WARNING - compile-time warnings (non-fatal errors) ; E_USER_ERROR - user-generated error message ; E_USER_WARNING - user-generated warning message ; E_USER_NOTICE - user-generated notice message ; ; Examples: ; ; - Show all errors, except for notices ; ;error_reporting = E_ALL & ~E_NOTICE ; ; - Show only errors ; ;error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR ; ; - Show all errors except for notices ; error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED ; Print out errors (as a part of the output). For production web sites, ; you're strongly encouraged to turn this feature off, and use error logging ; instead (see below). Keeping display_errors enabled on a production web site ; may reveal security information to end users, such as file paths on your Web ; server, your database schema or other information. display_errors = Off ; Even when display_errors is on, errors that occur during PHP's startup ; sequence are not displayed. It's strongly recommended to keep ; display_startup_errors off, except for when debugging. display_startup_errors = Off ; Log errors into a log file (server-specific log, stderr, or error_log (below)) ; As stated above, you're strongly advised to use error logging in place of ; error displaying on production web sites. log_errors = On ; Set maximum length of log_errors. In error_log information about the source is ; added. The default is 1024 and 0 allows to not apply any maximum length at all. log_errors_max_len = 1024 ; Do not log repeated messages. Repeated errors must occur in same file on same ; line until ignore_repeated_source is set true. ignore_repeated_errors = Off ; Ignore source of message when ignoring repeated messages. When this setting ; is On you will not log errors with repeated messages from different files or ; sourcelines. ignore_repeated_source = Off ; If this parameter is set to Off, then memory leaks will not be shown (on ; stdout or in the log). This has only effect in a debug compile, and if ; error reporting includes E_WARNING in the allowed list report_memleaks = On ; Store the last error/warning message in $php_errormsg (boolean). track_errors = Off ; Disable the inclusion of HTML tags in error messages. ;html_errors = Off ; If html_errors is set On PHP produces clickable error messages that direct ; to a page describing the error or function causing the error in detail. ; You can download a copy of the PHP manual from http://www.php.net/docs.php ; and change docref_root to the base URL of your local copy including the ; leading '/'. You must also specify the file extension being used including ; the dot. ;docref_root = "/phpmanual/" ;docref_ext = .html ; String to output before an error message. ;error_prepend_string = "<font color=ff0000>" ; String to output after an error message. ;error_append_string = "</font>" ; Log errors to specified file. error_log = error_log ; Log errors to syslog (Event Log on NT, not valid in Windows 95). ;error_log = syslog Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 Should I change it to the format you suggested Marcher? Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 Just changed it to error_reporting = E_ALL & ~E_DEPRECATED Also display errors was already off. Errors still show though. Link to comment Share on other sites More sharing options...
Marcher Technologies Posted April 15, 2013 Share Posted April 15, 2013 Just changed it to error_reporting = E_ALL & ~E_DEPRECATED Also display errors was already off. Errors still show though. restart the server? Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 Yes restarted apache and mysql This is my updated php.ini ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Error handling and logging ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; error_reporting is a bit-field. Or each number up to get desired error ; reporting level ; E_ALL - All errors and warnings ; E_ERROR - fatal run-time errors ; E_WARNING - run-time warnings (non-fatal errors) ; E_PARSE - compile-time parse errors ; E_NOTICE - run-time notices (these are warnings which often result ; from a bug in your code, but it's possible that it was ; intentional (e.g., using an uninitialized variable and ; relying on the fact it's automatically initialized to an ; empty string) ; E_CORE_ERROR - fatal errors that occur during PHP's initial startup ; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's ; initial startup ; E_COMPILE_ERROR - fatal compile-time errors ; E_COMPILE_WARNING - compile-time warnings (non-fatal errors) ; E_USER_ERROR - user-generated error message ; E_USER_WARNING - user-generated warning message ; E_USER_NOTICE - user-generated notice message ; ; Examples: ; ; - Show all errors, except for notices ; ;error_reporting = E_ALL & ~E_NOTICE ; ; - Show only errors ; ;error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR ; ; - Show all errors except for notices ; error_reporting = E_ALL & ~E_DEPRECATED ; Print out errors (as a part of the output). For production web sites, ; you're strongly encouraged to turn this feature off, and use error logging ; instead (see below). Keeping display_errors enabled on a production web site ; may reveal security information to end users, such as file paths on your Web ; server, your database schema or other information. display_errors = Off ; Even when display_errors is on, errors that occur during PHP's startup ; sequence are not displayed. It's strongly recommended to keep ; display_startup_errors off, except for when debugging. display_startup_errors = Off ; Log errors into a log file (server-specific log, stderr, or error_log (below)) ; As stated above, you're strongly advised to use error logging in place of ; error displaying on production web sites. log_errors = On ; Set maximum length of log_errors. In error_log information about the source is ; added. The default is 1024 and 0 allows to not apply any maximum length at all. log_errors_max_len = 1024 ; Do not log repeated messages. Repeated errors must occur in same file on same ; line until ignore_repeated_source is set true. ignore_repeated_errors = Off ; Ignore source of message when ignoring repeated messages. When this setting ; is On you will not log errors with repeated messages from different files or ; sourcelines. ignore_repeated_source = Off ; If this parameter is set to Off, then memory leaks will not be shown (on ; stdout or in the log). This has only effect in a debug compile, and if ; error reporting includes E_WARNING in the allowed list report_memleaks = On ; Store the last error/warning message in $php_errormsg (boolean). track_errors = Off ; Disable the inclusion of HTML tags in error messages. ;html_errors = Off ; If html_errors is set On PHP produces clickable error messages that direct ; to a page describing the error or function causing the error in detail. ; You can download a copy of the PHP manual from http://www.php.net/docs.php ; and change docref_root to the base URL of your local copy including the ; leading '/'. You must also specify the file extension being used including ; the dot. ;docref_root = "/phpmanual/" ;docref_ext = .html ; String to output before an error message. ;error_prepend_string = "<font color=ff0000>" ; String to output after an error message. ;error_append_string = "</font>" ; Log errors to specified file. error_log = error_log ; Log errors to syslog (Event Log on NT, not valid in Windows 95). ;error_log = syslog Link to comment Share on other sites More sharing options...
Marcher Technologies Posted April 15, 2013 Share Posted April 15, 2013 please repost the screenshot you removed. I(and others) need to see the text of the warning(s) that defy the php config again 0.o, blur root paths. Link to comment Share on other sites More sharing options...
THL Posted April 15, 2013 Author Share Posted April 15, 2013 Here it is Link to comment Share on other sites More sharing options...
GreenLinks Posted April 15, 2013 Share Posted April 15, 2013 That maybe a bug on xCache version you are using , i suggest you upgrade to most recent version 3.0.1 Link to comment Share on other sites More sharing options...
Grumpy Posted April 16, 2013 Share Posted April 16, 2013 Turn off notices... Such a useless thing...add "& ~E_NOTICE" at the end of your error_reporting. Link to comment Share on other sites More sharing options...
Dmacleo Posted April 16, 2013 Share Posted April 16, 2013 2.01...this cpanel server? thats what easyapache uses. Link to comment Share on other sites More sharing options...
THL Posted April 20, 2013 Author Share Posted April 20, 2013 2.01...this cpanel server? thats what easyapache uses. Dont understand? Link to comment Share on other sites More sharing options...
Dmacleo Posted April 20, 2013 Share Posted April 20, 2013 cpanel xcahe is version 2.01 so if installed though cpanel (by using easyapache) you get 2.01, and if there a bug you need to add new version manually. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.