Code@ Questions have Moved!

In an effort to streamline our efforts, Code@ has moved the Questions and Answers section to the Salesforce StackExchange site, which you can find at the following url: Please be sure to TAG YOUR QUESTIONS with exacttarget, so our partners know specifically what application your question is pertaining to, and our experts can provide you with a more timely response.

We will discontinue support for this section, and will only be monitoring questions at that location. If your question is currently unanswered, feel free to post that same question on StackExchange to the broader community.

Thank you for your understanding!

Home / question / Segmentation fault when using PHP starter kit code
Ask A Question

Segmentation fault when using PHP starter kit code

0 points
russbackfuel's picture


We have a PHP-based API integration working and tested on development and staging servers, but on the client's production server, the following line of code:

$response = $this->client->Create($request);

Throws a fatal segmentation fault:

child pid 30099 exit signal Segmentation fault (11)

Can you suggest why this may be caused? The server is running PHP v5.3.3 and we are using code from the PHP starter kit.

One thing I noticed is that on you mention that nusoap classes should be included but there is no reference to this in the PHP starter kit.

I have raised a case via 3Sixty but they suggested I post here. The code is available under case #00802717.


Product Group: 


3720 points
jmeketa's picture

Segmentation Fault is generic so I have to make some guesses with one line of code to go off of.

Assuming that:
$response = $this->client->Create($request);
is actually
$response = $this->client->Create($request);

and the fact it worked in the non production environments here are my guesses of things to check:

1. Internet Connectivity for server on port 80 and 443 (HTTPS) on the prod server. Both are required. As well as making sure no firewall or proxy issues with the specific Service.asmx location used in web service calls.

2. Make sure all config files and PHP code match from other systems and that you are not missing something required for the client object to be setup correctly.

3. Check for PHP version for differences on machines as well as Apache or whatever is hosting.

4. If your prod is using a different ET account check that the ET client is on the same server stack as your test ET account and that the API user credentials have API access and enough permissions to perform the call. The ET user credentials must match the correct web services end point (Service.asmx) from the list in the page linked below.

Jason Meketa