Waiting on Data for New Telon

[theFoof]

[quote="jimbo"]John - have just pretty much confirmed what you said - I created a new char (I know I only have one now since you cleared all mine) Logged straight in after creation and it seemed fine. Logged out - then pretty much logged in again - and got waiting on data - server was hung at that stage. Restarted server - logged in client - no problems. Logged out - waiting until approx 60 secs after start of Chunk shutdown notice - got in fine. Repeated this (i.e waited until after chunk shutdown) - 5 times - each time got back in. Will narrow down timing further tonight - but I think if you stick to that rule - i.e 60 secs after chunk shutdown your fine - but if there are already people in that chunk when you logged out -- hmmm need further analysis .[/quote]

I just fixed this, the client got reused if coming from the same port/address before being removed and the sequencing was off.

[John Adams]

Jimbo, give this a test on New Telon, if it improves I will push the code public for you to try on your own server(s).

[jimbo]

John - Created a char - logged in - all ok
Logged out - waited about 30 secs - logged in - all okay
Logged out - logged in again within 15 secs - 'Got stuck on waiting for data - no character portrait'
Quit
Tried again - same - stuck on waiting on New Telon

Maybe still an issue - IT was about 11:15am WST (GMT+8) when I tried this

[axisstargazer]

Still have issue that bro doesn't have..

When logging in from same network, same isp. I see on the server
I Net New Session: account ID 100 Session ID '81jhsgdjshdjsh'
I Net New Session: account ID 100 Session ID '81jhsgdjshdjsh'
I Net New Session: account ID 100 Session ID '81jhsgdjshdjsh'
I Net New Session: account ID 100 Session ID '81jhsgdjshdjsh'
I Net New Session: account ID 100 Session ID '81jhsgdjshdjsh'

repeated ad infinitem..

Same Two PCS but one on iphone net.. connects successfully..

Odd behaviour.. trying to debug code to see what''s actually happening..

[theFoof]

Ok, so I guess my fix only fixed it some of the time. I think what's happening now is the loginserver is telling the worldserver to do things too quickly, so they need to be synced up. Should be fixed in the next day or two, if that's the problem.

[jimbo]

Axis solved his issue - it seems his router was doing a 'Hairpin NAT' - and sending the Server the originating IP address - i.e a 192.168.0.N address as opposed
to the external facing Ip address.

He's got a work around for now by using a VPN connection.

Some others might also face this issue (some routers do it and some don't) - we noticed that the server was showing up an internal ip address as 'Connected from' and that gave us the hint.

Jim

[Lokked]

Here is my experience with this (Just updated WS from SVN):

I created 1 character (my first) on my server. I was able to log in, run around. etc.
Closed Client
Waited for client timeout, then relaunched VGO client. At Char Select screen, was met with WoD.
Closed client, waited for timeout, tried again. Same thing. Did this about 6 times.

Created 2nd char. Success in Char Creation. Instead of Pressing Play once char was created, cancelled that window to view Char Select screen: Both char avatars were of the char I'd just created. I selected the first one (perhaps it would turn out to be my original char?). It was the second char's avatar and name. What was also odd was that there were 2 of my chars showing in the Client in IoD: One that I could move (my logged in char), and another floating in the air, where you spawn, named "Prefix Lokked Upp Suffix". This duplicate avatar remained there until I when .rifted out and .rifted back, it was gone. Typing Clients in the WS Console only ever showed 1 connection/account.

I deleted these 2 characters from the Account Management web interface and created a new character. Now I cannot reproduce this behaviour. This new character is the only visible one on the account and hasn't gotten the WoD again since.

[jimbo]

Hi - I reported the same issue on Page 4 of "World Bugs and Crashes List" - it started happening at around 12 noon (GMT+8) on Saturday.

Jim

[Dakadin]

I've been working on trying to track down this issue and wanted to let everyone know that this issue doesn't occur with the rev 579 which is what the New Telon server is using for its code base. If you are having issues connecting to your servers try getting a copy of rev 579 until I can pinpoint the cause of it.

[Dakadin]

Okay it looks like it is more involved than just using an older rev of the code. I will continue to look into it.