massive Zone Unavalable errors +more

[ChaosSlayer]

part 2 with numerious atempts to autoboot with no success at the end

[02.08. - 00:54:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:3256
[02.08. - 00:54:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:3257
[02.08. - 00:54:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:3258
[02.08. - 00:54:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:3259
[02.08. - 00:54:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:3260
[02.08. - 00:54:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:3261
[02.08. - 00:54:35] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:3261
[02.08. - 00:54:35] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:3260
[02.08. - 00:54:35] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:3259
[02.08. - 00:54:35] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:3258
[02.08. - 00:54:35] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:3257
[02.08. - 00:54:35] [WORLD__CONSOLE] New zoneserver #6 from 127.0.0.1:3256
[02.08. - 00:54:36] [WORLD__ZONE] [6] Zone started with name dynamic_04 by launcher zones
[02.08. - 00:54:36] [WORLD__ZONE] [6] Auto zone port configuration. Telling zone to use port 7000
[02.08. - 00:54:36] [WORLD__ZONE] [5] Zone started with name dynamic_03 by launcher zones
[02.08. - 00:54:36] [WORLD__ZONE] [5] Auto zone port configuration. Telling zone to use port 7001
[02.08. - 00:54:36] [WORLD__ZONE] [4] Zone started with name dynamic_02 by launcher zones
[02.08. - 00:54:36] [WORLD__ZONE] [4] Auto zone port configuration. Telling zone to use port 7002
[02.08. - 00:54:36] [WORLD__ZONE] [3] Zone started with name dynamic_01 by launcher zones
[02.08. - 00:54:36] [WORLD__ZONE] [3] Auto zone port configuration. Telling zone to use port 7003
[02.08. - 00:54:36] [WORLD__ZONE] [2] Zone started with name dynamic_05 by launcher zones
[02.08. - 00:54:36] [WORLD__ZONE] [2] Auto zone port configuration. Telling zone to use port 7004
[02.08. - 00:54:36] [WORLD__ZONE] [1] Zone started with name dynamic_06 by launcher zones
[02.08. - 00:54:36] [WORLD__ZONE] [1] Auto zone port configuration. Telling zone to use port 7005
[02.08. - 00:59:37] [WORLD__CLIENT] New connection from 192.168.1.136:3265
[02.08. - 00:59:37] [NET__IDENT_TRACE] 192.168.1.136:3265: First opcode 0x4dd0 did not match expected 0x2792
[02.08. - 00:59:37] [NET__IDENT_TRACE] 192.168.1.136:3265: Tried patch 6.2_world, and it did not match.
[02.08. - 00:59:37] [NET__IDENT_TRACE] 192.168.1.136:3265: First opcode 0x4dd0 did not match expected 0x2ec9
[02.08. - 00:59:37] [NET__IDENT_TRACE] 192.168.1.136:3265: Tried patch 6.2_zone, and it did not match.
[02.08. - 00:59:37] [NET__IDENT_TRACE] 192.168.1.136:3265: First opcode matched 0x4dd0 and length matched 464
[02.08. - 00:59:37] [NET__IDENTIFY] Identified stream 192.168.1.136:3265 with signature Titanium_world
[02.08. - 00:59:37] [WORLD__CLIENT] New client from 192.168.1.136:3265
[02.08. - 00:59:37] [WORLD__CLIENT] drakeimperor: Logged in. Mode=(CharSel)
[02.08. - 00:59:37] [WORLD__CLIENT] drakeimperor: LS Account #101724
[02.08. - 01:01:38] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)
[02.08. - 01:02:14] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)
[02.08. - 01:02:24] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)
[02.08. - 01:02:28] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)
[02.08. - 01:02:32] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)
[02.08. - 01:15:45] [WORLD__CLIENT_ERR] NOCLE: Expecting OP_SendLoginInfo, got OP_EnterWorld
[02.08. - 01:16:30] [WORLD__CLIENT] New connection from 192.168.1.136:3288
[02.08. - 01:16:30] [NET__IDENT_TRACE] 192.168.1.136:3288: First opcode 0x4dd0 did not match expected 0x2792
[02.08. - 01:16:31] [NET__IDENT_TRACE] 192.168.1.136:3288: Tried patch 6.2_world, and it did not match.
[02.08. - 01:16:31] [NET__IDENT_TRACE] 192.168.1.136:3288: First opcode 0x4dd0 did not match expected 0x2ec9
[02.08. - 01:16:31] [NET__IDENT_TRACE] 192.168.1.136:3288: Tried patch 6.2_zone, and it did not match.
[02.08. - 01:16:31] [NET__IDENT_TRACE] 192.168.1.136:3288: First opcode matched 0x4dd0 and length matched 464
[02.08. - 01:16:31] [NET__IDENTIFY] Identified stream 192.168.1.136:3288 with signature Titanium_world
[02.08. - 01:16:31] [WORLD__CLIENT] New client from 192.168.1.136:3288
[02.08. - 01:16:31] [WORLD__CLIENT] drakeimperor: Logged in. Mode=(CharSel)
[02.08. - 01:16:31] [WORLD__CLIENT] drakeimperor: LS Account #101724
[02.08. - 01:19:27] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)
[02.08. - 01:20:17] [WORLD__CLIENT] drakeimperor: Attempting autobootup of gfaydark (54)

[ChaosSlayer]

ok found something what could be interesting, and prety much cuases the error, however I am at a loos how to fix it.
Apparetnly it desperatly looking for specific spawn2 ID which however is not used in any other table. I am not mySQl expert - but the local IDs of spawn2 table are mapping to anywhere? Is there a pattern to this numbers?
I was under impression they could be deleted at will or changed.

---------------------------------------------
[02.08. - 01:45:18] Starting Log: logs/eqemu_error_zone_2212.log
[02.08. - 01:45:18] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:18] Loading zone state failed.
[02.08. - 01:45:32] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:32] Loading zone state failed.
[02.08. - 01:45:34] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:34] Loading zone state failed.
[02.08. - 01:45:35] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:35] Loading zone state failed.
[02.08. - 01:45:36] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:36] Loading zone state failed.
[02.08. - 01:45:37] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:37] Loading zone state failed.
[02.08. - 01:45:39] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:39] Loading zone state failed.
[02.08. - 01:45:40] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:45:40] Loading zone state failed.
[02.08. - 01:46:14] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:46:14] Loading zone state failed.
[02.08. - 01:46:16] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:46:16] Loading zone state failed.
[02.08. - 01:47:48] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=332456':
[02.08. - 01:47:48] Loading zone state failed.
[02.08. - 01:48:34] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=16451159':
[02.08. - 01:48:34] Loading zone state failed.

[ChaosSlayer]

ok this getting ridiculus I am got a brand new PEQ DB, copied over my own spawn info (spawn2, spawnentry and spawngroup) from my old backedup DB, and I am still getign the same stupid error!

---------------------------------------------
[02.09. - 00:56:04] Starting Log: logs/eqemu_error_zone_1244.log
[02.09. - 00:56:04] Error in LoadSpawn2 query 'SELECT id, spawngroupID, x, y, z, heading, respawntime, variance, pathgrid, _condition, cond_value FROM spawn2 WHERE id=332456':
[02.09. - 00:56:04] Loading zone state failed.

I have no idea WHY in the world I woudl get this error if in my original DB these values never existed to begin with.
The program keep trying to pull up something which is not referenced ANYWHERE!

[ChaosSlayer]

ok i did some mySQl manual reading - it seesm that problem is with the spawn2 table.

The table is InnoDB type - and from I understand this thing CANNOT BE just backed up, cuase the IDs of the primary key writen into file are not REAL IDs.
And if you EVER do any changes - like delete an entry and then back up the DB And if DB is later restored from backup - the whole thing (since it uses internal index table which is not shown to the user) and discover than enetry that supose to follow does nto exist - the whole thing crashes...

This mayby not very accurate (I am not mySQl expert), but i belive the problem is how to PROPERLY backup spawn2 table which was in any way altered so it will actualy WORK after restore..

Any mySQl experts can help with this????

[ChaosSlayer]

ok, this cost me a few grey hair (well few hair...), but with little mySQl expert help we solved this one....

PEOPLE!!! If you EVER delete or move ANY values in spawn2 tables using 1090 server build (INCLUDING using GeorgeS spawn editing tool) TURN OFF zone persistant state! Otherwise you will spend next 5 days drawing in error codes....

[Yeormom]

Thanks for sharing!

I spent longer than I should have looking for why the zone was trying to load a spawn with an id in the billions...