Edit report at https://bugs.php.net/bug.php?id=61325&edit=1
ID: 61325
Comment by: samuel dot hassine at anotherservice dot com
Reported by: Alastair at adewra dot com
Summary: FastCGI keeps dieing
Status: Feedback
Type: Bug
Package: CGI/CLI related
Operating System: CentOS
PHP Version: 5.4.0
Block user comment: N
Private report: N
New Comment:
Hi,
I am experiencing the same problem on Debian testing with :
php5 5.4.0-2
FastCGI PHP processes are unexpectly died.
Best regards.
Sam
Previous Comments:
------------------------------------------------------------------------
[2012-03-26 15:19:59] chlovechek at amis dot net
I am experiencing the exact same problem on Debian Wheezy (PHP 5.4.0-2 and
Lighttpd 1.4.30-1). Bellow is the backtrace from core dump:
#0 zend_llist_add_element (l=0x0, element=0x7fff44c32990) at
/tmp/buildd/php5-5.4.0/Zend/zend_llist.c:39
#1 0x000000000046b9a0 in _php_list_set_error_structure (error=0x6d69,
msg=0x7fff44c32990 "")
at /tmp/buildd/php5-5.4.0/ext/libxml/libxml.c:485
#2 0x00007f01ef3a7103 in __xmlRaiseError (schannel=0x46b9b0
<php_libxml_structured_error_handler>, channel=0, data=0x0, ctx=0x23d61a0,
nod=0x0, domain=5, code=76, level=XML_ERR_ERROR, file=<optimized out>,
line=1, str1=0x23d77e4 "", str2=0x0, str3=0x0, int1=0, col=416,
msg=0x7f01ef48a7e3 "Unexpected end tag : %s\n") at ../../error.c:588
#3 0x00007f01ef3e4018 in htmlParseErr (ctxt=0x23d61a0, error=<optimized out>,
msg=<optimized out>, str1=<optimized out>,
str2=<optimized out>) at ../../HTMLparser.c:114
#4 0x00007f01ef3e73dd in htmlParseEndTag (ctxt=0x23d61a0) at
../../HTMLparser.c:3856
#5 htmlParseEndTag (ctxt=0x23d61a0) at ../../HTMLparser.c:3800
#6 0x00007f01ef3e9480 in htmlParseContentInternal (ctxt=0x23d61a0) at
../../HTMLparser.c:4403
#7 0x00007f01ef3e9fcf in htmlParseDocument__internal_alias (ctxt=0x23d61a0) at
../../HTMLparser.c:4660
#8 0x0000000000498660 in dom_load_html.isra.1 (ht=0, return_value=0x23bbd38,
this_ptr=0x230cd98, mode=0)
at /tmp/buildd/php5-5.4.0/ext/dom/document.c:2195
#9 0x00000000007493a9 in zend_do_fcall_common_helper_SPEC
(execute_data=0x7f01f2157cd0)
at /tmp/buildd/php5-5.4.0/Zend/zend_vm_execute.h:642
#10 0x000000000070340f in execute (op_array=0x23efe50) at
/tmp/buildd/php5-5.4.0/Zend/zend_vm_execute.h:410
#11 0x00000000006a36a0 in zend_execute_scripts (type=0, retval=0x0,
file_count=3) at /tmp/buildd/php5-5.4.0/Zend/zend.c:1272
#12 0x0000000000642f13 in php_execute_script (primary_file=0x0) at
/tmp/buildd/php5-5.4.0/main/main.c:2473
#13 0x0000000000431ae6 in main (argc=32767, argv=0x1) at
/tmp/buildd/php5-5.4.0/sapi/cgi/cgi_main.c:2422
------------------------------------------------------------------------
[2012-03-21 10:42:14] rm at romanrm dot ru
...it worked briefly, but then suddenly stopped with the same symptoms again,
and in I notice that the socket got renamed to "/tmp/php.socket-0-0" this time.
Duh!
------------------------------------------------------------------------
[2012-03-21 10:40:16] rm at romanrm dot ru
In /etc/lighttpd/conf-enabled/15-fastcgi-php.conf
I had to change /tmp/php.socket to /tmp/php.socket-0
and then it worked.
Looks like the new PHP creates the socket under a different name, adding "-0"
to it.
------------------------------------------------------------------------
[2012-03-09 16:09:02] Alastair at adewra dot com
Sorry, i actually ended up downgrading it to 5.3.3 as it was a live server fr
other content and it wasn't a necessity to have it on 5.4.0
Unfortunately, I didnt have core dump set up and when i ran strace, it simply
just hung.
I rebuilt the source several times, and tried to reinstall but it returned the
same error.
I do still have the old php-cgi on my server (but my lighttpd config is
currently
pointing to the 5.3.3 one) in a different directory, and when i run -v on the
5.4.0 it now has excluded the warning.
------------------------------------------------------------------------
[2012-03-09 02:35:53] [email protected]
Hi, plz look into the pwd of php-cgi, check is there any core dump file
generated?
if find one, plz paste the bt here.
thanks
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=61325
--
Edit this bug report at https://bugs.php.net/bug.php?id=61325&edit=1
