Zone.exe crashes directly after entering world

[Culex]

Hiyas,

All day today I've been experiencing zone.exe crashing directly after I have entered a character from the character-select screen. I get into the zone, but it acts as if I'm linkdead and just disconnects me after the set time.

Anyways, after some poking around logs and some experimenting with various backups of previous states of the server I can't find out why this is happening. It happens even with older server states that have worked fine for half a month.

So, here's some information about what I have:

I use the Minilogin server from Cavedude's serverpack

The adresses in eqemu_config.xml are set to 127.0.0.1 with no other changes.

Here are the last few lines of the zone log:

[07.13. - 16:29:37] Default weather for zone is:1
[07.13. - 16:29:37] [WORLD__CLIENT] New connection from 127.0.0.1:1153
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: First opcode 0x7752 did not match expected 0x2792
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: Tried patch 6.2_world, and it did not match.
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: First opcode 0x7213 did not match expected 0x2ec9
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: Tried patch 6.2_zone, and it did not match.
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: First opcode 0x7752 did not match expected 0x4dd0
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: Tried patch Titanium_world, and it did not match.
[07.13. - 16:29:38] [NET__IDENT_TRACE] 127.0.0.1:1153: First opcode matched 0x7213 and length matched 68
[07.13. - 16:29:38] [NET__IDENTIFY] Identified stream 127.0.0.1:1153 with signature Titanium_zone
[07.13. - 16:29:38] [WORLD__CLIENT] New client from 127.0.0.1:1153
[07.13. - 16:29:54] Unable to convert EQ opcode 0x5966 to an Application opcode.
[07.13. - 16:30:07] [GUILDS__OUT_PACKETS] Soandso: Sending OP_GuildMOTD of length 648


Here are the two lines from the zone error log:

[07.13. - 16:29:54] Starting Log: logs/eqemu_error_zone_2924.log
[07.13. - 16:29:54] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 0


Hopefully that will help anyone help me.


Culex

[Culex]

Well, after some trial and error I finally got it worked out.

The problem seemed to be the characters I had in the database.

I came to this conclusion first by trying a fresh server install with the server upgraded to the 0.7.0-821 build and the database updated accordingly. This worked fine, so I had ruled out that it was something other than the server and database.

Next thing I did was try the database that didn't work previously, and it still didn't work. So, server troubles ruled out I began to test and tinker with the database to see what went wrong.

After some time studying the differences between the two databases and much switching back and forth between the two, I finally tried a character and account purge on the non-working database. Now it worked! Yay!


Anyways, hope this helps anyone else who finds themself in a similar situation.


Culex

[Culex]

Okie dokies.

After encountering the problem once more(In the span of one day no less!) I went to work to find out more about it.

After some forum-delving and database editing I finally found out that I had an npc_faction entry which id-column exceeded the limit of 49999. A quick fix there, some editing of other entries in npc_faction_entries and faction_list later on and I'm back up and running.

Here's the link to the thread that really tipped me off about it:
HELP!!!.. had a slight accident!


Culex

[quintenwolfe]

I am still getting this problem as well. I did a fresh install too.
Decided to use Linux.. and Minilogin on a windows machine.

EQEmu-0.7.0-823 is the version I have....

I can login fine.. create characters..

soon as I select a character and try to zone in.. it gives the following just before it croaks...

[Status] Zone Bootup: halas (29)
[Debug] Default weather for zone is:1
[Debug] [WORLD__ZONE] [12] Setting to 'halas' (29)
[Debug] [WORLD__CLIENT] quinten: Entering zone halas (29)
[Debug] [WORLD__ZONE] [12] [halas] Setting to 'halas' (29)
[Debug] [WORLD__CLIENT] quinten: Sending client to zone halas (29) at 192.168.1.12:7011
[Debug] [WORLD__CLIENT] quinten: Client disconnected (not active in process)
[Debug] [WORLD__CLIENT] New connection from 192.168.1.9:4036
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: First opcode 0x7752 did not match expected 0x2792
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: Tried patch 6.2_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: First opcode 0x7213 did not match expected 0x2ec9
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: Tried patch 6.2_zone, and it did not match.
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: First opcode 0x7752 did not match expected 0x4dd0
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: Tried patch Titanium_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 192.168.1.9:4036: First opcode matched 0x7213 and length matched 68
[Debug] [NET__IDENTIFY] Identified stream 192.168.1.9:4036 with signature Titanium_zone
[Debug] [WORLD__CLIENT] New client from 192.168.1.9:4036
[Debug] Unable to convert EQ opcode 0x5966 to an Application opcode.
[Error] Starting Log: logs/eqemu_error_zone.log
[Error] HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 0
./zload: line 4: 3333 Segmentation fault ./zone
[Debug] [WORLD__ZONELIST] Removing zoneserver #12 at :7011
[Debug] [WORLD__ZONELIST] Hold Zones mode is ON - rebooting lost zone
Got Server Requested Zone reboot
Removing connection

One thing I DO notice... is
It identifies the client once as
"[Debug] [NET__IDENTIFY] Identified stream 192.168.1.9:4036 with signature Titanium_zone"

When I tried to zone in..

but before it identifies the client as

"[Debug] [NET__IDENTIFY] Identified stream 192.168.1.9:4029 with signature Titanium_world
[Debug] [WORLD__CLIENT] New client from 192.168.1.9:4029
"

when I was login in......

I have done all the adjustments according to the changelogs, wiped databases, re-installed...

re-copied the opcodes from utils.. as well as copied them from a Windows version I have installed..

If it is database related... where? I checked the npc_faction_entries.. nothing over 49999..

but in npc_types.. there are several over that number.. could that be it?

what am I missing?

I used cavedude's database and peq database..
....

Its funny.. really. I didnt have this issue before with the windows server install.. but then again.. i ran that ServerPack self install on windows.. and ya really cant tell what the hell that thing is doing, and there really isnt any step by step windows install in any of the docs or forum searchs.

Notice: I downloaded, compiled and installed EQEmu-0.7.0-823.. but
why in the debug is it showing tried patch 6.2_world and 6.2_zone? or are those just defaults?

[rojadruid]

Originally Posted by quintenwolfe

Its funny.. really. I didnt have this issue before with the windows server install.. but then again.. i ran that ServerPack self install on windows.. and ya really cant tell what the hell that thing is doing, and there really isnt any step by step windows install in any of the docs or forum searchs.

You should look in the wiki, it can be your friend.

[quintenwolfe]

I have been checking into the wiki. Learning alot from it.. however, after toying with the databases and making several changes. reinstalls.. (including Titanium Client)

I am still getting the following message in my zone logs...

HandlePacket() Opcode error: Unexpected packet during CLIENT_CONNECTING: opcode: OP_Unknown (#0 eq=0x0000), size: 0

Now.. should I be looking at the opcodes conf files? or is it a client problem?

I have 2 PC's running the same client... get the same error..

and I have 2 databases.. .cavedudes and peq. ...

They are both 0.6.6 with the items.sql update from the ServerPack

[Belfedia]

Have you apply all SQL mod on your database like Emulation changelog say ?
With linux version you use the last version of eqemu, and some change
are very important for run the emu.

[bushman77]

too bad there isn't an sql with each that has all the updates already instead of sifting through all of the text in the changelog

[John Adams]

Take charge. Make one.