Discussion in 'Rebornbuddy Forum' started by mastahg, Aug 26, 2014.
This issue needs to be investigated, profile cannot be used.
The problem did not recur.
Looks like there was an issue with the auth login system, where it was not properly respecting the region and sessions were getting lost. I am still seeing some sessions being reported as missing but the rate is dropping as clients reconnect to the proper region. Still investigating the cause.
This new build contains what I am dubbing NuAuth. If you would like to test NuAuth select the test region in the dropdown at the login prompt or set region 6 in the globalsettings.json
NuAuth is a total rewrite of the auth+offsets+heartbeat back end of rb. Many users were plagued with poor connection stability to the auth service and the auth service was designed with windows server only in mind and has very poor performance.
Right now NuAuth only has one region deployed for it, in the eu, but the response time of the nuauth vs old auth is so much faster that a single server might be sufficient and is part of the feedback im looking for.
@mastahg CN session has expired
Well without a log I can't do anything.
I highly recommend you try switching to the TestAuth on the login screen.
I'm pushing a new build out now as I have discovered a potential exploit that would allow session reusage in the current version. These zombie clients are hammering the auth server and are contributing somewhat to the performance issue.
I still recommend that users use the TestAuth if they are having connectivity issues.
@mastahg UTC/GMT 2022.10.11. 12:00-16:00 Ver.2022.09.28.0000.0000（6.15ver.）
auth service unstable
I'm looking for logs containing "Session reused, terminating" . There seems to be either a bug in base RB or a plugin that is causing clients to open multiple connections to the nav server. I have seen some clients initiating over 45 connections that remain idle never sending requests. I just fixed a bug on the nav server that allowed these ghost sessions to remain connected and they are now actively being purged, this is not ideal as I would rather the clients not establish these ghost connections in the first place.
CN Update ，UTC/GMT 2022.11.15. 12:00-16:00 Ver.2022.11.01.0000.0000（6.18ver.）
CN Update ，UTC/GMT 2022.12.20。12:00-16:00.（6.2ver.Ver.2022.12.07.0000.0000）
As always, thank you for posting this ahead of time.
Separate names with a comma.