Zones Crushing like crazy...

[ChaosSlayer]

Ok I just recently moved a latest build (from my old May 07 build) and zones are crushing liek crazy on me.
I am not even using my custom DB - I am using brand new peq.

My char can't seem to be able to zone even once or twice as zone would crash. But as of this morning I cna't seem to be able to even enter the game - the zones are crashing as soon as log in.

Back with my old build, I ocasinaly had the issue when zone woudl crahs, but then it would QICKLY self reboot while my char still in zone and go on wihout even disconecting me and all would be fine.

But now I am geting droped out in like 30 sec, zone reboots, I try to go back in and zone crashes 15 seconds after I loged in.

some of my crushing info


[01.31. - 12:53:23] [WORLD__CLIENT] New client from 192.168.1.136:3254
[01.31. - 12:53:23] [WORLD__CLIENT] drakeimperor: Logged in. Mode=(CharSel)
[01.31. - 12:53:23] [WORLD__CLIENT] drakeimperor: MiniLogin Account #14
[01.31. - 12:56:19] [WORLD__CLIENT] drakeimperor: Attempting autobootup of paw (18)
[01.31. - 12:56:44] [WORLD__ZONE] [6] Setting to 'paw' (18)
[01.31. - 12:56:44] [WORLD__CLIENT] drakeimperor: Entering zone paw (18)
[01.31. - 12:56:44] [WORLD__ZONE] [6] [paw] Setting to 'paw' (18)
[01.31. - 12:56:44] [WORLD__CLIENT] drakeimperor: Sending client to zone paw (18) at 192.168.1.136:7004
[01.31. - 12:56:45] [WORLD__CLIENT] drakeimperor: Client disconnected (not active in process)
[01.31. - 12:59:41] [WORLD__ZONELIST] Removing zoneserver #6 at :7004
[01.31. - 12:59:52] [WORLD__LAUNCH] zones: dynamic_06 reported state STOPPED (1 starts)
[01.31. - 13:00:02] [WORLD__LAUNCH] zones: dynamic_06 reported state STARTED (2 starts)
[01.31. - 13:00:08] [WORLD__ZONE] New TCP connection from 127.0.0.1:3327
[01.31. - 13:00:08] [WORLD__CONSOLE] New zoneserver #7 from 127.0.0.1:3327
[01.31. - 13:00:08] [WORLD__ZONE] [7] Zone started with name dynamic_06 by launcher zones
[01.31. - 13:00:08] [WORLD__ZONE] [7] Auto zone port configuration. Telling zone to use port 7006
[01.31. - 13:01:23] [WORLD__CLIENT] New connection from 192.168.1.136:3336
[01.31. - 13:01:23] [NET__IDENT_TRACE] 192.168.1.136:3336: First opcode 0x4dd0 did not match expected 0x2792
[01.31. - 13:01:23] [NET__IDENT_TRACE] 192.168.1.136:3336: Tried patch 6.2_world, and it did not match.
[01.31. - 13:01:23] [NET__IDENT_TRACE] 192.168.1.136:3336: First opcode 0x4dd0 did not match expected 0x2ec9
[01.31. - 13:01:23] [NET__IDENT_TRACE] 192.168.1.136:3336: Tried patch 6.2_zone, and it did not match.
[01.31. - 13:01:23] [NET__IDENT_TRACE] 192.168.1.136:3336: First opcode matched 0x4dd0 and length matched 464
[01.31. - 13:01:23] [NET__IDENTIFY] Identified stream 192.168.1.136:3336 with signature Titanium_world
[01.31. - 13:01:23] [WORLD__CLIENT] New client from 192.168.1.136:3336
[01.31. - 13:01:23] [WORLD__CLIENT] drakeimperor: Logged in. Mode=(CharSel)
[01.31. - 13:01:23] [WORLD__CLIENT] drakeimperor: MiniLogin Account #14
[01.31. - 13:07:32] [WORLD__CLIENT_ERR] NOCLE: Expecting OP_SendLoginInfo, got OP_EnterWorld
[01.31. - 13:09:11] [WORLD__CLIENT] New connection from 192.168.1.136:3556
[01.31. - 13:09:11] [NET__IDENT_TRACE] 192.168.1.136:3556: First opcode 0x4dd0 did not match expected 0x2792
[01.31. - 13:09:11] [NET__IDENT_TRACE] 192.168.1.136:3556: Tried patch 6.2_world, and it did not match.
[01.31. - 13:09:11] [NET__IDENT_TRACE] 192.168.1.136:3556: First opcode 0x4dd0 did not match expected 0x2ec9
[01.31. - 13:09:11] [NET__IDENT_TRACE] 192.168.1.136:3556: Tried patch 6.2_zone, and it did not match.
[01.31. - 13:09:11] [NET__IDENT_TRACE] 192.168.1.136:3556: First opcode matched 0x4dd0 and length matched 464
[01.31. - 13:09:11] [NET__IDENTIFY] Identified stream 192.168.1.136:3556 with signature Titanium_world
[01.31. - 13:09:11] [WORLD__CLIENT] New client from 192.168.1.136:3556
[01.31. - 13:09:11] [WORLD__CLIENT] drakeimperor: Logged in. Mode=(CharSel)
[01.31. - 13:09:11] [WORLD__CLIENT] drakeimperor: MiniLogin Account #14
[01.31. - 13:15:20] [WORLD__CLIENT_ERR] NOCLE: Expecting OP_SendLoginInfo, got OP_AckPacket
[01.31. - 13:16:52] [WORLD__ZONELIST] Removing zoneserver #7 at :7006
[01.31. - 13:16:52] [WORLD__ZONE] New TCP connection from 127.0.0.1:3747
[01.31. - 13:16:52] [WORLD__CONSOLE] New zoneserver #8 from 127.0.0.1:3747
[01.31. - 13:16:52] [WORLD__ZONE] [8] Zone started with name dynamic_06 by launcher zones
[01.31. - 13:16:53] [WORLD__ZONE] [8] Zone specified port 7006, must be a previously allocated zone reconnecting.
[01.31. - 13:17:17] [WORLD__ZONELIST] Removing zoneserver #8 at :7006
[01.31. - 13:17:19] [WORLD__ZONE] New TCP connection from 127.0.0.1:3752
[01.31. - 13:17:19] [WORLD__CONSOLE] New zoneserver #9 from 127.0.0.1:3752
[01.31. - 13:17:19] [WORLD__ZONE] [9] Zone started with name dynamic_06 by launcher zones
[01.31. - 13:17:19] [WORLD__ZONE] [9] Zone specified port 7006, must be a previously allocated zone reconnecting.
[01.31. - 13:17:23] [WORLD__LS] Connecting to login server...
[01.31. - 13:17:23] [WORLD__LS] Setting World to MiniLogin Server type
[01.31. - 13:17:23] [WORLD__LS] Connected to Loginserver: 127.0.0.1:5999

[AndMetal]

Out of curiosity (and I'm kinda jumping ahead on this one), do you start go to LD right as you zone in?

In my experience, it's usually because I'm missing the spells_us.txt file, but it can also be something not setup properly in the DB.

If you can show a log of the zone that's crashing, that would be more helpful. It should indicate where it's failing to load.

[narcberry]

The latest, brand new cvs release of the peq db is usually still behind the eqemu version. Whenever I do a cvs update on the peq db, I find the newest file and apply all sql changes in the changelog from that date on. However, I don't think this is your big problem.

[01.31. - 13:15:20] [WORLD__CLIENT_ERR] NOCLE: Expecting OP_SendLoginInfo, got OP_AckPacket

Did you copy in the latest patchfiles? I know those have had significant updates.

[cavedude]

CVS is current. The last sql change required by the code was actually coded by me, so for once PEQ CVS was slightly ahead of the code for a few hours ;)

[ChaosSlayer]

Out of curiosity (and I'm kinda jumping ahead on this one), do you start go to LD right as you zone in?

In my experience, it's usually because I'm missing the spells_us.txt file, but it can also be something not setup properly in the DB.

If you can show a log of the zone that's crashing, that would be more helpful. It should indicate where it's failing to load.

You were 100% right =)
I forgot the spells =)
But the best part is that the first zone I went into were Broodlands- it was working FINE wihout spells - prabobly because mosb do not have any spell assigned to them yet. But as soon as I try to go Commons or Paw- I started get booted.


BTW unrelated crash: tryign to CLICK "get random name" at char cretaion screen creates an error along the lines of:

"OP_login_info excpected OP_random_name recived instead. World have crashed"

Puting a char name manual works fine

BTW- what are good number setting for things like zone time out? char time out? In case zone crashes/LDs I like it to quickly reboot, and keep players in wihout booting them off.

Thanks =)