[MCOL-375] AMI 1.0.4-1 - ssh connection refused error occurred for newly created instance Created: 2016-10-24 Updated: 2016-12-02 Resolved: 2016-12-02 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.0.4 |
| Fix Version/s: | 1.0.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lee (Inactive) | Assignee: | David Hill (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2016-23 |
| Description |
|
Build tested: 1.0.4-1AMI For AWS installatoin for a 1UM2PM configuration, postConfigure creates the instances for UM1 and PM2, then continue on connecting to the two instances for further installation. At the time of connection, sshd seems to be not yet ready and a “connection refused” occurred. Installation failed. I reran postConfigure (this time, with the instances up and running already), installation was successful. I think we need to account for the fact that sshd will take time to come up on a new instances. |
| Comments |
| Comment by David Hill (Inactive) [ 2016-10-24 ] |
|
There is already retry and wait login in the ssh connection... maybe the time we are waiting needs to be bumped... I will look into that.. |
| Comment by David Hill (Inactive) [ 2016-12-02 ] |
|
There is already a timeout wait of 5 minutes for an instance come up where it can be ssh into. This is plenty of time... In my experience in the past, when you cant log into an instance after 5 minutes, it is a bad instance and should be removed and terminated. Then re-added. So no code change is needed, this is already covered |