MiniLogin server
Hi i have got my server to the point of hitting enter world but as soon as i hit enter world on my character in world.exe it says "client disconnected (not active process) anyone had this problem and solved this?? i am running the server on the same machine as im trying to play if this is any help
|
here is what is in my world.exe
[Debug] Starting Log: logs/eqemu_debug_world_3720.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_3720.log [Status] Using database 'peq' at localhost:3306 [Debug] [WORLD__INIT] HTTP world service disabled. [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=54307 [Debug] [WORLD__INIT] Loading guilds.. [Debug] [RULES__CHANGE] Loading rule set 'default' (2) [Debug] [WORLD__INIT] Loaded default rule set 'default' [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] Setting World to MiniLogin Server type [Debug] [WORLD__LS] Connected to Loginserver: localhost:5999 [Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2769 [Debug] [WORLD__CONSOLE] New launcher from 127.0.0.1:2769 [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__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts) [Debug] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts) [Debug] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts) [Debug] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts) [Debug] [WORLD__LAUNCH] zone: dynamic_06 reported state STARTED (1 starts) [Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2774 [Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2775 [Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2776 [Debug] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:2776 [Debug] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:2775 [Debug] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:2774 [Debug] [WORLD__ZONE] [3] Zone started with name dynamic_01 by launcher zone [Debug] [WORLD__ZONE] [3] Auto zone port configuration. Telling zone to use por t 7000 [Debug] [WORLD__ZONE] [1] Zone started with name dynamic_03 by launcher zone [Debug] [WORLD__ZONE] [1] Auto zone port configuration. Telling zone to use por t 7001 [Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2777 [Debug] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:2777 [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 7002 [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__ZONE] New TCP connection from 127.0.0.1:2780 [Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2781 [Debug] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:2781 [Debug] [WORLD__CONSOLE] New zoneserver #6 from 127.0.0.1:2780 [Debug] [WORLD__ZONE] [6] Zone started with name dynamic_05 by launcher zone [Debug] [WORLD__ZONE] [6] Auto zone port configuration. Telling zone to use por t 7004 [Debug] [WORLD__ZONE] [5] Zone started with name dynamic_06 by launcher zone [Debug] [WORLD__ZONE] [5] Auto zone port configuration. Telling zone to use por t 7005 [Debug] [WORLD__CLIENT] New connection from 10.10.2.254:2783 [Debug] [NET__IDENT_TRACE] 10.10.2.254:2783: First opcode 0x4dd0 did not match e xpected 0x2792 [Debug] [NET__IDENT_TRACE] 10.10.2.254:2783: Tried patch 6.2_world, and it did n ot match. [Debug] [NET__IDENT_TRACE] 10.10.2.254:2783: First opcode 0x4dd0 did not match e xpected 0x2ec9 [Debug] [NET__IDENT_TRACE] 10.10.2.254:2783: Tried patch 6.2_zone, and it did no t match. [Debug] [NET__IDENT_TRACE] 10.10.2.254:2783: First opcode matched 0x4dd0 and len gth matched 464 [Debug] [NET__IDENTIFY] Identified stream 10.10.2.254:2783 with signature Titani um_world [Debug] [WORLD__CLIENT] New client from 10.10.2.254:2783 [Debug] [WORLD__CLIENT] ashley: Logged in. Mode=(CharSel) [Debug] [WORLD__CLIENT] ashley: MiniLogin Account #13 [Debug] [WORLD__CLIENT] ashley: Attempting autobootup of qcat (45) [Debug] [WORLD__ZONE] [6] Setting to 'qcat' (45) [Debug] [WORLD__CLIENT] ashley: Entering zone qcat (45) [Debug] [WORLD__ZONE] [6] [qcat] Setting to 'qcat' (45) [Debug] [WORLD__CLIENT] ashley: Sending client to zone qcat (45) at 10.10.2.254: 7004 [Debug] [WORLD__CLIENT] ashley: Client disconnected (not active in process) |
Client disconnected (not in active process)
means that the server passed the client off to another process and therefore it is not in the active process anymore. This is normal for the world server to do because the player plays in the zone. So, the login server passes the client off to the world server. The world server handles character selection and when you hit enter world, the world server tells the launcher to startup the required zone if it isn't already and then passes the client to the zone server. If the zone does not load the character within the specified timeout period, the client will get booted back to the login screen. |
Hi thats what keeps happening to me i keep getting kicked back to the login screen any way i can increase the timeout time?? thanks for the replay
|
Double check your config files for the IP addresses you are using. If you are only using a single machine and not networking it on a lan, make all of the ip addresses everywhere in the config and eqhosts.txt files 127.0.0.1 (or localhost). Otherwise insure that all of them except the database are not 127.0.0.1 (or localhost), but rather your network card's IP address.
If after that you are still having a problem, double check your work for typos and verify that you followed the setup guide completely. |
There is a way to modify the timeout for the zone when launching.
Bring up your SQL browser and check out the two rules tables. You will see the entries to modify. As an aside, I was having a very similar problem on one of 3 machines on my network. Turns out, the kids had moved some memory from what it was originally. Once I returned the offending machine to 512 rather than 256, it was no longer chunking down the memory while trying to load in sections. Any such config problems for your machine? I would hate to see you go through all the massaging (read I had to by my database dinner first) to get the client to respond properly. |
Just tried changing all the IP address but the one's pointing to the Database still same problem and i can't seem to find the right querys in the sql database
|
Code:
INSERT INTO rule_valuesUp them however you like. That thread also references everything I was attempting for the same symptoms. |
| All times are GMT -4. The time now is 07:48 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.