Skip to content
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

"Read from socket failed: Resource temporarily unavailable" on ssh connection #8

Open
Hubbitus opened this issue Aug 18, 2014 · 4 comments

Comments

@Hubbitus
Copy link
Contributor

Please look at https://bugzilla.redhat.com/show_bug.cgi?id=1023559 for details.

@lepennec
Copy link

adding both a download limit with -d and an upload limit with -u seems to solve the issue.

@Hubbitus
Copy link
Contributor Author

Thanks for the workaround. I'm doubt meantime it is normal behaviour.

@bjodah
Copy link

bjodah commented May 4, 2019

I just ran into this using trickle on FreeBSD 12, what didn't work:

$ trickle -s -u 5000 ssh myremoteserver
Fssh_ssh_dispatch_run_fatal: Connection to 256.256.256.256 port 2222: Resource temporarily unavailable

what did work:

$ trickle -s -u 5000 -d 5000 ssh myremoteserver

Thank you @lepennec !

@summetj
Copy link

summetj commented Jul 27, 2022

I can confirm the same issue on Ubuntu 22.04.

Using -d 1500 only gives the Resource temporarily unavailable error, but adding in a -u 1500 as well makes things work correctly. [This is a workaround.....previously, I only needed to specify the download speed limit....]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants