-
Notifications
You must be signed in to change notification settings - Fork 20
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
Each target works using individual passhport access but randomly fails while using ansible #559
Comments
Mmmm i'll try that on my side with your pro-tip you sent on another thread. Stay tuned… |
around 90 targets, sometimes happen on the 5/6 first targets sometimes not. Thanks |
Hi, |
Hi, No it's not. This is basically the default passhport setup wrote through an ansible playbook |
Haven't had the time to reproduce yet, but @elg is right, it might come from the embedded server in flask which is very limited. You should definitely try this : https://docs.passhport.org/en/latest/installation-and-configuration/apache-wsgi-for-production.html |
While trying to "ansible ping" every target, I get random erros and did not see anything relevant in sshd debug logs.
The same targets works perfectly while using passhport menu.
I can run my test several times and I never get the same amount of failed targets nor related targets.
Already tried to set sshd maxsession to higher value and did check ulimit.
Thank you,
UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: kex_exchange_identification: Connection closed by remote host",
"unreachable": true
SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o 'ProxyCommand=ssh -t -W %h:%p -q -p xxxx passhport@xxxxxxxxxx' -o ControlPath=/home/xx/.ansible/cp/0176122d91 ipaddress '/bin/sh -c '"'"'echo ~root && sleep 0'"'"''
(255, '', 'kex_exchange_identification: Connection closed by remote host\r\n')
The text was updated successfully, but these errors were encountered: