Closed barryprice closed 1 year ago
This sounds like an upstream issue for the matter most desktop application itself.
This bugtracker is for the snap package. Can you reopen it in the mattermost desktop repo of the mattermost organization?
Thanks!
Thanks, apologies for the noise - filed upstream here:
What happened?
We migrated a production Mattermost instance between data centres earlier today.
During the downtime period we intentionally took both source and target instances offline (so users would receive a 503 error) to avoid skew between the two installations during the sync.
Prior to and during this period, DNS TTL was reduce to 60s.
Once migration was complete, we restored service on the target instance but intentionally kept the source instance offline.
Connecting to the service via web browser worked fine at this point, but trying to use the already-running mattermost-desktop snap just showed 503 errors, confirmed by several users.
We tried logging out and logging in again, but this didn't make any difference.
It appears that the app does a DNS lookup on startup and then caches that result for far longer than expected, possibly indefinitely.
Fully stopping and relaunching the app resolved the problem.
What should have happened?
The app should have noticed that the target IP changed, and attempted to reconnect to the new target.
If not immediately, then certainly at the logout/login step.
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
No response
Teminal output of app
No response