Bug #61045 [Com]: fpm don't send error log to fastcgi clients(nginx)
Edit report at https://bugs.php.net/bug.php?id=61045&edit=1 ID: 61045 Comment by: ewgraf at gmail dot com Reported by:lxlight at gmail dot com Summary:fpm don't send error log to fastcgi clients(nginx) Status: Open Type: Bug Package:FPM related Operating System: Linux PHP Version:5.3.10 Block user comment: N Private report: N New Comment: Add patch for 5.3.10. It simple, not so right, because I think this functionality need move to zlog_ex, but it works for me. If anybody can review it and test, would be nice. Previous Comments: [2012-02-13 19:43:05] me at nicholassavilerobinson dot com I confirm this deficiency: php5-fpm 5.3.9+ prevents fpm passing error_log output to the web server's error log via SAPI. I encounter this issue using nginx 1.0.11, but it is also present with older nginx releases. The problem is encountered even with 777 permissions on the logs. If I roll back to php5-fpm_5.3.8 (keeping the same configs), it starts working again. I would like fpm STDERR to output to the virtual host's error log (this was the default behavior before). A sample php.ini/php-fpm.conf is attached: /etc/php5/fpm/php.ini [PHP] engine = On short_open_tag = Off asp_tags = Off precision = 14 y2k_compliance = On output_buffering = 4096 zlib.output_compression = Off implicit_flush = Off unserialize_callback_func = serialize_precision = 17 allow_call_time_pass_reference = Off safe_mode = Off safe_mode_gid = Off safe_mode_include_dir = safe_mode_exec_dir = safe_mode_allowed_env_vars = PHP_ safe_mode_protected_env_vars = LD_LIBRARY_PATH disable_functions = disable_classes = expose_php = On max_execution_time = 30 max_input_time = 60 memory_limit = 128M error_reporting = E_ALL & ~E_DEPRECATED display_errors = Off display_startup_errors = Off log_errors = On log_errors_max_len = 1024 ignore_repeated_errors = Off ignore_repeated_source = Off report_memleaks = On track_errors = Off html_errors = Off variables_order = "GPCS" request_order = "GP" register_globals = Off register_long_arrays = Off register_argc_argv = Off auto_globals_jit = On post_max_size = 8M magic_quotes_gpc = Off magic_quotes_runtime = Off magic_quotes_sybase = Off auto_prepend_file = auto_append_file = default_mimetype = "text/html" doc_root = user_dir = enable_dl = Off file_uploads = On upload_max_filesize = 2M max_file_uploads = 20 allow_url_fopen = On allow_url_include = Off default_socket_timeout = 60 /etc/php5/fpm/php-fpm.conf: [global] pid = /var/run/php5-fpm.pid error_log = /var/log/php5-fpm.log [www] listen = /tmp/fcgi.socket user = www-data group = www-data pm = dynamic pm.max_children = 50 pm.start_servers = 25 pm.min_spare_servers = 5 pm.max_spare_servers = 35 pm.max_requests = 500 pm.status_path = /status ping.path = /ping ping.response = Ok slowlog = log/$pool.log.slow chdir = / [2012-02-10 14:27:29] lxlight at gmail dot com Description: Since php 5.3.9 released with any variation of config parameters php-fpm don't send php script errors/warnings to nginx. Reading logs on one frontend which contains get request, referrer, backend host is very simply. Pleas add the ability to send stderr to frontend when error_log is undefined. -- Edit this bug report at https://bugs.php.net/bug.php?id=61045&edit=1
#47199 [Com]: pg_delete fails on NULL
ID: 47199 Comment by: ewgraf at gmail dot com Reported By: andrew at labyrinth-it dot co dot uk Status: Open Bug Type: PostgreSQL related Operating System: Linux (Fedora) PHP Version: 5.2.10 New Comment: Patch for this bug: http://news.php.net/php.internals/46974 Previous Comments: [2009-05-31 06:27:21] andrew at labyrinth-it dot co dot uk Sorry, I think I posted my reply in the wrong place, so let me try again. I have just downloaded and tested the latest PHP version: PHP 5.2.10RC2-dev (cli) (built: May 31 2009 07:16:36) With this version I still get the same error. The Postgresql version I am testing against is: PostgreSQL 8.3.5 on i386-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.3.2 20081007 (Red Hat 4.3.2-6) The call to: print(pg_delete($db,'demo',$row,PGSQL_DML_STRING)) still prints out: DELETE FROM demo WHERE id=1 AND col1=NULL; The final test should use the SQL language "IS NULL" test rather than "=NULL" which never evaluates to true. The same problem exists if using pg_update, which produces: UPDATE demo SET id=2,col1='Two' WHERE id=1 AND col1=NULL; Again, "col1=NULL" will never evaluate to true using SQL, and the test col1 IS NULL should be used instead. [2009-05-19 15:34:41] andrew at labyrinth-it dot co dot uk For completeness, I get the error running on Fedora 10 with Postgres 8.3.5 [2009-05-19 15:31:54] andrew at labyrinth-it dot co dot uk I am using: PHP 5.2.10-dev (cli) (built: May 19 2009 15:40:36) and still get the same error result. This error is also in the pg_update function, where NULl values are compared with "= NULL" rather than "IS NULL" in the WHERE part of the generated SQL. [2009-01-23 11:46:35] andrew at labyrinth-it dot co dot uk Description: pg_delete uses incorrect syntax for NULL columns. The code generated compares values with "col = NULL" instead of "col IS NULL". As a result, the row is not matched so is not deleted. Reproduce code: --- 1 [col1] => ) DELETE FROM demo WHERE id=1 AND col1 IS NULL; Actual result: -- When this runs, the second loop displays results for tables that have NULL columns at the start of the run. --- Array ( [id] => 1 [col1] => ) DELETE FROM demo WHERE id=1 AND col1=NULL; Array ( [id] => 1 [col1] => ) -- Edit this bug report at http://bugs.php.net/?id=47199&edit=1
Bug #63257 [Com]: checkdate(): Wrong if year is two digits and year is 2000
Edit report at https://bugs.php.net/bug.php?id=63257&edit=1
ID: 63257
Comment by: ewgraf at gmail dot com
Reported by:php at skay dot se
Summary:checkdate(): Wrong if year is two digits and year is
2000
Status: Open
Type: Bug
Package:*Calendar problems
Operating System: Unix
PHP Version:5.3.10
Block user comment: N
Private report: N
New Comment:
Seems not a bug.
>From manual:
> 'year' The year is between 1 and 32767 inclusive.
int from "00" will be 0
Previous Comments:
[2012-10-10 22:22:19] php at skay dot se
Description:
---
>From manual page: http://www.php.net/function.checkdate
---
If year is 2000 the function will return TRUE (provided the rest is valid) -
Thats good!
But if year is 00 the function will always return FALSE
Test script:
---
echo checkdate("01", "01", "2000");
echo checkdate("01", "01", "00");
Expected result:
TRUE
TRUE
Actual result:
--
TRUE
FALSE
[2012-10-10 22:17:13] php at skay dot se
Description:
---
>From manual page: http://www.php.net/function.checkdate
---
PHP version 5.3.10
If year is 2000 the function will return TRUE (provided the rest is valid) -
Thats good!
But if year is 00 the function will always return FALSE
Test script:
---
echo checkdate("01", "01", "2000");
echo checkdate("01", "01", "00");
Expected result:
TRUE
TRUE
Actual result:
--
TRUE
FALSE
--
Edit this bug report at https://bugs.php.net/bug.php?id=63257&edit=1
