[Twisted-Python] FTP box disconnecting after 60 seconds
Hey, This is a bit of a stab in the dark, but I'm really not sure what to try next. Basically I've got a custom twisted FTP server, recently (not sure when it started) I've noticed that connections to it seem to disconnect after 60 seconds if they haven't completed. This could be a slow LIST response, or a large file being transferred in a RETR download. It doesn't seem to matter if the connection is idle or not, but after 60 seconds it seems to get closed. I can't recreate this locally, nor if I clone the live box. I've even set up a new box which didn't exhibit the behaviour, then switched the current live box to the new box and then the behaviour started to occur, only when it went live. So the only thing I can think of is that it happens when multiple users are on the box which makes it very difficult to pin point / recreate. I'm a bit of a loss as to how to try and move this forward and try and work out what the issue is. I just thought I'd ask here incase it sounds like anything someone has run into before? or if anyone has any ideas of where to start looking (it disconnects at 60/61 seconds)? Maybe a timeout value somewhere perhaps? Thanks! Paul
On 08/07/14 15:45, Paul Wiseman wrote:
Hey,
This is a bit of a stab in the dark, but I'm really not sure what to try next.
Basically I've got a custom twisted FTP server, recently (not sure when it started) I've noticed that connections to it seem to disconnect after 60 seconds if they haven't completed. This could be a
Are there any middlebox devices (firewall, NAT) in the path?
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. On 8 July 2014 16:26, Phil Mayers <p.mayers@imperial.ac.uk> wrote:
On 08/07/14 15:45, Paul Wiseman wrote:
Hey,
This is a bit of a stab in the dark, but I'm really not sure what to try next.
Basically I've got a custom twisted FTP server, recently (not sure when it started) I've noticed that connections to it seem to disconnect after 60 seconds if they haven't completed. This could be a
Are there any middlebox devices (firewall, NAT) in the path?
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
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
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.
participants (3)
-
Paul Wiseman -
Phil Mayers -
Werner Thie