blocks|key|1083939|text|出现502错误是因为nginx无法切换到php5-cgi。您可以尝试重新配置php5-cgi以使用unix套接字，而不是tcp。然后调整服务器配置，使其指向套接字，而不是tcp+...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1083940|ps+auxww+%7C+grep+php5-cgi+#--+is+the+process+running?++
netstat+-an+%7C+grep+9000+#+is+the+port+open?+|code-block|syntax|javascript|1083941|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The 502 error appears because nginx cannot hand off to php5-cgi. You can try reconfiguring php5-cgi to use unix sockets as opposed to tcp .. then adjust the server config to point to the socket instead of the tcp ... 

<pre><code>ps auxww | grep php5-cgi #-- is the process running? 
netstat -an | grep 9000 # is the port open? 
</code></pre>

blocks|key|1084188|text|转到/etc/php5/fpm/pool.d/www.conf，如果您正在使用套接字或此行未注释|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1084189|listen+=+/var/run/php5-fpm.sock|code-block|syntax|javascript|1084190|还设置了几个其他值：-|1084191|listen.owner+=+www-data
listen.group+=+www-data
listen.mode+=+0660|1084192|不要忘记重新启动php-fpm和nginx。确保使用相同的nginx所有者和组名称。|1084193|entityMap^0|2|T|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

Go to <code>/etc/php5/fpm/pool.d/www.conf</code> and if you are using sockets or this line is uncommented 

<pre><code>listen = /var/run/php5-fpm.sock
</code></pre>

Set couple of other values too:-

<pre><code>listen.owner = www-data
listen.group = www-data
listen.mode = 0660
</code></pre>

Don't forget to restart php-fpm and nginx. Make sure you are using the same nginx owner and group name.

blocks|key|1084267|text|您必须匹配PHP-FPM和Nginx的设置才能通过套接字或TCP进行通信。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084268|因此，请转到/etc/php5/fpm/pool.d/www.conf并查找这一行：|offset|length|style|CODE|1084269|listen+=+/var/run/php5-fpm.sock|code-block|syntax|javascript|1084270|然后转到/etc/nginx/nginx.conf|1084271|查找以下内容：|1084272|upstream+php+{
++++server+unix:/var/run/php5-fpm.socket;
}|1084273|匹配这些值，您应该都设置好了。|1084274|entityMap^0|0|6|T|0|0|4|L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|15|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

You have to match the settings for PHP-FPM and Nginx to communicate over sockets or TCP. 

So go to <code>/etc/php5/fpm/pool.d/www.conf</code> and look for this line:

<pre><code>listen = /var/run/php5-fpm.sock
</code></pre>

Then go to <code>/etc/nginx/nginx.conf</code>

Look for this: 

<pre><code>upstream php {
 server unix:/var/run/php5-fpm.socket;
}
</code></pre>

Match those values and you should be all set.

blocks|key|1084125|text|变化|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084126|fastcgi_pass++++unix:/var/run/php-fpm.sock;|code-block|syntax|javascript|1084127|至|1084128|fastcgi_pass++++unix:/var/run/php5-fpm.sock;|1084129|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

change

<pre><code>fastcgi_pass unix:/var/run/php-fpm.sock;
</code></pre>

to

<pre><code>fastcgi_pass unix:/var/run/php5-fpm.sock;
</code></pre>

blocks|key|1084059|text|当我执行sudo+/etc/init.d/php-fpm+start时，我得到了以下错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1084060|Starting+php-fpm:+[28-Mar-2013+16:18:16]+ERROR:+[pool+www]+cannot+get+uid+for+user+'apache'|code-block|syntax|javascript|1084061|我猜/etc/php-fpm.d/www.conf需要知道运行when服务器的用户身份，并假设它是apache，而对于nginx，它实际上是nginx，并且需要更改。|1084062|entityMap^0|4|U|0|0|2|N|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

When I did <code>sudo /etc/init.d/php-fpm start</code> I got the following error:

<pre><code>Starting php-fpm: [28-Mar-2013 16:18:16] ERROR: [pool www] cannot get uid for user 'apache'
</code></pre>

I guess <code>/etc/php-fpm.d/www.conf</code> needs to know the user that the webserver is running as and assumes it's apache when, for nginx, it's actually nginx, and needs to be changed.

blocks|key|1084087|text|您可以使用以下命令让nginx忽略客户端中止：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084088|location+/+{
++proxy_ignore_client_abort+on;
}|code-block|syntax|javascript|1084089|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can make nginx ignore client aborts using:

<pre><code>location / {
 proxy_ignore_client_abort on;
}
</code></pre>

blocks|key|869678|text|我在设置Ubuntu服务器时也遇到了同样的问题。原来我的问题是由于套接字文件的不正确权限造成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|869679|如果由于权限问题而出现此问题，可以取消注释以下行:+/etc/php5/fpm/pool.d/www.conf|869680|listen.owner+=+www-data
listen.group+=+www-data
listen.mode+=+0660|code-block|syntax|javascript|869681|或者，尽管我不推荐，但您可以使用以下命令为所有组授予读写权限。|869682|sudo+chmod+go%2Brw+/var/run/php5-fpm.sock|869683|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had the same problem while setting up an Ubuntu server. Turns out I was having the problem due to incorrect permissions on socket file.

If you are having the problem due to a permission problem, you can uncomment the following lines from: /etc/php5/fpm/pool.d/www.conf

<pre><code>listen.owner = www-data
listen.group = www-data
listen.mode = 0660
</code></pre>

Alternatively, although I wouldn't recommend, you can give read and write permissions to all groups by using the following command.

<pre><code>sudo chmod go+rw /var/run/php5-fpm.sock
</code></pre>

blocks|key|1084324|text|尝试禁用xcache或apc模块。在某些版本中，将对象保存到会话变量似乎会导致问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084325|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try disabling the xcache or apc modules. Seems to cause a problem with some versions are saving objects to a session variable.

blocks|key|869592|text|希望这篇小贴士能拯救别人的生命。在我的例子中，问题是我耗尽了内存，但只是轻微的，很难考虑它。在这上面浪费了3个小时。我建议你运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|869593|sudo+htop|code-block|syntax|javascript|869594|或|869595|sudo+free+-m|869596|...along在服务器上运行有问题的请求，以查看您的内存是否没有用完。如果它和我的例子一样，你需要创建一个交换文件(除非你已经有了一个)。|869597|我按照这个教程在Ubuntu+Server14.04上创建了交换文件，它工作得很好：http://www.cyberciti.biz/faq/ubuntu-linux-create-add-swap-file/|offset|length|869598|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cyberciti.biz/faq/ubuntu-linux-create-add-swap-file/^0|0|0|0|0|0|16|1R|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Hope this tip will save someone else's life. In my case the problem was that I ran out of memory, but only slightly, was hard to think about it. Wasted 3hrs on that. I recommend running:

<pre><code>sudo htop
</code></pre>

or

<pre><code>sudo free -m
</code></pre>

...along with running problematic requests on the server to see if your memory doesn't run out. And if it does like in my case, you need to create a swap file (unless you already have one).

I have followed this tutorial to create swap file on Ubuntu Server 14.04 and it worked just fine:
<a href="http://www.cyberciti.biz/faq/ubuntu-linux-create-add-swap-file/" rel="nofollow">http://www.cyberciti.biz/faq/ubuntu-linux-create-add-swap-file/</a>

blocks|key|1084529|text|如果你使用的是Ubuntu，而上述所有的问题都让你失望了，那么AppArmor很可能是罪魁祸首。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1084530|下面是如何修复它的一个很好的指南：https://www.digitalocean.com/community/tutorials/how-to-create-an-apparmor-profile-for-nginx-on-ubuntu-14-04|offset|length|1084531|长话短说：|1084532|vi+/etc/apparmor.d/nginx|code-block|syntax|javascript|1084533|或|1084534|sudo+aa-complain+nginx
sudo+service+nginx+restart|1084535|看到一切都运行得很好..。然后|1084536|sudo+aa-logprof|1084537|我仍然有问题的Nginx不能读取error.log，即使它有所有可能的权限，包括在Apparomor。我猜这与条目的顺序有关，或者与Passenger或PHP-Fpm的某些交互有关……我已经没有时间来解决这个问题了，现在已经回到了Apache。(Apache的表现也要好得多，仅供参考)|1084538|如果你只是删除配置文件，AppArmor会让Nginx做任何它想做的事情：|1084539|+rm+/etc/apparmor.d/nginx
+service+apparmor+reload|1084540|令人震惊但并不令人惊讶的是，许多关于修复Nginx错误的帖子求助于完全禁用SELinux或删除AppArmor。这是一个糟糕的想法，因为你失去了对大量软件的保护。删除Nginx配置文件是排除配置文件故障的更好方法。一旦你知道问题不在你的Nginx配置文件中，你可以花时间创建一个合适的AppArmor配置文件。|1084541|如果没有AppArmor配置文件，特别是如果你也运行Passenger之类的东西，我给你的服务器大约一个月的时间来恢复。|1084542|entityMap|0|LINK|mutability|MUTABLE|url|https://www.digitalocean.com/community/tutorials/how-to-create-an-apparmor-profile-for-nginx-on-ubuntu-14-04^0|0|H|30|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|F|3|G|5|6|7|1H|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1I|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1J|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1K|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1L|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1M|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1N|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|J|7|1P|8|@]|9|@]|A|$K|L]]|$1|10|3|11|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1R|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]]]

If you're on Ubuntu, and all of the above has failed you, AppArmor is most likely to blame. 

Here is a good guide how to fix it: <a href="https://www.digitalocean.com/community/tutorials/how-to-create-an-apparmor-profile-for-nginx-on-ubuntu-14-04" rel="nofollow noreferrer">https://www.digitalocean.com/community/tutorials/how-to-create-an-apparmor-profile-for-nginx-on-ubuntu-14-04</a>

Long story short: 

<pre><code>vi /etc/apparmor.d/nginx
</code></pre>

Or 

<pre><code>sudo aa-complain nginx
sudo service nginx restart
</code></pre>

See everything working nicely... then

<pre><code>sudo aa-logprof
</code></pre>

I still had problems with Nginx not being able to read error.log, even though it had all the permissions possible, including in Apparomor. I'm guessing it's got something to do with the order of the entries, or some interaction with Passenger or PHP-Fpm... I've run out of time to troubleshoot this and have gone back to Apache for now. (Apache performs much better too FYI.) 

AppArmor just lets Nginx do whatever it wants if you just remove the profile:

<pre><code> rm /etc/apparmor.d/nginx
 service apparmor reload
</code></pre>

Shockingly, but hardly surprising, a lot of posts on fixing Nginx errors resorts to completely disabling SELinux or removing AppArmor. That's a bad idea because you lose protection from a whole lot of software. Just removing the Nginx profile is a better way to troubleshoot your config files. Once you know that the problem isn't in your Nginx config files, you can take the time to create a proper AppArmor profile. 

Without an AppArmor profile, especially if you run something like Passenger too, I give your server about a month to get backdoored.

blocks|key|1083995|text|类似的设置，看起来只是我代码中的一个bug。在我的应用程序开始时，我查找了令人不快的网址，结果成功了：echo+'<html>test</html>';+exit();|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1083996|在我的例子中，问题是一个未初始化的变量，只有在特殊情况下才会失败。|1083997|entityMap^0|1F|X|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Similar setup here and looks like it was just a bug in my code. At the start of my app I looked for the offending URL and this worked: <code>echo '&lt;html&gt;test&lt;/html&gt;'; exit();</code> 

In my case, turns out the problem was an uninitialized variable that only failed under peculiar circumstances.

I get a 502 Bad Gateway with nginx when using spawn fcgi to spawn php5-cgi.

I use this to span an instance on server start using the following line in rc.local

<pre><code>/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -g www-data -f /usr/bin/php5-cgi -P /var/run/fastcgi-php.pid
</code></pre>

presumably I'm getting the error because the spawn-fcgi / php5-cgi dies and there is nothing listening there anymore to parse php.

I get nothing in the logs that I can see anywhere, I'm out of ideas (and new to this setup with nginx)

nginx 502 bad gateway

当我使用spawn fcgi生成php5-cgi时，我得到了一个502 Bad Gateway with nginx。我使用rc.local中的以下行在server start上使用它来跨越一个实例/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -g www-data -f /usr/bin/php5-cgi -P /var/run/fas

问nginx 502坏网关
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问nginx 502坏网关EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问nginx 502坏网关
EN