简体繁体 English

PHP 升级后的 nginx 错误：FastCGI 在 stderr 中发送：“”同时从上游读取响应标头

[英]nginx error after PHP upgrade: FastCGI sent in stderr: " " while reading response header from upstream

原文 2012-08-22 19:31:21 5 1 php/ nginx/ fastcgi

I'm guessing this is due to a PHP upgrade, as I upgraded Apache2 and PHP on my ubuntu server and now nginx is no longer functioning properly.我猜这是由于 PHP 升级，因为我在我的 ubuntu 服务器上升级了 Apache2 和 PHP，现在 nginx 不再正常运行。

I've restarted the nginx process and fast CGI and it's obviously not working properly and states that FastCGI sends a blank message in stderr.我重新启动了 nginx 进程和快速 CGI，它显然无法正常工作，并指出 FastCGI 在 stderr 中发送空白消息。 I'm kind of at a loss on how to continue debugging.我对如何继续调试有点茫然。

Does anyone have any ideas on what step I should take next to debug?有人对我接下来应该采取什么步骤进行调试有任何想法吗？

1 个解决方案

I had a similar problem a few weeks back.几周前我遇到了类似的问题。 turned out to be an issue with permissions.原来是权限问题。 make sure your server root directory, all the files and directories it contains and the entire path to the server root has the correct permissions (don't forget to check the chmod in addition to the ownership).确保您的服务器根目录、它包含的所有文件和目录以及服务器根目录的整个路径都具有正确的权限（除了所有权之外，别忘了检查 chmod）。

错误28105＃0：* 1 stderr发送的FastCGI：从上游读取响应头时“主脚本未知” - error 28105#0: *1 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream

如何调试“FastCGI sent in stderr: Primary script unknown while reading response header from upstream”并找到实际的错误消息？ - How to debug "FastCGI sent in stderr: Primary script unknown while reading response header from upstream" and find the actual error message?

从上游读取响应标头时，在未知的 stderr 主脚本中发送的 FastCGI - FastCGI sent in stderr primary script unknown while reading response header from upstream

从上游读取响应 header 时在 stderr 中发送的 FastCGI：“主脚本未知” - FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream

NGINX FASTCGI / PHP-从上游客户端读取响应头时，主脚本未知 - NGINX FASTCGI/PHP - Primary script unknown while reading response header from upstream, client

Nginx Web 服务器错误 - 从上游读取响应标头时，上游发送的标头太大 - Nginx Web Server Error - upstream sent too big header while reading response header from upstream

上游从客户端，客户端（nginx，清漆）读取响应头时发送了太大的头 - upstream sent too big header while reading response header from upstream, client (nginx, varnish)

连接重置 - 使用 nginx 和 php-fpm7.2 从上游读取响应头时 - Connection reset by peer - while reading response header from upstream using nginx and php-fpm7.2

如何修复上游从上游读取响应头时发送过大的头？ - how to fix upstream sent too big header while reading response header from upstream?

从上游读取响应标头时，上游发送了太大的标头 - upstream sent too big header while reading response header from upstream

暂无

暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 错误28105＃0：* 1 stderr发送的FastCGI：从上游读取响应头时“主脚本未知” - error 28105#0: *1 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream 如何调试“FastCGI sent in stderr: Primary script unknown while reading response header from upstream”并找到实际的错误消息？ - How to debug "FastCGI sent in stderr: Primary script unknown while reading response header from upstream" and find the actual error message? 从上游读取响应标头时，在未知的 stderr 主脚本中发送的 FastCGI - FastCGI sent in stderr primary script unknown while reading response header from upstream 从上游读取响应 header 时在 stderr 中发送的 FastCGI：“主脚本未知” - FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream NGINX FASTCGI / PHP-从上游客户端读取响应头时，主脚本未知 - NGINX FASTCGI/PHP - Primary script unknown while reading response header from upstream, client Nginx Web 服务器错误 - 从上游读取响应标头时，上游发送的标头太大 - Nginx Web Server Error - upstream sent too big header while reading response header from upstream 上游从客户端，客户端（nginx，清漆）读取响应头时发送了太大的头 - upstream sent too big header while reading response header from upstream, client (nginx, varnish) 连接重置 - 使用 nginx 和 php-fpm7.2 从上游读取响应头时 - Connection reset by peer - while reading response header from upstream using nginx and php-fpm7.2 如何修复上游从上游读取响应头时发送过大的头？ - how to fix upstream sent too big header while reading response header from upstream? 从上游读取响应标头时，上游发送了太大的标头 - upstream sent too big header while reading response header from upstream

相关标签

粤ICP备18138465号 © 2020-2024 STACKOOM.COM