# Random ssh error when fork above 2 even 1 - Unreachable hosts

**URL:** <https://forum.ansible.com/t/random-ssh-error-when-fork-above-2-even-1-unreachable-hosts/35832>\
**Category:** Ansible Project\
**Created:** [October 7, 2021, 6:31pm UTC](https://forum.ansible.com/t/random-ssh-error-when-fork-above-2-even-1-unreachable-hosts/35832 "2021-10-07T18:31:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anil\_Dursun](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@Anil\_Dursun](https://forum.ansible.com/u/Anil_Dursun)\
**Post date:** [October 7, 2021, 6:31pm UTC](https://forum.ansible.com/t/random-ssh-error-when-fork-above-2-even-1-unreachable-hosts/35832/1 "2021-10-07T18:31:38Z")

</div>

Hello,

I’m having random ssh fails with default fork=5.  
I realized it could be solved with fork=1 (not even 2 to be sure).

I’m running playbooks that  
create dirs,  
copy a shell script (can take some time to complete)  
execute it (i don’t remember why I do it with shell module and not with script)  
fetch output  
delete the script and output file

Why in this environment even fork=2 is problematic? On what it depends?

I saw

grep -i MaxStart /etc/ssh/sshd\_config

I can’t access this value right now and I’d really want to have your opinion.

Thanks in advance.