Jump to content
  • 0

Client don't working


Slindex

Question

Hello!

I did downloaded that serverfiles based on FreeBSD and replaced by Vanilla bd and game core.

After that i did downloaded that client and edited serverinfo.py - i  did changed ports that are in the server config:

/usr/home/game/g1/auth/CONFIG

PORT: 11002

REGION_AUTH_SERVER_DICT = {
    0 : {
        1 : { 'ip':'25.2.116.100', 'port':11002, },
        2 : { 'ip':'25.2.116.100', 'port':41001, }, (it doesn't matter)
        }    
}

 

and

/usr/home/game/channel1/core1

PORT: 13000

SERVER1_CHANNEL_DICT = {
    1:{'key':11,'name':'CH1   ','ip':'25.2.116.100','tcp_port':13000,'udp_port':13000,'state':STATE_NONE,},
    2:{'key':12,'name':'CH2   ','ip':'25.2.116.100','tcp_port':32000,'udp_port':32000,'state':STATE_NONE,}, (it doesn't matter)
    3:{'key':13,'name':'CH3   ','ip':'25.2.116.100','tcp_port':33000,'udp_port':33000,'state':STATE_NONE,}, (it doesn't matter)
    4:{'key':14,'name':'CH4   ','ip':'25.2.116.100','tcp_port':34000,'udp_port':34000,'state':STATE_NONE,}, (it doesn't matter)
}

 

 

There is my full serverinfo.py:

import app

app.ServerName = None

STATE_NONE = '...'
        
STATE_DICT = {
    0 : '....',
    1 : 'NORM',
    2 : 'BUSY',
    3 : 'FULL'    }

SERVER1_CHANNEL_DICT = {
    1:{'key':11,'name':'CH1   ','ip':'25.2.116.100','tcp_port':13000,'udp_port':13000,'state':STATE_NONE,},
    2:{'key':12,'name':'CH2   ','ip':'25.2.116.100','tcp_port':32000,'udp_port':32000,'state':STATE_NONE,},
    3:{'key':13,'name':'CH3   ','ip':'25.2.116.100','tcp_port':33000,'udp_port':33000,'state':STATE_NONE,},
    4:{'key':14,'name':'CH4   ','ip':'25.2.116.100','tcp_port':34000,'udp_port':34000,'state':STATE_NONE,},
}

SERVER2_CHANNEL_DICT = {
    1:{'key':11,'name':'CH1   ','ip':'25.2.116.100','tcp_port':31000,'udp_port':31000,'state':STATE_NONE,},
    2:{'key':12,'name':'CH2   ','ip':'25.2.116.100','tcp_port':32000,'udp_port':32000,'state':STATE_NONE,},
    3:{'key':13,'name':'CH3   ','ip':'25.2.116.100','tcp_port':33000,'udp_port':33000,'state':STATE_NONE,},
    4:{'key':14,'name':'CH4   ','ip':'25.2.116.100','tcp_port':34000,'udp_port':34000,'state':STATE_NONE,},
}
    
REGION_NAME_DICT = {
    0 : "GERMANY",        
}

REGION_AUTH_SERVER_DICT = {
    0 : {
        1 : { 'ip':'25.2.116.100', 'port':11002, },
        2 : { 'ip':'25.2.116.100', 'port':41001, },
        }    
}

REGION_DICT = {
    0 : {
        1 : { 'name' : 'ololol', 'channel' : SERVER1_CHANNEL_DICT, },
        2 : { 'name' : 'Test Root', 'channel' : SERVER2_CHANNEL_DICT, },
        },
}

MARKADDR_DICT = {
    10 : { 'ip' : '25.2.116.100', 'tcp_port' : 13000, 'mark' : '10.tga', 'symbol_path' : '10', },
    20 : { 'ip' : '25.2.116.100', 'tcp_port' : 13000, 'mark' : '20.tga', 'symbol_path' : '20', },
    }

TESTADDR = { 'ip' : '25.2.116.100', 'tcp_port' : 50000, 'udp_port' : 50000, }

#DONE

So, and when i writing incorrect login and password - client say that login or password are incorrect.

But when i writing correctly login and password - client say that error with connecting to server.

Any solutions? :huh:

 

P.S. Sorry, for my english, i'm from Russia.

 

 

Link to comment

14 answers to this question

Recommended Posts

  • 0

After cleaning syserr and rebooting (2 time). Now it looks like this:

SYSERR: Jul 24 06:10:33 :: pid_init:
Start of pid: 874

SYSERR: Jul 24 06:10:34 :: Boot: item table size error
SYSERR: Jul 24 06:10:34 :: pid_deinit:
End of pid

SYSERR: Jul 24 06:16:26 :: pid_init:
Start of pid: 873

SYSERR: Jul 24 06:16:27 :: Boot: item table size error
SYSERR: Jul 24 06:16:27 :: pid_deinit:
End of pid

 

 

Link to comment
  • 0

Also

/usr/home/game/g1/db

syserr gives me

SYSERR: Jul 24 06:14:01 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jul 24 06:14:02 :: pid_deinit:
End of pid

SYSERR: Jul 24 06:16:22 :: pid_init:
Start of pid: 867

SYSERR: Jul 24 06:16:22 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jul 24 06:16:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Table './player/quest' is marked as crashed and last (automatic?) repair failed
query: SELECT szName, lValue FROM quest WHERE dwPID = 0
SYSERR: Jul 24 06:16:22 :: Load:  DirectQuery failed(SELECT login FROM block_exception)
SYSERR: Jul 24 06:16:24 :: ChildLoop: AsyncSQL: query failed: Table './player/quest' is marked as crashed and last (automatic?) repair failed (query: REPLACE INTO quest (dwPID, szName, szState, lValue) VALUES(0, 'oxevent_status', '', 0) errno: 144)
SYSERR: Jul 24 06:16:26 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 06:16:27 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 06:16:28 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 06:16:29 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 06:16:30 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 06:16:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 06:16:32 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 06:16:33 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 06:16:34 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 06:16:35 :: Process: FDWATCH: peer null in event: ident 21

When i try to fix quest bd navicat gives me 3 errors:
947d5cb35367.png

Link to comment
  • 0
  • VIP

SYSERR: Jul 24 06:10:34 :: Boot: item table size erro

 

You have a wrong item_proto, maybe damaged or from another rev

 

About your Navicat error, you probably have wrong permissions on the files. Do this in putty:

 

chown -R mysql /var/db/mysql

 

Then try to repair it again

  • Love 1

 

 

Link to comment
  • 0
  • Bot
ee /usr/local/etc/rc.d/mysql-server
 
change mysqluser="mysql" to  mysqluser="root"
 
If it is already on root maybe you should change privilages to 0777 via fttp on important files .
 
If you could give me your serverfiles rev i can give you official item proto .
Link to comment
  • 0

Thank you Shogun, after

chown -R mysql /var/db/mysql

I can fix my bd files.

Also, after crearing syserr and rebooting it gives error again.

 

/usr/home/game/channel1/core1

SYSERR: Jul 24 16:39:01 :: pid_init:
Start of pid: 1362

SYSERR: Jul 24 16:39:02 :: Boot: item table size error
SYSERR: Jul 24 16:39:02 :: pid_deinit:
End of pid

 

 

/usr/home/game/g1/auth

SYSERR: Jul 24 16:38:59 :: pid_init:
Start of pid: 1359

(I think no errors here)

 

/usr/home/game/g1/db

SYSERR: Jul 24 16:38:57 :: pid_init:
Start of pid: 1356

SYSERR: Jul 24 16:38:57 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jul 24 16:38:57 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Jul 24 16:39:01 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 16:39:02 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 16:39:03 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 16:39:04 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 16:39:05 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 16:39:06 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 16:39:07 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 16:39:08 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jul 24 16:39:09 :: ProcessPackets: Unknown header (header: 139 handle: 0 length: 3)
SYSERR: Jul 24 16:39:10 :: Process: FDWATCH: peer null in event: ident 21

But in syslog i see how i try to sign in:

Jul 24 16:45:04 :: AUTH_LOGIN id(2) login(slindexin) social_id() login_key(2058615781), client_key(700853983 305088486 1578718813 1366631406)
Jul 24 16:45:07 :: [     3700] return 0/0/0 async 0/0/0
Jul 24 16:45:12 :: [     3750] return 0/0/0 async 0/0/0

 

Link to comment
  • 0

 

ee /usr/local/etc/rc.d/mysql-server
 
change mysqluser="mysql" to  mysqluser="root"
 
If it is already on root maybe you should change privilages to 0777 via fttp on important files .
 
If you could give me your serverfiles rev i can give you official item proto .

 

 

I see only mysql_user="mysql". Is it the same thing?

UPD: How i can contacts with u?

Link to comment
  • 0

log.txt from client:

0724 15:40:36769 :: 알림: 파일 모드입니다.
0724 15:40:00002 ::
0724 15:40:00002 :: ## Network - OffLine Phase ##
0724 15:40:00002 ::
0724 15:40:00020 :: importing from pack debugInfo
0724 15:40:00021 :: importing from pack localeInfo
0724 15:40:00029 :: importing from pack constInfo
0724 15:40:00034 :: importing from pack mouseModule
0724 15:40:00037 :: importing from pack ui
0724 15:40:00061 :: importing from lib _weakref
0724 15:40:00062 :: importing from pack networkModule
0724 15:40:00064 :: importing from pack playerSettingModule
0724 15:40:00093 :: importing from pack emotion
0724 15:40:00098 :: importing from pack uiPhaseCurtain
0724 15:40:00100 :: importing from pack uiCandidate
0724 15:40:00103 :: importing from pack musicInfo
0724 15:40:00104 :: importing from pack stringCommander
0724 15:40:00346 :: NEWMAIN STREAM ----------------------------------------------------------------------------0724 15:40:00346 ::
0724 15:40:00346 :: NEW POPUP DIALOG ----------------------------------------------------------------------------0724 15:40:00346 ::
0724 15:40:00346 :: importing from pack exception
0724 15:40:00346 :: importing from lib errno
0724 15:40:00347 :: ===== Load Script File : UIScript/PopupDialog.py0724 15:40:00347 ::
0724 15:40:00347 :: importing from pack uiScriptLocale
0724 15:40:00354 :: NEW CURTAIN  ----------------------------------------------------------------------------0724 15:40:00354 ::
0724 15:40:00354 ::
0724 15:40:00354 :: ## Network - OffLine Phase ##
0724 15:40:00354 ::
0724 15:40:00354 :: importing from pack introLogin
0724 15:40:00363 :: importing from pack serverInfo
0724 15:40:00364 :: importing from pack uiCommon
0724 15:40:00367 :: importing from lib time
0724 15:40:00367 :: importing from pack ServerCommandParser
0724 15:40:00368 :: NEW LOGIN WINDOW  ----------------------------------------------------------------------------0724 15:40:00368 ::
0724 15:40:00368 :: LOGIN WINDOW OPEN ----------------------------------------------------------------------------0724 15:40:00368 ::
0724 15:40:00368 :: ===== Load Script File : locale/de/ui/LoginWindow.py0724 15:40:00368 ::
0724 15:40:00541 :: 자동 로그인을 하시려면loginInfo.py파일을 작성해주세요

내용:
================================================================
addr=주소
port=포트
id=아이디
pwd=비밀번호
slot=캐릭터 선택 인덱스 (없거나 -1이면 자동 선택 안함)
autoLogin=자동 접속 여부
autoSelect=자동 접속 여부
localeInfo=(ymir) LC_Ymir 일경우 ymir로 작동. 지정하지 않으면 korea로 작동
0724 15:40:00541 ::
0724 15:40:00545 :: Succeed connecting.
0724 15:40:05430 :: HANDSHAKE RECV 104942 0
0724 15:40:05430 :: HANDSHAKE SEND 104942
0724 15:40:05513 :: HANDSHAKE RECV 105022 40
0724 15:40:05513 :: HANDSHAKE SEND 105102
0724 15:40:05595 :: HANDSHAKE RECV 105101 0
0724 15:40:05595 :: HANDSHAKE SEND 105101
0724 15:40:05677 :: HANDSHAKE RECV 105181 40
0724 15:40:05677 :: HANDSHAKE SEND 105261
0724 15:40:05759 :: KEY_AGREEMENT RECV 256
0724 15:40:05794 :: KEY_AGREEMENT SEND 256
0724 15:40:05843 :: KEY_AGREEMENT_COMPLETED RECV

 

 

Link to comment
  • 0

As i said before, if i replace vanilla core to default (by sf) client gives an error

 

a504ff987159.png

 

Да/Нет = Yes/No in Russian

 

And after a few seconds client gives me 2nd window:

 

97a050b7c176.png

 

 

But if i replace default core to vanilla, client will give me error with connection to server.

 

IMPORTANT: That error appear only when I enter the correct login and password. In other cases, it writes about the wrong login/password.

Link to comment

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


×
×
  • 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.