|
Viewing Issue Advanced Details
[ Jump to Notes ]
|
[ View Simple ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0005209 |
[Resin] |
minor |
always |
09-06-12 10:40 |
09-08-14 17:45 |
|
|
Reporter |
rickHigh |
View Status |
public |
|
|
Assigned To |
ferg |
|
Priority |
normal |
Resolution |
no change required |
Platform |
|
|
Status |
closed |
|
OS |
|
|
Projection |
none |
|
OS Version |
|
|
ETA |
none |
Fixed in Version |
|
Product Version |
4.0.31 |
| |
Product Build |
|
|
|
Summary |
0005209: Problem with admin when bringing up three triad servers (and only one triad member is up) |
|
Description |
This occurred twice while testing the triad setup on Amazon EC2.
I had three triad servers configured correctly to talk to each other using ext:
When brining up one of three servers, I was not able to get into the /resin-admin.
Logging into /resin-admin just hangs. After bringing up the other two servers, I am able to log into /resin-admin. It appears that there is some call in /resin-admin where it tries to contact the other servers and gets stuck.
I have seen this happen three times. I have not diagnosed it further.
It seems to be fairly reproducible. I am digging into something else and will circle back to this to get logs. |
|
Steps To Reproduce |
|
|
Additional Information |
|
|
|
Attached Files |
|
|
|
Relationships 
