<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PHP segfault in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726915#M5522</link>
    <description>&lt;P&gt;Hi Kyle,&lt;/P&gt;

&lt;P&gt;Got it, thank you.&lt;/P&gt;
&lt;P&gt;So, you have already seen this issue with IonCube, but this is not supported at the moment. Is that correct? So, this is kind of extected behavior or known issue.&lt;/P&gt;

&lt;P&gt;Is there any hint when will be this supported?&lt;/P&gt;

&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Sandor&lt;/P&gt;</description>
    <pubDate>Mon, 04 Feb 2019 16:55:49 GMT</pubDate>
    <dc:creator>Sandor_Bihary</dc:creator>
    <dc:date>2019-02-04T16:55:49Z</dc:date>
    <item>
      <title>PHP segfault</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726913#M5520</link>
      <description>&lt;P&gt;Hi All!&lt;/P&gt;

&lt;P&gt;We are facing with an issue using the PHP agent on our application.&lt;/P&gt;

&lt;P&gt;After we installed the agent we are getting Segmentation fault (11) errors. After we disabled the agent this error did not occure again.&lt;/P&gt;

&lt;P&gt;Has anyone seen similar before? Is there any fix for this?&lt;/P&gt;

&lt;P&gt;This is the error message:&lt;/P&gt;

&lt;PRE&gt;[Sat Feb 02 08:57:49.488042 2019] [core:notice] [pid 2053] AH00051: child pid 16769 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Sat Feb 02 08:57:53.491981 2019] [core:notice] [pid 2053] AH00051: child pid 2220 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Sat Feb 02 08:57:57.495323 2019] [core:notice] [pid 2053] AH00051: child pid 2117 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Sat Feb 02 08:57:57.495453 2019] [core:notice] [pid 2053] AH00051: child pid 25962 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Sat Feb 02 08:58:03.499494 2019] [core:notice] [pid 2053] AH00051: child pid 2286 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Sat Feb 02 08:58:08.503125 2019] [core:notice] [pid 2053] AH00051: child pid 2092 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Sat Feb 02 08:58:08.503232 2019] [core:notice] [pid 2053] AH00051: child pid 2276 exit signal Segmentation fault (11), possible coredump in /etc/apache2
&lt;/PRE&gt;
&lt;P&gt;The information about the system:&lt;/P&gt;
&lt;PRE&gt;Appdynamics version: AppDynamics Controller build 4.5.5.10390&lt;BR /&gt;kernel: 
Linux eu2 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
OS:
Ubuntu 14.04.5 LTS

apache:
Server version: Apache/2.4.7 (Ubuntu)
Server built:   Jul 15 2016 15:34:04

php:
PHP 5.5.9-1ubuntu4.22 (cli) (built: Aug  4 2017 19:40:28) 
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
    with the ionCube PHP Loader + Intrusion Protection from ioncube24.com (disabled) v5.0.7, Copyright (c) 2002-2015, by ionCube Ltd.
    with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
&lt;/PRE&gt;</description>
      <pubDate>Sat, 02 Feb 2019 13:23:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726913#M5520</guid>
      <dc:creator>Sandor_Bihary</dc:creator>
      <dc:date>2019-02-02T13:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: PHP segfault</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726914#M5521</link>
      <description>&lt;P&gt;Hi Sandor,&lt;/P&gt;

&lt;P&gt;Unfortunately we don't yet support the ionCube loader module. I suspect these crashes are due to that module being used, as we've experienced in the past.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 16:50:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726914#M5521</guid>
      <dc:creator>Kyle_Furlong</dc:creator>
      <dc:date>2019-02-04T16:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: PHP segfault</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726915#M5522</link>
      <description>&lt;P&gt;Hi Kyle,&lt;/P&gt;

&lt;P&gt;Got it, thank you.&lt;/P&gt;
&lt;P&gt;So, you have already seen this issue with IonCube, but this is not supported at the moment. Is that correct? So, this is kind of extected behavior or known issue.&lt;/P&gt;

&lt;P&gt;Is there any hint when will be this supported?&lt;/P&gt;

&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Sandor&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 16:55:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726915#M5522</guid>
      <dc:creator>Sandor_Bihary</dc:creator>
      <dc:date>2019-02-04T16:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: PHP segfault</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726916#M5523</link>
      <description>&lt;P&gt;Hi Sandor,&lt;/P&gt;

&lt;P&gt;Yes, this is expected with ionCube loader. I don't yet have a timeline for this support.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 16:57:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/PHP-segfault/m-p/726916#M5523</guid>
      <dc:creator>Kyle_Furlong</dc:creator>
      <dc:date>2019-02-04T16:57:03Z</dc:date>
    </item>
  </channel>
</rss>

