SSH timeout and [Errno None] Unable to connect to port 22 on AWS EC2 about flintrock

[nchammas]

SSH timeouts are normal for a brief period while the instances are still coming online.

If you just wait a few minutes, do the timeouts persist or does the setup eventually continue?

[satendrakumar]

@nchammas thanks for replay.

After timeout. it is throwing Error:

2022-05-24 20:54:47,131 - flintrock.ssh       - DEBUG - [52.201.***.***] SSH AuthenticationException.
2022-05-24 20:54:54,041 - flintrock.ssh       - DEBUG - [52.201.***.***] SSH AuthenticationException.
2022-05-24 20:55:01,017 - flintrock.ssh       - DEBUG - [52.201.***.***]  SSH AuthenticationException.
2022-05-24 20:55:07,881 - flintrock.ssh       - DEBUG - [52.201.***.***]SSH AuthenticationException.
2022-05-24 20:55:14,781 - flintrock.ssh       - DEBUG - [52.201.***.***] SSH AuthenticationException.
Exception: Error reading SSH protocol banner
Traceback (most recent call last):
  File "/home/satendra/decooda/NH-AWS/env/lib/python3.8/site-packages/paramiko/transport.py", line 2211, in _check_banner
    buf = self.packetizer.readline(timeout)
  File "/home/satendra/decooda/NH-AWS/env/lib/python3.8/site-packages/paramiko/packet.py", line 380, in readline
    buf += self._read_timeout(timeout)
  File "/home/satendra/decooda/NH-AWS/env/lib/python3.8/site-packages/paramiko/packet.py", line 609, in _read_timeout
    raise EOFError()
EOFError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/satendra/decooda/NH-AWS/env/lib/python3.8/site-packages/paramiko/transport.py", line 2039, in run
    self._check_banner()
  File "/home/satendra/decooda/NH-AWS/env/lib/python3.8/site-packages/paramiko/transport.py", line 2215, in _check_banner
    raise SSHException(
paramiko.ssh_exception.SSHException: Error reading SSH protocol banner

Do you want to terminate the 2 instances created by this operation? [Y/n]: Y
Terminating instances...
52.201.***.***] SSH protocol error. Possible causes include using the wrong key file or username.

[nchammas]

SSH is working from my local machine. I tested using same pem file but cluster setup is failin with timeout.

You used the same pem file in your SSH test, but did you use the same username as in your Flintrock config?

[satendrakumar]

@nchammas yes, User name was same ec2-user

[nchammas]

That's weird. Can you show me all the properties of the instance you are able to SSH into? Are the subnet, security group, VPC, and AMI all the same as in your Flintrock config? Please share also the full SSH command that is working for you.

[satendrakumar]

@nchammas I found the issue. I was using key name in upper camel case(SparkStack.pem). That was not working with flintrock. It works for SSH.

I created new key pair called spark_stack.pem. It is working. Thank you so much for help.