php-general Digest 2 Sep 2013 08:57:25 -0000 Issue 8352

Topics (messages 322017 through 322020):

Re: PHP-5.5.2 +opcache segfaults with Piwik
        322017 by: Lester Caine
        322018 by: Jan Ehrhardt
        322019 by: Jan Ehrhardt
        322020 by: Jan Ehrhardt

Administrivia:

To subscribe to the digest, e-mail:
        php-general-digest-subscr...@lists.php.net

To unsubscribe from the digest, e-mail:
        php-general-digest-unsubscr...@lists.php.net

To post to the list, e-mail:
        php-gene...@lists.php.net


----------------------------------------------------------------------
--- Begin Message ---
Grant wrote:
I've tried php-5.5.2 and 5.5.3 but both segfault with piwik unless the
>opcache is disabled.  Someone filed a piwik bug but was told it's a
>php bug:
>
>http://dev.piwik.org/trac/ticket/4093

Is this a known issue?

I'm running my own port of piwik in production with eaccelerator on 5.4 but I've made the decision not to move any of the machines to 5.5 until all of the legacy 5.2 machines have been brought up to 5.4. Not an answer, but explains perhaps why the problem is not being seen by others.

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

--- End Message ---
--- Begin Message ---
Lester Caine in php.general (Sun, 01 Sep 2013 12:59:18 +0100):
>Grant wrote:
>>> >I've tried php-5.5.2 and 5.5.3 but both segfault with piwik unless the
>>> >opcache is disabled.  Someone filed a piwik bug but was told it's a
>>> >php bug:
>>> >
>>> >http://dev.piwik.org/trac/ticket/4093
>
>> Is this a known issue?
>
> (...) Not an answer, but explains perhaps  why the problem is not being
>seen by others.

It is more likely that users do not notice it. I have Piwik running with
PHP 5.3 and php_opcache.dll (Centos 5) and it segfaults:

[Sun Sep 01 17:06:53.131410 2013] [core:notice] [pid 25411] AH00052:
child pid 25451 exit signal Segmentation fault (11)
[Sun Sep 01 17:08:18.561917 2013] [core:notice] [pid 25411] AH00052:
child pid 25453 exit signal Segmentation fault (11)
[Sun Sep 01 17:08:19.569714 2013] [core:notice] [pid 25411] AH00052:
child pid 25450 exit signal Segmentation fault (11)

However, nothing special is displaying on the page. You have to grep
your Apache error_log to know that it happens. How did you notice?

Jan

--- End Message ---
--- Begin Message ---
Grant in php.general (Sun, 1 Sep 2013 02:13:54 -0700):
>> I've tried php-5.5.2 and 5.5.3 but both segfault with piwik unless the
>> opcache is disabled.  Someone filed a piwik bug but was told it's a
>> php bug:
>>
>> http://dev.piwik.org/trac/ticket/4093
>
>Is this a known issue?

I changed the PHP on my (dev) Centos5 server to PHP 5.5.3, pulled the
latest OPcache from Github and tried to get a segfault. That was clearly
visible when I tried to access the Goals tab in the dashboard of one of
my websites. The page never got further than 'Loading data...' and my
Apache log showed a segfault.

So, if it was no known issue it is confirmed now.

Jan

--- End Message ---
--- Begin Message ---
Grant in php.general (Sun, 25 Aug 2013 02:31:29 -0700):
>I've tried php-5.5.2 and 5.5.3 but both segfault with piwik unless the
>opcache is disabled.  Someone filed a piwik bug but was told it's a
>php bug:
>
>http://dev.piwik.org/trac/ticket/4093

Could you try to add a function_exists check to
libs/upgradephp/upgrade.php?

This at the function declaration of _json_encode:
if (!function_exists('_json_encode')) { function _json_encode($var, ...

And a extra } at the end.

This seemed to correct this fatal error on my side:

[02-Sep-2013 10:35:40 Europe/Paris] PHP Fatal error:  Cannot redeclare
_json_encode() (previously declared in
/usr/local/lib/php/share/piwik/libs/upgradephp/upgrade.php:109) in
/usr/local/lib/php/share/piwik/libs/upgradephp/upgrade.php on line 109

I do not know what opcache has to do with it, although I suspect that
Piwik is calling itself a lot of times and that opcache is trailing
behind (or something like that).

Jan

--- End Message ---

Reply via email to