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

ansible-playbook needs to report on 'dark' hosts #33

Closed
mpdehaan opened this issue Mar 14, 2012 · 1 comment
Closed

ansible-playbook needs to report on 'dark' hosts #33

mpdehaan opened this issue Mar 14, 2012 · 1 comment

Comments

@mpdehaan
Copy link
Contributor

No description provided.

@mpdehaan
Copy link
Contributor Author

done

GustavoHennig pushed a commit to GustavoHennig/ansible that referenced this issue Apr 27, 2017
kihahu pushed a commit to kihahu/ansible that referenced this issue May 16, 2018
toshywoshy pushed a commit to toshywoshy/ansible that referenced this issue Oct 1, 2018
The last time I tested set_nonblock() as a fix for the rsync hang, I
used F_SETFD rather than F_SETFL, which resulted in no error, but also
did not set O_NONBLOCK. Turns out missing O_NONBLOCK was the problem.

The rsync hang was due to every context blocking in os.write() waiting
for either a parent or child buffer to empty, which was exacerbated by
rsync's own pipelining, that allows writes from both sides to proceed
even while reads aren't progressing. The hang was due to os.write() on a
blocking fd blocking until buffer space is available to complete the
write. Partial writes are only supported when O_NONBLOCK is enabled.
@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
pilou- pushed a commit to pilou-/ansible that referenced this issue Aug 26, 2020
pilou- pushed a commit to pilou-/ansible that referenced this issue Aug 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant