[MCOL-355] Multi-node installation with public IPs on AWS completed, but system would not start Created: 2016-10-11 Updated: 2022-11-05 Resolved: 2022-11-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.0.4 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Minor |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2016-20 |
| Description |
|
Build tested: 1.0.4-1 (build created on Oct 9, 2016) I did a 1UM-2PM installation on AWS. I choose AWS installation option 2 for manually entering IP addresses. After installation is completed, the last step failed to start the system. I also restarted the instances and try to start the system, it hung. |
| Comments |
| Comment by David Hill (Inactive) [ 2016-10-12 ] |
|
I found the issue occurs when the public Ip address are used instead of the Private IP addresses, which is the norm... The issue of the system not coming up. having issue getting a workable debug build, but still wanting to find out what is going on when the publics are used... I can still ping and scp on the public, so its a a strange scenario.. |
| Comment by David Hill (Inactive) [ 2016-10-14 ] |
|
since this is only happening on amazon instances using the unrecommend Public IP addresses and works when they use the recommend private Ip address, the severity of this should be changed... Will continue investigating the issue of using the public, but this is not a blocking MCOL |
| Comment by Todd Stoffel (Inactive) [ 2022-11-05 ] |
|
This item is being closed because it was well passed the expiration date with no activity. If you suspect this was done in error please create a new ticket. |