On 9 July 2014 02:34, Werner Thie <werner@thieprojects.ch> wrote:
On 7/8/14 6:30 AM, Paul Wiseman wrote:
This is a google compute instance, so there is there firewall on there. I did at first think it could be a hidden firewall rule google have.
I think I can rule anything like that out though. I tried to recreate the problem on another box, and got to the point where i'd set up the entire working environment without the issue (same firewall etc.). A bit puzzled and thinking I'd somehow fixed the issue, I swapped the new box for the live one and once I'd done that I then started to see the exact same problem on the new box. (And the problem had gone away on the ex-live box). So the only thing I can think of is it is somehow being triggered by the traffic.
What's the number of connections when this is occuring?
Werner
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Thank you for the suggestions on this. I did locate the issue in the end - it was unrelated to twisted so sorry about the post! Just incase it could help anyone in the future, the issue was the live traffic did have an extra step of going though a load balancer, which had an idle connection timeout of 60 seconds on it. I was kind of surprised that this closed the data connection as the PASV connection is established directly between the server and client, but I guess when the load balancer kills the initial connection it also stops the data connection some how too.