nginx:502坏网关与Curl/https在Mac OS X上

Question

我不明白为什么每次尝试使用curl:时我的nginx都会崩溃

再现崩溃的代码片段：

$request = new BuzzMessageRequest('GET', '/', 'https://google.com');
$response = new BuzzMessageResponse();
$client = new BuzzClientCurl();
$client->send($request, $response);

应用程序日志

2015/12/29 11:42:30 [error] 213#0: *416 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: dev-fr.local.xxxx.com, request: "GET /login/check-vkontakte?code=xxxxx HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "dev-ru.local.xxxx.com", referrer: "https://dev-ru.local.xxxx.com/"

/var/log/system.log

Dec 29 11:40:54 Alains-MacBook-Pro.local ReportCrash[75875]: Saved crash report for php-fpm[75864] version 0 to /Users/alain/Library/Logs/DiagnosticReports/php-fpm_2015-12-29-114054_Alains-MacBook-Pro.crash

崩溃报告（开始）

Process:               php-fpm [75865]
Path:                  /usr/local/Cellar/php56/5.6.15/sbin/php-fpm
Identifier:            php-fpm
Version:               0
Code Type:             X86-64 (Native)
Parent Process:        php-fpm [75858]
Responsible:           php-fpm [75858]
User ID:               501
Date/Time:             2015-12-29 11:42:30.733 +0100
OS Version:            Mac OS X 10.10.5 (14F1021)
Report Version:        11
Anonymous UUID:        1DC6CEB0-0479-4A5E-FFD2-E48BA3961196
Sleep/Wake UUID:       A704AF01-8AE8-44D2-BBF3-DED65D834B0B
Time Awake Since Boot: 29000 seconds
Time Since Wake:       3000 seconds
Crashed Thread:        0  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000110

我找了好几个小时，总是放弃，但现在我累了，真的想修复它。

完整的故障报告：http://ninsuo.com/crash-nginx-xxxx.html

我的phpinfo（）：http://ninsuo.com/phpinfo-xxxx.html

Answer 1

更好的做法是使用重新安装php

brew install --with-fpm --with-homebrew-curl --with-homebrew-openssl --with-imap --with-homebrew-libxslt --without-snmp php56

然后用重新安装curl

brew install --with-openssl curl

Answer 2

我很早就遇到了同样的问题，并通过以root身份运行php-fpm解决了这个问题。此外，我还发现了证实这个解决方案的链接：第一个链接，第二个链接。希望它也能帮助你。