new binaries

SoTRichard · #1 08-22-2007, 11:23 AM

ok, i sourced in a few of those updates because some of them i had already done but it didn't do anything for the server hehe... i think my server still thinks it's running on 7.0.0 even though i overwrote world.exe and everything else i've mentioned before. here's what my world.exe shows...

Code:

[Debug] Starting Log: logs/eqemu_debug_world_5640.log
[Debug] [WORLD__INIT] Loading server configuration..
[Debug] [WORLD__INIT] Log settings loaded from log.ini
[Debug] [WORLD__INIT] CURRENT_WORLD_VERSION:EQEMu 0.7.0
[Debug] [WORLD__INIT] Connecting to MySQL...
[Status] Starting Log: logs/eqemu_world_5640.log
[Status] Using database 'ax' at localhost:3306
[Debug] [WORLD__INIT] Starting HTTP world service...
[Debug] [WORLD__HTTP] Loaded mime types from mime.types
[Debug] [WORLD__INIT] Loading variables..
[Debug] [WORLD__INIT] Loading zones..
[Debug] [WORLD__INIT] Clearing groups..
[Debug] [WORLD__INIT] Clearing temporary merchant lists..
[Debug] [WORLD__INIT] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=55059
[Debug] [WORLD__INIT] Loading guilds..
[Debug] [WORLD__INIT] Loading EQ time of day..
[Debug] [WORLD__INIT] Loading launcher list..
[Debug] [WORLD__INIT] Reboot zone modes ON
[Debug] [WORLD__INIT] Deleted 0 stale player corpses from database
[Debug] [WORLD__INIT] Deleted 0 stale player backups from database
[Debug] [WORLD__INIT] Zone (TCP) listener started.
[Debug] [WORLD__INIT] Client (UDP) listener started.
[Debug] [NET__IDENTIFY] Registered patch 6.2
[Debug] [NET__IDENTIFY] Registered patch Titanium
[Debug] [NET__IDENTIFY] Registered patch Live
[Debug] [WORLD__LS] Connecting to login server...
[Debug] [WORLD__LS] Connected to Loginserver: eqemulator.net:5998
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1518
[Debug] [WORLD__CONSOLE] New launcher from 127.0.0.1:1518
[Debug] [WORLD__LAUNCH] Adding pending launcher 1
[Debug] [WORLD__LAUNCH] Launcher Identified itself as 'zone'. Loading zone list.

[Debug] [WORLD__LAUNCH] Removing pending launcher 1. Adding zone to active list.

[Debug] [WORLD__LAUNCH] zone: dynamic_01 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1532
[Debug] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:1532
[Debug] [WORLD__ZONE] [1] Zone started with name dynamic_01 by launcher zone
[Debug] [WORLD__ZONE] [1] Auto zone port configuration.  Telling zone to use por
t 7000
[Debug] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1534
[Debug] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:1534
[Debug] [WORLD__ZONE] [2] Zone started with name dynamic_02 by launcher zone
[Debug] [WORLD__ZONE] [2] Auto zone port configuration.  Telling zone to use por
t 7001
[Debug] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1536
[Debug] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:1536
[Debug] [WORLD__ZONE] [3] Zone started with name dynamic_03 by launcher zone
[Debug] [WORLD__ZONE] [3] Auto zone port configuration.  Telling zone to use por
t 7002
[Debug] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1538
[Debug] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:1538
[Debug] [WORLD__ZONE] [4] Zone started with name dynamic_04 by launcher zone
[Debug] [WORLD__ZONE] [4] Auto zone port configuration.  Telling zone to use por
t 7003
[Debug] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1540
[Debug] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:1540
[Debug] [WORLD__ZONE] [5] Zone started with name dynamic_05 by launcher zone
[Debug] [WORLD__ZONE] [5] Auto zone port configuration.  Telling zone to use por
t 7004
[Debug] [WORLD__LAUNCH] zone: dynamic_06 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1542
[Debug] [WORLD__CONSOLE] New zoneserver #6 from 127.0.0.1:1542
[Debug] [WORLD__ZONE] [6] Zone started with name dynamic_06 by launcher zone
[Debug] [WORLD__ZONE] [6] Auto zone port configuration.  Telling zone to use por
t 7005
[Debug] [WORLD__LAUNCH] zone: dynamic_07 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1544
[Debug] [WORLD__CONSOLE] New zoneserver #7 from 127.0.0.1:1544
[Debug] [WORLD__ZONE] [7] Zone started with name dynamic_07 by launcher zone
[Debug] [WORLD__ZONE] [7] Auto zone port configuration.  Telling zone to use por
t 7006
[Debug] [WORLD__LAUNCH] zone: dynamic_08 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1546
[Debug] [WORLD__CONSOLE] New zoneserver #8 from 127.0.0.1:1546
[Debug] [WORLD__ZONE] [8] Zone started with name dynamic_08 by launcher zone
[Debug] [WORLD__ZONE] [8] Auto zone port configuration.  Telling zone to use por
t 7007
[Debug] [WORLD__LAUNCH] zone: dynamic_09 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1548
[Debug] [WORLD__CONSOLE] New zoneserver #9 from 127.0.0.1:1548
[Debug] [WORLD__ZONE] [9] Zone started with name dynamic_09 by launcher zone
[Debug] [WORLD__ZONE] [9] Auto zone port configuration.  Telling zone to use por
t 7008
[Debug] [WORLD__LAUNCH] zone: dynamic_10 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1550
[Debug] [WORLD__CONSOLE] New zoneserver #10 from 127.0.0.1:1550
[Debug] [WORLD__ZONE] [10] Zone started with name dynamic_10 by launcher zone
[Debug] [WORLD__ZONE] [10] Auto zone port configuration.  Telling zone to use po
rt 7009
[Debug] [WORLD__LAUNCH] zone: dynamic_11 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1552
[Debug] [WORLD__CONSOLE] New zoneserver #11 from 127.0.0.1:1552
[Debug] [WORLD__ZONE] [11] Zone started with name dynamic_11 by launcher zone
[Debug] [WORLD__ZONE] [11] Auto zone port configuration.  Telling zone to use po
rt 7010
[Debug] [WORLD__LAUNCH] zone: dynamic_12 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1554
[Debug] [WORLD__CONSOLE] New zoneserver #12 from 127.0.0.1:1554
[Debug] [WORLD__ZONE] [12] Zone started with name dynamic_12 by launcher zone
[Debug] [WORLD__ZONE] [12] Auto zone port configuration.  Telling zone to use po
rt 7011
[Debug] [WORLD__LAUNCH] zone: dynamic_13 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1556
[Debug] [WORLD__CONSOLE] New zoneserver #13 from 127.0.0.1:1556
[Debug] [WORLD__ZONE] [13] Zone started with name dynamic_13 by launcher zone
[Debug] [WORLD__ZONE] [13] Auto zone port configuration.  Telling zone to use po
rt 7012
[Debug] [WORLD__LAUNCH] zone: dynamic_14 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1558
[Debug] [WORLD__CONSOLE] New zoneserver #14 from 127.0.0.1:1558
[Debug] [WORLD__ZONE] [14] Zone started with name dynamic_14 by launcher zone
[Debug] [WORLD__ZONE] [14] Auto zone port configuration.  Telling zone to use po
rt 7013
[Debug] [WORLD__LAUNCH] zone: dynamic_15 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1560
[Debug] [WORLD__CONSOLE] New zoneserver #15 from 127.0.0.1:1560
[Debug] [WORLD__ZONE] [15] Zone started with name dynamic_15 by launcher zone
[Debug] [WORLD__ZONE] [15] Auto zone port configuration.  Telling zone to use po
rt 7014
[Debug] [WORLD__LAUNCH] zone: dynamic_16 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1562
[Debug] [WORLD__CONSOLE] New zoneserver #16 from 127.0.0.1:1562
[Debug] [WORLD__ZONE] [16] Zone started with name dynamic_16 by launcher zone
[Debug] [WORLD__ZONE] [16] Auto zone port configuration.  Telling zone to use po
rt 7015
[Debug] [WORLD__LAUNCH] zone: dynamic_17 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1564
[Debug] [WORLD__CONSOLE] New zoneserver #17 from 127.0.0.1:1564
[Debug] [WORLD__ZONE] [17] Zone started with name dynamic_17 by launcher zone
[Debug] [WORLD__ZONE] [17] Auto zone port configuration.  Telling zone to use po
rt 7016
[Debug] [WORLD__LAUNCH] zone: dynamic_18 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1566
[Debug] [WORLD__CONSOLE] New zoneserver #18 from 127.0.0.1:1566
[Debug] [WORLD__ZONE] [18] Zone started with name dynamic_18 by launcher zone
[Debug] [WORLD__ZONE] [18] Auto zone port configuration.  Telling zone to use po
rt 7017
[Debug] [WORLD__LAUNCH] zone: dynamic_19 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1568
[Debug] [WORLD__CONSOLE] New zoneserver #19 from 127.0.0.1:1568
[Debug] [WORLD__ZONE] [19] Zone started with name dynamic_19 by launcher zone
[Debug] [WORLD__ZONE] [19] Auto zone port configuration.  Telling zone to use po
rt 7018
[Debug] [WORLD__LAUNCH] zone: dynamic_20 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1570
[Debug] [WORLD__CONSOLE] New zoneserver #20 from 127.0.0.1:1570
[Debug] [WORLD__ZONE] [20] Zone started with name dynamic_20 by launcher zone
[Debug] [WORLD__ZONE] [20] Auto zone port configuration.  Telling zone to use po
rt 7019

Angelox · #2 08-22-2007, 11:42 AM

Don't know if this makes any difference, but change the launcher from "zone" to "zones" - thats the way all mine are (change in batch files and DB). Hope you didn't overwrite your eqemu_config.xml file ( I did that once)?
It appears you launched 20 dynamic zones?

SoTRichard · #3 08-22-2007, 12:20 PM

just changed them both (batch and db) to zones and it didn't make any difference =/... and nope, didn't overwrite my eqemu_config.xml...
ya, i booted 20 dynamic zones... like i said before my server has been up and running for about 2 months just fine... and the other day i decided to update my binaries from 7.0.0 to 7.0-1034.

Angelox · #4 08-22-2007, 01:04 PM

All I can think of, is your SQL database is still missing something - You need to go back through the log files at the EqEmu download, and see if all is included. also you need to source in things like the AAData.Sql. If the latter isn't properly added, it won't work (didn't with me).

sfisque · #5 08-23-2007, 05:24 AM

you mentioned overwriting world.exe and zone.exe. did you also update the EMuShareMem module? not sure what its called on windows, but i know if you dont update it on linux when updating the other binaries, all sorts of fubar behavior happens.

== sfisque

**GeorgeS** · #6 08-23-2007, 02:17 PM

Please note, my site has an updated list of all sql needed to make this work. If your DB is not in compliance fully, it won't work at all.

GeorgeS

techguy84 · #7 08-23-2007, 06:36 PM

What customized stuff do you have on your server SoTRichard? Most things that you have customized, and things that are not present in a new DB (like player accounts)could be backed up and resourced into a more current DB like PEQ CVS or Angelox's, unless there was table structure changes in those tables from your DB to a new one. I would just say that if your wanting to fully update to a newer version, and you dont have custom content, back up your characters and accounts, make a new DB using a newer release, and then source your stuff back in to the newer one. Replace all files for the server itself, make any config file changes and let er rip.

But thats my opinion, and it could turn out to be more hassle than its worth in some cases.

Your zone launcher, given your log file is functioning perfectly to the normal eye, as its connecting to world, and world is setting up ports and making connections ect... Is world just not transfering characters over to zone?

P.S. Just now read this in your OP. The launcher is a blank window. It shows absolutly nothing. The key to see wether its working or not is to see the connections made in world and that the launcher title goes to 0:Sleeping, of course meaning that it has been set up, and is in sleep mode since there is no active client connections or booted up zones.

SoTRichard · #8 08-24-2007, 05:38 AM

Quote:

Originally Posted by GeorgeS

Please note, my site has an updated list of all sql needed to make this work. If your DB is not in compliance fully, it won't work at all.

GeorgeS

ok, thanks just tried your website now and it works... for some reason it hadn't been working.

SoTRichard · #9 08-24-2007, 03:29 PM

Quote:

Originally Posted by GeorgeS

Please note, my site has an updated list of all sql needed to make this work. If your DB is not in compliance fully, it won't work at all.

GeorgeS

ok, just finished sourcing in everything on your site... and i'm still getting the error... here is what world looks like when i try to enter from character select...

Code:

[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Recevied EQApplicationPacket
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Recevied EQApplicationPacket
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Recevied EQApplicationPacket
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x00f
b
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x010
9
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x010
a
[Debug] [WORLD__CLIENT] TheJ2005: Attempting autobootup of tutorial (183)
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x00c
7
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Recevied EQApplicationPacket
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Recevied EQApplicationPacket
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x00f
b
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x010
9
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x010
a
[Debug] [WORLD__CLIENT] TheJ2005: Attempting autobootup of tutorial (183)
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Sending EQApplicationPacket OpCode 0x00c
7
[Debug] [WORLD__CLIENT_TRACE] TheJ2005: Recevied EQApplicationPacket

SoTRichard · #10 08-24-2007, 05:37 AM

Quote:

Originally Posted by sfisque

you mentioned overwriting world.exe and zone.exe. did you also update the EMuShareMem module? not sure what its called on windows, but i know if you dont update it on linux when updating the other binaries, all sorts of fubar behavior happens.

== sfisque

yeah, i did the emusharemem.dll and mime.types as well