Jump to content
  • 0

Disconnect after loading screen


SoNiice

Question

Hi,

 

I got another error at my local server right now ._.

 

db syslog:

Jan 19 19:48:53.250000 :: [     1650] return 0/0/0 async 0/0/0
Jan 19 19:48:58.125000 :: [     1700] return 0/0/0 async 0/0/0
Jan 19 19:49:03.0 :: [     1750] return 0/0/0 async 0/0/0
Jan 19 19:49:07.875000 :: [     1800] return 0/0/0 async 0/0/0
Jan 19 19:49:12.718000 :: [     1850] return 0/0/0 async 0/0/0
Jan 19 19:49:17.609000 :: [     1900] return 0/0/0 async 0/0/0
Jan 19 19:49:22.468000 :: [     1950] return 0/0/0 async 0/0/0
Jan 19 19:49:27.343000 :: [     2000] return 0/0/0 async 0/0/0
Jan 19 19:49:32.250000 :: [     2050] return 0/0/0 async 0/0/0
Jan 19 19:49:37.125000 :: [     2100] return 0/0/0 async 0/0/0
Jan 19 19:49:42.0 :: [     2150] return 0/0/0 async 0/0/0
Jan 19 19:49:47.906000 :: [     2200] return 0/0/0 async 0/0/0
Jan 19 19:49:51.750000 :: [     2250] return 0/0/0 async 0/0/0
Jan 19 19:49:52.437000 :: socket_read: WSAGetLastError returned 10054
SYSERR: Jan 19 19:49:52 :: socket_read: about to lose connection
SYSERR: Jan 19 19:49:52 :: CPeerBase::Recv: socket_read failed Result too large
SYSERR: Jan 19 19:49:52 :: CClientManager::Process: Recv failed
Jan 19 19:49:52.515000 :: Connection closed. (host: 127.0.0.1)
Jan 19 19:49:52.515000 :: ItemIDRange: returned. 10000001 ~ 20000000
Jan 19 19:49:53.62000 :: ItemIDRange: Build: 10000001 ~ 20000000 start:10000001

core syslog:

Jan 19 19:46:58.718000 :: InputDB::login_success: soniice
Jan 19 19:46:59.593000 :: player_select: login: soniice index: 0
Jan 19 19:47:00.937000 :: PK_MODE: WARRIOR 3
Jan 19 19:47:00.953000 :: PLAYER_LOAD: WARRIOR PREMIUM 0 1514686024, LOGGOFF_INTERVAL 1421693219 PTR: 0A1168C8
Jan 19 19:47:00.0 :: InputDB: player_load WARRIOR 51839x166836x0 LEVEL 1 MOV_SPEED 100 JOB 0 ATG 14 DFG 4 GMLv 0
Jan 19 19:47:00.15000 :: ITEM_LOAD: COUNT WARRIOR 0
Jan 19 19:47:00.15000 :: QUEST_LOAD: count 0
Jan 19 19:47:00.625000 :: [QUERY : LONG INTERVAL(OverSec 0.625000)] : INSERT DELAYED INTO log (type, time, who, x, y, what, how, hint, ip) VALUES('CHARACTER', NOW(), 1055, 51839, 166836, 0, 'LOGIN', '127.0.0.1 0 1 21 0', '127.0.0.1')
Jan 19 19:47:11.937000 :: GLOBAL_TIME: Jan 19 19:47:11 time_gap 0
Jan 19 19:48:09.421000 :: GLOBAL_TIME: Jan 19 19:48:09 time_gap 0
Jan 19 19:48:52.468000 :: PING_EVENT: no pong 127.0.0.1
Jan 19 19:48:52.468000 :: DISCONNECT: WARRIOR (DESC::~DESC)
Jan 19 19:48:52.531000 :: SAVE: WARRIOR 51839x166836
Jan 19 19:48:52.531000 :: QUEST clear timer 0
Jan 19 19:48:52.546000 :: SYSTEM: closing socket. DESC #576
Jan 19 19:48:54.875000 :: SYSTEM: new connection from [127.0.0.1] fd: 604 handshake 3190464759 output input_len 0, ptr 0A27F050
Jan 19 19:48:54.265000 :: SYSTEM: closing socket. DESC #604
Jan 19 19:49:08.906000 :: GLOBAL_TIME: Jan 19 19:49:07 time_gap -1

My character is getting disconnected right after the loading screen. Syserrs are totally empty.

Link to comment
  • Answers 1
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

1 answer to this question

Recommended Posts

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Read our Rules
  • Activity

    1. 2

      [Python] Code Translator 2 to 3

    2. 0

      bug gaya

    3. 5

      Fix Core Crash (unused serverside packet)

    4. 45

      Chest Drop View

    5. 0

      How to add Python 3.9 script?

    6. 15

      Metin2 Download Center - Specifications & Documentation

    7. 5

      Fix Core Crash (unused serverside packet)

    8. 45

      Chest Drop View

    9. 5

      Fix Core Crash (unused serverside packet)

  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.