Closed jennifer-richards closed 6 years ago
The expiration time issue is addressed by 536646258cdf77d28015493c460022e6a239b4f3
Not currently seeing the connected to/from or last_connection issues. However, the TR clearly does not seem to be noticing when a peer disconnects.
I think all but the APCs for remote realms not being shown has been resolved.
The system currently copies the "apcs" list for a community update into the "apcs" list for a realm that is created as a result of the update. However, if the community itself was an APC, that list is empty. If the incoming community is an APC, any realms created by the update should be created with that community as its APC.
The last bit should be fixed by #74.
trmon [...] show realms
and verify that an APC is defined for every realmtrmon [...] show communities
and verify that the expiration times for remote realms appear as future UTC timestrmon [...] show routes
and verify that the expiration times for remote routes appear as future UTC timestrmon [...] show peers
and verify that each peer's connected_to
, connected_from
, and last_connection_attempt
fields are accurate and that the latter is shown in a past UTC timeAs described in the steps above
Verified!
show peers