0.7.0-990 almost working, but not quite ...

herold · #1 03-19-2007, 07:19 PM

Using MySQL v5.0.37
EQemu v0.7.0-990
PEQ CVS (dated march 2)

As you can see, it is almost working (don't remember all that text from 0.7.0, but all the better) ... 2 things that worry me:

1. All the internal (LAN) IP's used, shouldn't it be communicating thru external IP (WAN)?
2. The very last line "Client disconnected (not active in process)", which results in a login screen.

I somehow feel that these 2 could be connected, but I am not sure ... not by a longshot.

Anyone got any input?

External IP exchanged with xxx.xxx.xxx.xxx
LS account exchanged with xxxxx

Code:

[03.16. - 00:09:40] Starting Log: logs/eqemu_debug_world_2176.log
[03.16. - 00:09:40] [WORLD__INIT] Loading server configuration..
[03.16. - 00:09:40] [WORLD__INIT] Log settings loaded from log.ini
[03.16. - 00:09:40] [WORLD__INIT] CURRENT_WORLD_VERSION:EQEMu 0.7.0
[03.16. - 00:09:40] [WORLD__INIT] Connecting to MySQL...
[03.16. - 00:09:40] [WORLD__INIT] Starting HTTP world service...
[03.16. - 00:09:40] [WORLD__HTTP] Loaded mime types from mime.types
[03.16. - 00:09:40] [WORLD__INIT] Loading variables..
[03.16. - 00:09:40] [WORLD__INIT] Loading zones..
[03.16. - 00:09:40] [WORLD__INIT] Clearing groups..
[03.16. - 00:09:40] [WORLD__INIT] Clearing temporary merchant lists..
[03.16. - 00:09:41] [WORLD__INIT] Loading items..
[03.16. - 00:10:13] [WORLD__INIT] Loading guilds..
[03.16. - 00:10:13] [RULES__CHANGE] Loading rule set 'default' (2)
[03.16. - 00:10:13] [WORLD__INIT] Loaded default rule set 'default'
[03.16. - 00:10:13] [WORLD__INIT] Loading EQ time of day..
[03.16. - 00:10:13] [WORLD__INIT] Loading launcher list..
[03.16. - 00:10:13] [WORLD__INIT] Reboot zone modes ON
[03.16. - 00:10:14] [WORLD__INIT] Deleted 0 stale player corpses from database
[03.16. - 00:10:14] [WORLD__INIT] Deleted 0 stale player backups from database
[03.16. - 00:10:14] [WORLD__INIT] Zone (TCP) listener started.
[03.16. - 00:10:14] [WORLD__INIT] Client (UDP) listener started.
[03.16. - 00:10:14] [NET__IDENTIFY] Registered patch 6.2
[03.16. - 00:10:14] [NET__IDENTIFY] Registered patch Titanium
[03.16. - 00:10:14] [NET__IDENTIFY] Registered patch Live
[03.16. - 00:10:14] [WORLD__LS] Connecting to login server...
[03.16. - 00:10:15] [WORLD__ZONE] New TCP connection from 127.0.0.1:2482
[03.16. - 00:10:15] [WORLD__CONSOLE] New launcher from 127.0.0.1:2482
[03.16. - 00:10:15] [WORLD__LAUNCH] Adding pending launcher 1
[03.16. - 00:10:15] [WORLD__LAUNCH] Launcher Identified itself as 'zone'. Loading zone list.
[03.16. - 00:10:15] [WORLD__LAUNCH] Removing pending launcher 1. Adding zone to active list.
[03.16. - 00:10:17] [WORLD__LS] Connected to Loginserver: eqemulator.net:5998
[03.16. - 00:10:18] [WORLD__LS] Loginserver provided xxx.xxx.xxx.xxx as world address
[03.16. - 00:10:20] [WORLD__LAUNCH] zone: dynamic_01 reported state STARTED (1 starts)
[03.16. - 00:10:42] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts)
[03.16. - 00:10:44] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts)
[03.16. - 00:10:47] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts)
[03.16. - 00:10:49] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts)
[03.16. - 00:11:17] [WORLD__CLIENT] New connection from 192.168.111.11:1242
[03.16. - 00:11:17] [NET__IDENT_TRACE] 192.168.111.11:1242: First opcode 0x4dd0 did not match expected 0x2792
[03.16. - 00:11:17] [NET__IDENT_TRACE] 192.168.111.11:1242: Tried patch 6.2_world, and it did not match.
[03.16. - 00:11:17] [NET__IDENT_TRACE] 192.168.111.11:1242: First opcode 0x4dd0 did not match expected 0x2ec9
[03.16. - 00:11:17] [NET__IDENT_TRACE] 192.168.111.11:1242: Tried patch 6.2_zone, and it did not match.
[03.16. - 00:11:17] [NET__IDENT_TRACE] 192.168.111.11:1242: First opcode matched 0x4dd0 and length matched 464
[03.16. - 00:11:17] [NET__IDENTIFY] Identified stream 192.168.111.11:1242 with signature Titanium_world
[03.16. - 00:11:17] [WORLD__CLIENT] New client from 192.168.111.11:1242
[03.16. - 00:11:19] [WORLD__CLIENT] herold: Logged in. Mode=(CharSel)
[03.16. - 00:11:19] [WORLD__CLIENT] herold: LS Account #xxxxx
[03.16. - 00:12:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:2491
[03.16. - 00:12:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:2492
[03.16. - 00:12:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:2493
[03.16. - 00:12:35] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:2492
[03.16. - 00:12:35] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:2491
[03.16. - 00:12:35] [WORLD__ZONE] [2] Zone started with name dynamic_01 by launcher zone
[03.16. - 00:12:35] [WORLD__ZONE] [2] Auto zone port configuration.  Telling zone to use port 7000
[03.16. - 00:12:35] [WORLD__ZONE] [1] Zone started with name dynamic_03 by launcher zone
[03.16. - 00:12:35] [WORLD__ZONE] [1] Auto zone port configuration.  Telling zone to use port 7001
[03.16. - 00:12:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:2494
[03.16. - 00:12:35] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:2494
[03.16. - 00:12:35] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:2493
[03.16. - 00:12:35] [WORLD__ZONE] [4] Zone started with name dynamic_02 by launcher zone
[03.16. - 00:12:35] [WORLD__ZONE] [4] Auto zone port configuration.  Telling zone to use port 7002
[03.16. - 00:12:35] [WORLD__ZONE] [3] Zone started with name dynamic_04 by launcher zone
[03.16. - 00:12:35] [WORLD__ZONE] [3] Auto zone port configuration.  Telling zone to use port 7003
[03.16. - 00:12:35] [WORLD__ZONE] New TCP connection from 127.0.0.1:2495
[03.16. - 00:12:35] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:2495
[03.16. - 00:12:35] [WORLD__ZONE] [5] Zone started with name dynamic_05 by launcher zone
[03.16. - 00:12:35] [WORLD__ZONE] [5] Auto zone port configuration.  Telling zone to use port 7004
[03.16. - 00:12:45] [WORLD__CLIENT] herold: Attempting autobootup of gfaydark (54)
[03.16. - 00:13:26] [WORLD__ZONE] [5] Setting to 'gfaydark' (54)
[03.16. - 00:13:26] [WORLD__CLIENT] herold: Entering zone gfaydark (54)
[03.16. - 00:13:26] [WORLD__ZONE] [5] [gfaydark] Setting to 'gfaydark' (54)
[03.16. - 00:13:26] [WORLD__CLIENT] herold: Sending client to zone gfaydark (54) at 192.168.111.1:7004
[03.16. - 00:13:26] [WORLD__CLIENT] herold: Client disconnected (not active in process)

Kind regards
herold

Zandig · #2 03-20-2007, 05:58 AM

Check this post:
http://www.projecteq.net/phpBB2/viewtopic.php?t=2346

it may be of help.

herold · #3 03-20-2007, 06:28 AM

It could explain a lot ... do you know if the LAN ip's is or isn't a problem?

Just to be sure ... I create a txt document on desktop and copy/paste the code mentioned on the link ... rename the txt to sql and source them?

Upon inspection of my database, I found that the sharedbank is almost right, only "UNIQUE KEY account (acctid,slotid)" is not represented. With regards to the other 3, those tables are not present.

herold · #4 03-20-2007, 07:27 AM

Made the changes, but still ... "Client disconnected (not active in process)"

Code:

[03.20. - 21:18:09] Starting Log: logs/eqemu_debug_world_1756.log
[03.20. - 21:18:09] [WORLD__INIT] Loading server configuration..
[03.20. - 21:18:09] [WORLD__INIT] Log settings loaded from log.ini
[03.20. - 21:18:09] [WORLD__INIT] CURRENT_WORLD_VERSION:EQEMu 0.7.0
[03.20. - 21:18:09] [WORLD__INIT] Connecting to MySQL...
[03.20. - 21:18:09] [WORLD__INIT] Starting HTTP world service...
[03.20. - 21:18:09] [WORLD__HTTP] Loaded mime types from mime.types
[03.20. - 21:18:09] [WORLD__INIT] Loading variables..
[03.20. - 21:18:09] [WORLD__INIT] Loading zones..
[03.20. - 21:18:09] [WORLD__INIT] Clearing groups..
[03.20. - 21:18:10] [WORLD__INIT] Clearing temporary merchant lists..
[03.20. - 21:18:10] [WORLD__INIT] Loading items..
[03.20. - 21:18:40] [WORLD__INIT] Loading guilds..
[03.20. - 21:18:40] [RULES__CHANGE] Loading rule set 'default' (2)
[03.20. - 21:18:40] [WORLD__INIT] Loaded default rule set 'default'
[03.20. - 21:18:40] [WORLD__INIT] Loading EQ time of day..
[03.20. - 21:18:40] [WORLD__INIT] Loading launcher list..
[03.20. - 21:18:40] [WORLD__INIT] Reboot zone modes OFF
[03.20. - 21:18:40] [WORLD__INIT] Deleted 0 stale player corpses from database
[03.20. - 21:18:40] [WORLD__INIT] Deleted 0 stale player backups from database
[03.20. - 21:18:40] [WORLD__INIT] Zone (TCP) listener started.
[03.20. - 21:18:40] [WORLD__INIT] Client (UDP) listener started.
[03.20. - 21:18:41] [NET__IDENTIFY] Registered patch 6.2
[03.20. - 21:18:41] [NET__IDENTIFY] Registered patch Titanium
[03.20. - 21:18:41] [NET__IDENTIFY] Registered patch Live
[03.20. - 21:18:41] [WORLD__ZONE] New TCP connection from 127.0.0.1:1408
[03.20. - 21:18:41] [WORLD__CONSOLE] New launcher from 127.0.0.1:1408
[03.20. - 21:18:41] [WORLD__LAUNCH] Adding pending launcher 1
[03.20. - 21:18:41] [WORLD__LAUNCH] Launcher Identified itself as 'zone'. Loading zone list.
[03.20. - 21:18:41] [WORLD__LAUNCH] Removing pending launcher 1. Adding zone to active list.
[03.20. - 21:18:41] [WORLD__LS] Connecting to login server...
[03.20. - 21:18:42] [WORLD__LS] Connected to Loginserver: eqemulator.net:5998
[03.20. - 21:18:42] [WORLD__LS] Loginserver provided xxx.xxx.xxx.xxx as world address
[03.20. - 21:18:47] [WORLD__LAUNCH] zone: dynamic_01 reported state STARTED (1 starts)
[03.20. - 21:19:11] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts)
[03.20. - 21:19:22] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts)
[03.20. - 21:19:28] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts)
[03.20. - 21:19:36] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts)
[03.20. - 21:21:12] [WORLD__CLIENT] New connection from 192.168.111.11:1294
[03.20. - 21:21:12] [NET__IDENT_TRACE] 192.168.111.11:1294: First opcode 0x4dd0 did not match expected 0x2792
[03.20. - 21:21:12] [NET__IDENT_TRACE] 192.168.111.11:1294: Tried patch 6.2_world, and it did not match.
[03.20. - 21:21:12] [NET__IDENT_TRACE] 192.168.111.11:1294: First opcode 0x4dd0 did not match expected 0x2ec9
[03.20. - 21:21:12] [NET__IDENT_TRACE] 192.168.111.11:1294: Tried patch 6.2_zone, and it did not match.
[03.20. - 21:21:12] [NET__IDENT_TRACE] 192.168.111.11:1294: First opcode matched 0x4dd0 and length matched 464
[03.20. - 21:21:12] [NET__IDENTIFY] Identified stream 192.168.111.11:1294 with signature Titanium_world
[03.20. - 21:21:12] [WORLD__CLIENT] New client from 192.168.111.11:1294
[03.20. - 21:21:12] [WORLD__CLIENT] herold: Logged in. Mode=(CharSel)
[03.20. - 21:21:12] [WORLD__CLIENT] herold: LS Account #xxxxx
[03.20. - 21:21:29] [WORLD__ZONE] New TCP connection from 127.0.0.1:1494
[03.20. - 21:21:29] [WORLD__ZONE] New TCP connection from 127.0.0.1:1495
[03.20. - 21:21:29] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:1494
[03.20. - 21:21:29] [WORLD__ZONE] [1] Zone started with name dynamic_04 by launcher zone
[03.20. - 21:21:29] [WORLD__ZONE] [1] Auto zone port configuration.  Telling zone to use port 7000
[03.20. - 21:21:29] [WORLD__ZONE] New TCP connection from 127.0.0.1:1496
[03.20. - 21:21:29] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:1496
[03.20. - 21:21:29] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:1495
[03.20. - 21:21:29] [WORLD__ZONE] [3] Zone started with name dynamic_02 by launcher zone
[03.20. - 21:21:29] [WORLD__ZONE] [3] Auto zone port configuration.  Telling zone to use port 7001
[03.20. - 21:21:29] [WORLD__ZONE] [2] Zone started with name dynamic_01 by launcher zone
[03.20. - 21:21:29] [WORLD__ZONE] [2] Auto zone port configuration.  Telling zone to use port 7002
[03.20. - 21:21:29] [WORLD__ZONE] New TCP connection from 127.0.0.1:1497
[03.20. - 21:21:29] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:1497
[03.20. - 21:21:29] [WORLD__ZONE] [4] Zone started with name dynamic_05 by launcher zone
[03.20. - 21:21:29] [WORLD__ZONE] [4] Auto zone port configuration.  Telling zone to use port 7003
[03.20. - 21:21:29] [WORLD__ZONE] New TCP connection from 127.0.0.1:1498
[03.20. - 21:21:29] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:1498
[03.20. - 21:21:29] [WORLD__ZONE] [5] Zone started with name dynamic_03 by launcher zone
[03.20. - 21:21:29] [WORLD__ZONE] [5] Auto zone port configuration.  Telling zone to use port 7004
[03.20. - 21:22:48] [WORLD__CLIENT] herold: Attempting autobootup of gfaydark (54)
[03.20. - 21:23:25] [WORLD__ZONE] [5] Setting to 'gfaydark' (54)
[03.20. - 21:23:25] [WORLD__CLIENT] herold: Entering zone gfaydark (54)
[03.20. - 21:23:25] [WORLD__ZONE] [5] [gfaydark] Broadcasting a world time update
[03.20. - 21:23:25] [WORLD__ZONE] [5] [gfaydark] Setting to 'gfaydark' (54)
[03.20. - 21:23:25] [WORLD__CLIENT] herold: Sending client to zone gfaydark (54) at 192.168.111.1:7004
[03.20. - 21:23:26] [WORLD__CLIENT] herold: Client disconnected (not active in process)

Angelox · #5 03-20-2007, 07:35 AM

Quote:

Originally Posted by herold

Made the changes, but still ... "Client disconnected (not active in process)"

It always says that - nothing to worry about - if you are not getting into the game, check your ports;
Do you have a firewall up? if so, disable it for a while and see if it's a firewall problem

Zandig · #6 03-20-2007, 08:04 AM

Are you sure you have the correct LoginType set?

Using the MySQL query browser open up the PEQ database and load the 'variables' table. Then check the 'LoginType'. The value should be 'MiniLogin' (without quotes) for minilogin and 'public' (without quotes) for a public server.

PS:
Angelox - 777 posts! Lucky number.

- Zandig Slaytanic

herold · #7 03-20-2007, 08:23 PM

Logintype is set to Public and no firewall is used ... but if I understand it correctly, the error I am getting is a timeout? Is there any way to raise the time? Or will I have to live with the re-login's?

herold · #8 03-21-2007, 12:55 AM

But ... if you didn't get it from the previous post, the server is actually working ... only with the timeout problem.

Angelox · #9 03-21-2007, 07:58 AM

Quote:

Originally Posted by herold

Logintype is set to Public and no firewall is used ... but if I understand it correctly, the error I am getting is a timeout? Is there any way to raise the time? Or will I have to live with the re-login's?

- Again, forget the "Client disconnected (not active in process)" - this means nothing Important, and is not an error.
- The man said you should change LoginType from "Public" to 'MiniLogin' , if you are running a LAN set up and not going via the EqEmu LogIn , then you have to do this.
- And to honest with you, you're not being complete on your question/problem so you're making us think other things; "Or will I have to live with the re-login's?" this gives me the impression, you have another problem because you are logging in

- a Public-Login server means you use eqemu's login server. MiNilogin means you use "minilogin" in you LAN for loggin server ; what do you use?

I think your biggest problem is, you haven't researched much of anything, not even things like what type server you have. EqEmu forums has a wealth of information just waiting for you to find. We've been over/posted these basic problems many times over.
I almost cried when I thought the forums were gone, because I still search and find my answers right here, almost daily.

EDIT: do a forum search for "Timeout problem" and you might find some answers

**Doodman** · #10 03-21-2007, 04:13 PM

Quote:

Originally Posted by herold

1. All the internal (LAN) IP's used, shouldn't it be communicating thru external IP (WAN)?

LAN vs WAN is not a problem, the loginserver is smart enough to see that your client and your server are reaching it via the same external IP. So, it tells your client to use the internal IP instead. This avoids and issue a lot of routers have of allowing an internal machine access to the external address of that router.

herold · #11 03-22-2007, 06:32 AM

Sorry for being an "ignoramus" ... The server is actually working now, I am connecting thru EQemu's login-server (that is why I was confused about the LAN-ip's) and with regards to the "error", I discovered it is only a timeout occuring and that 4 out of 5 times I will still get thru. The last 1 out of 5 times I will get disconnected and will have to re-login thru EQemu's login-server ... but I guess I will have to live with that.

btw ... I found an entry in the PEQ database that controls the timeouts and altered til client-side timeout to be 13% higher. So hopefully it won't be so annoying anymore.

But thanks too you all for your willingness to help a n00b out.

/bow