Changes between Initial Version and Version 1 of Ticket #502, comment 5
- Timestamp:
- 02/10/14 15:33:52 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #502, comment 5
initial v1 1 1 Hi Valentin. My name is Hongli Lai, CTO at Phusion and lead developer of Phusion Passenger. 2 2 3 I've just helped David with this problem. It turns out that his problem is caused by neither Nginx nor Passenger, but froma TCP rate limiter in the kernel. Once in a while, his port 80 becomes totally unreachable. TCP handshakes don't complete. Even TCP handshakes from localhost don't work. All Nginx processes seem to be working fine, with the Nginx worker blocking on epoll_wait(). However his /var/log/sys contains messages like these:3 I've just helped David with this problem. It turns out that his problem is caused by neither Nginx nor Passenger, but by a TCP rate limiter in the kernel. Once in a while, his port 80 becomes totally unreachable. TCP handshakes don't complete. Even TCP handshakes from localhost don't work. All Nginx processes seem to be working fine, with the Nginx worker blocking on epoll_wait(). However his /var/log/sys contains messages like these: 4 4 5 5 … … 14 14 I'd also like to take this opportunity to comment on the thread you linked to, http://mailman.nginx.org/pipermail/nginx/2013-February/037563.html. In the 5 years that Phusion Passenger has supported Nginx, we've never encountered a problem looks like the one described in 037563.html. It seems that the two people in 037563.html were the only ones who have ever seen the problem, but unfortunately they did not respond to our requests for more information. I was hoping that this time, David's problem would shed more light on the same issue as 037563.html. But it turns out to be false alarm. 15 15 16 I fully understand that you, as an Nginx developer, is not keen on debugging problems caused by external modules. However I'm hoping that in the future you could take a more nuanced position w.r.t. Phusion Passenger, because I don't think that two unconfirmed reports count as "known for introducing strange bugs". There are tens of thousands of Phusion Passenger + Nginx users out there for whom Phusion Passenger works fine, e.g. Pixar, New York Times, Apple, Juniper, etc. Of course, I'm not saying that such bugs don't exist - they *might*.16 I fully understand that you, as an Nginx developer, is not keen on debugging problems caused by external modules. However I'm hoping that in the future you could take a more nuanced position w.r.t. Phusion Passenger, because I don't think that two unconfirmed reports count as "known for introducing strange bugs". There are tens of thousands of Phusion Passenger + Nginx users out there for whom Phusion Passenger works fine, e.g. Pixar, New York Times, Apple, Juniper, etc. There are even Nginx Plus customers. Of course, I'm not saying that such bugs don't exist - they *might*. 17 17 18 18 Unfortunately, the two users in 037563.html got the (wrong) idea that problems were intentionally introduced in the open source version, in favor of the Enterprise version. However, nothing is further from the truth. We take pride in producing high-quality, stable and robust software, regardless of whether we charge for it or not. When it comes to core stability, there are no differences between the open source and Enterprise.
