Odd Client Disconnects and Server Crashes
 

Has anyone recently experienced issues with indeterminable server crashes or client disconnects upon zoning?


Possible factors:

- Bots Enabled (Verified occurrence in non-bot enabled code)
- Perl Support (Verified occurrence in non-perl enabled code)
- Lua Support (Verified occurrence in non-lua enabled code)
- Windows Server


EDIT: I define recently within the last 3 months or so using up-to-date code.

If so, please consult your doctor.
(My code was last git pulled from master branch about 1 month ago, and I don't use bot, and I don't have these symptoms)

No crashes per se on my side, but I've been experiencing a couple of client disconnects here and there using the latest code (bots enabled + Windows server).

These disconnects were few and usually happened during the first 5 or so minutes of my server coming online and me logging in to a zone - I'd then get kicked back to the Character screen.

No other disconnections were noticed past that point, tho !

Thanks for the input guys!


I did replicate the issue in non-bot code..so, that contributor is out.


TBH, it looks like the zone server is spooling up and shutting down before the client is able to contact it (5000ms timer.)

After the shutdown, there does appear to be a TCP re-connection from zone to world. (I have 3 dynamic zones for solo play - no static.)

I need to test the #zone command to see if the problem persists there..but, any world->zone login or zone->zone login can create the issue. (Tested UF, RoF and RoF2)


My test was zoning from 'Crescent Reach' to 'Blightfire Moors'

I know that Moors is a large zone..but, that shouldn't be a factor. I have successfully made that transition hundreds of times in the past.


EDIT:

There is at least one other player experiencing this.

I was trying to help him update his code and database and we were weeding out issues when this particular behavior popped up.

I logged in to see if I could replicate it and did so in my 'clean' code and database localhost server.


UPDATE:

I build a clean server with no bots and no perl/lua support.

The issue still persists..

Logs for affected world and zone servers:


world: http://wiki.eqemulator.org/i?Module=...Paste=jTKJ91ei

zone: http://wiki.eqemulator.org/i?Module=...Paste=Ln371PZj


EDIT: I changed the zone auto-shutdown value from 5 to 120 seconds with no affect.

So you aren't getting any actual world/zone crash dumps? Those packets are definitely gobbledygook...

Nothing..and I enabled even more log cats after posting those.

The only changes locally since it worked last are the routine repo pulls and db updates.

[07-06-2016 :: 16:48:55] [World Server] Zone bootup timer expired, bootup failed or too slow.

HD or ram corruption, perhaps

I don't have any issues (atm) with anything else on my system..and I push the limits of 8GB with apps sometimes.

I'm running Win7 pro and the other user has Windows Server 2012.


I know most ppl that update their servers regularly are probably Linux users..so, if it's a Windows-related issue, it may be up to a month or more before others start to see it.

(That issue with linking the dll's from static to dynamic went a few months before others started reporting the problem.)

I can't wait until this bug is fixed , it has been a plague for the players on Raid Addicts. Really appreciate you looking into this folks and hope to see a fix soon from these efforts.

Mort
www.raidaddicts.org

I tried replicating this, but no bananas.I updated source today. (one with bots enabled and one without). I zoned all over, including crescent>blightfire and #zone'd all over, didn't get
any problems. Only issue I have ever had in the past with a client crashing, once in awhile,
after I do some DB edits, start server up, then when I try to enter world, the client crashes
but it will only do it once and server sees it as linkdead. That only happens once in a blue
moon though. But I've never crashed from zoning. Win 7 Ultimate OS

I'm starting to lean towards a timeout issue and map loading.

High detail zone maps (moors, springs, mesa) take forever to load and I think the bootup timer may be expiring.

May not be the issue..but, I'll keep digging in this hole for awhile.

I will agree, just zoning in to moors takes a good 20+ secs. (my client box is not
shy for gaming hardware).

I got this message in the client when I was actually able to get into moors:


I have a ton of logging enabled atm..but, it's all going to file and nothing additional to gmsay.