-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad packet length #442
Comments
Are there any other differences between those two cases? Configs or other fabfile related data differing, different network path, etc? Otherwise, this is new to me, I'd be curious if you can reproduce it with older Paramiko versions. For example it might be due to the changes in #372 (released in 1.15.0) so if you can try 1.14.x or 1.13.x, that'd be a great start. |
There's really nothing different about the servers. They're basically identical. Probably different subnets, but nothing more than that. This actually worked fine at some point too, so I'm not really sure what started causing this. Also confirmed the issue happens both in 1.14.x and 1.13.x, as well as Fabric 1.9.1 and 1.8.5. It's also not something that's local to my system as it happens both on our build server as well as my local OS X machine. If it helps the code looks like this:
With some of the execute tasks being @parallel and some not, and specifically the one it fails on being @serial. The runs_once stuff isn't the built-in code but that shouldn't matter. In this case, the "bar" command doesnt actually run as the node isnt in the list of roles and the command it fails on is "baz" When I removed @serial on it it actually worked fine (I switched it to @parallel), so maybe it's a bug in Fabric somehow? As a shitty workaround I'm going to @parallel(pool_size=1) |
If that parallel trick works I suspect state shenanigans, since moving to parallel should be recreating the connection/client (vs serial, where it caches a single Paramiko client object and reuses it - which normally works fine but if something is getting hinky at some point...). I bet you'd see the same 'it suddenly works now' if you went back to the This would prove that something odd is going on re: the client object inside If you can share what |
Hitting this with current (master) of Fabric + paramiko.
Not sure what details are useful, but we're using a gateway, and this reproduces itself under a specific case 100% of the time.
Strangely, it only happens on this case (a push to a staging node) and not others (i.e. our production push).
From the Fabric side of things this is a run command:
The text was updated successfully, but these errors were encountered: