Jump to content
  • 0
Sign in to follow this  
Mehti

Guys Have a Big Problem on r40250

Question

Hello i still development my server files. All is good about r40250, but have a big fail.

When i kill metins and use bravery cape map got closed and cant login again. Need open core again and work.

Syserr have write this:


channel_core2 (map41- blue kingdom map here)


SYSERR: Feb  7 21:10:55.945392 :: pid_init: 
Start of pid: 31562

SYSERR: Feb  7 21:10:56.117897 :: main: Failed to Load ClientPackageCryptInfo File(package/)
SYSERR: Feb  7 21:10:59.341236 :: Show: cannot find sectree by 505207x921833 mapindex 1
SYSERR: Feb  7 21:10:59.341257 :: Show: cannot find sectree by 504856x920823 mapindex 1
SYSERR: Feb  7 21:10:59.341265 :: Show: cannot find sectree by 504760x921216 mapindex 1
SYSERR: Feb  7 21:10:59.341273 :: Show: cannot find sectree by 505653x920686 mapindex 1

channel core 3 (red1-and other here)


SYSERR: Feb  7 21:10:50.939900 :: pid_init: 
Start of pid: 31560

SYSERR: Feb  7 21:22:46.839802 :: Process: SEQUENCE 2a01f000 mismatch 0xaf != 0x64 header 254
SYSERR: Feb  7 21:22:46.839859 :: Process: SEQUENCE_LOG [UNKNOWN]-------------
	[254 : 0xaf]

SYSERR: Feb  7 21:40:29.199548 :: Process: SEQUENCE 303db000 mismatch 0xaf != 0x64 header 254
SYSERR: Feb  7 21:40:29.199582 :: Process: SEQUENCE_LOG [UNKNOWN]-------------
	[254 : 0xaf]

SYSERR: Feb  7 21:42:41.919480 :: GiveItemFromSpecialItemGroup: cannot find special item group 71160
SYSERR: Feb  7 21:58:34.599608 :: Process: SEQUENCE 303dc000 mismatch 0xaf != 0x64 header 254
SYSERR: Feb  7 21:58:34.599633 :: Process: SEQUENCE_LOG [UNKNOWN]-------------
	[254 : 0xaf]

core3


SYSERR: Feb  7 21:11:04.368030 :: Show: cannot find sectree by 505207x921833 mapindex 1
SYSERR: Feb  7 21:11:04.368072 :: Show: cannot find sectree by 504856x920823 mapindex 1
SYSERR: Feb  7 21:11:04.368087 :: Show: cannot find sectree by 504760x921216 mapindex 1
SYSERR: Feb  7 21:11:04.368102 :: Show: cannot find sectree by 505653x920686 mapindex 1

Auth


SYSERR: Feb  7 21:10:17.292441 :: socket_connect: HOST 127.0.0.1:14466, could not connect.
SYSERR: Feb  7 21:10:17.297543 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_ds.dat
SYSERR: Feb  7 21:10:17.297598 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_dss_box.dat
SYSERR: Feb  7 21:10:17.298620 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_w20_sound.dat
SYSERR: Feb  7 21:10:17.298688 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_w21_etc.dat
SYSERR: Feb  7 21:10:17.299976 :: ChildLoop: AsyncSQL: query failed: Table 'account.string' doesn't exist (query: SELECT name, text FROM string errno: 1146)
SYSERR: Feb  7 21:10:18.203115 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  7 21:10:18.231847 :: pid_deinit: 
End of pid

SYSERR: Feb  7 21:10:30.891857 :: pid_init: 
Start of pid: 31552

SYSERR: Feb  7 21:10:30.897919 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_ds.dat
SYSERR: Feb  7 21:10:30.898030 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_dss_box.dat
SYSERR: Feb  7 21:10:30.898918 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_w20_sound.dat
SYSERR: Feb  7 21:10:30.898973 :: LoadPackageCryptInfo: [PackageCryptInfo] Failed to load package/cshybridcrypt_metin2_patch_w21_etc.dat
SYSERR: Feb  7 21:54:16.290059 :: locale_find: LOCALE_ERROR: "°æÇèÄ¡ ¹èÀ²";
SYSERR: Feb  7 21:54:16.290081 :: locale_find: LOCALE_ERROR: "ÀüÁ¦±¹";
SYSERR: Feb  7 21:54:16.290096 :: locale_find: LOCALE_ERROR: "%sÀÇ %sÀÌ %d%% Áõ°¡Çß½À´Ï´Ù!";
SYSERR: Feb  7 21:54:16.809963 :: locale_find: LOCALE_ERROR: "°æÇèÄ¡ ¹èÀ²";
SYSERR: Feb  7 21:54:16.809994 :: locale_find: LOCALE_ERROR: "ÀüÁ¦±¹";
SYSERR: Feb  7 21:54:16.810017 :: locale_find: LOCALE_ERROR: "%sÀÇ %sÀÌ Á¤»óÀ¸·Î µ¹¾Æ¿Ô½À´Ï´Ù.";
SYSERR: Feb  7 21:54:37.380984 :: locale_find: LOCALE_ERROR: "°æÇèÄ¡ ¹èÀ²";
SYSERR: Feb  7 21:54:37.381002 :: locale_find: LOCALE_ERROR: "ÀüÁ¦±¹";
SYSERR: Feb  7 21:54:37.381016 :: locale_find: LOCALE_ERROR: "%sÀÇ %sÀÌ %d%% Áõ°¡Çß½À´Ï´Ù!";

I try upload other map attr, but still same when kill metins, core closed..

I try without diffs clean r40250, still same..

I hope some friends help me, and sorry for my bad english.


Regards, Mehti.

Share this post


Link to post

10 answers to this question

Recommended Posts

  • 0
DROP TABLE IF EXISTS `string`;
CREATE TABLE `string` (
  `name` varchar(64) NOT NULL DEFAULT '',
  `text` text,
  PRIMARY KEY (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
  • Love 5

Share this post


Link to post
  • 0

You are missing symlinks to share/package in some cores and you are missing csh files as well.

 

About the korean errors: save them to a text file and open it with Chrome then select Tools > Encoding > Korean and translate the output with Google Translate

  • Love 1

Share this post


Link to post
  • 0

Yes I made all, nothing. I trying vanilla's new core but same problem on killing metin.. I try now new mob_proto..

Share this post


Link to post
  • 0

Your mob proto file may wrong. Some program doesn't convert truth.

SYSERR: Feb  7 21:10:17.299976 :: ChildLoop: AsyncSQL: query failed: Table 'account.string' doesn't exist (query: SELECT name, text FROM string errno: 1146)

This error ; If string table not exist in your mysql account database, you're must be install it. 

Share this post


Link to post
  • 0

Your mob proto file may wrong. Some program doesn't convert truth.

SYSERR: Feb  7 21:10:17.299976 :: ChildLoop: AsyncSQL: query failed: Table 'account.string' doesn't exist (query: SELECT name, text FROM string errno: 1146)

This error ; If string table not exist in your mysql account database, you're must be install it. 

Thanks for reply, Already make this no changes, same when kill shit metins with much monster and core auto closed, need re open core to login map.

 

I see there much error on new revision, I think try with r34k if have a same problem %100 problem on my database or other stuffs.. 

Share this post


Link to post
  • 0
SYSERR: Feb  7 21:22:46.839802 :: Process: SEQUENCE 2a01f000 mismatch 0xaf != 0x64 header 254
SYSERR: Feb  7 21:22:46.839859 :: Process: SEQUENCE_LOG [UNKNOWN]-------------
    [254 : 0xaf]

Incompatible client rev

Share this post


Link to post
  • 0

I've never seen this error. Sometimes there are many error but you can fixed these error but slowly.. ;)

Share this post


Link to post
  • 0

Did you be sure to delete the files in the "package" folder?

Share this post


Link to post
  • 0
SYSERR: Feb  7 21:11:04.368030 :: Show: cannot find sectree by 505207x921833 mapindex 1
SYSERR: Feb  7 21:11:04.368072 :: Show: cannot find sectree by 504856x920823 mapindex 1
SYSERR: Feb  7 21:11:04.368087 :: Show: cannot find sectree by 504760x921216 mapindex 1
SYSERR: Feb  7 21:11:04.368102 :: Show: cannot find sectree by 505653x920686 mapindex 1

help

Share this post


Link to post
  • 0
Guest
SYSERR: Feb  7 21:11:04.368030 :: Show: cannot find sectree by 505207x921833 mapindex 1
SYSERR: Feb  7 21:11:04.368072 :: Show: cannot find sectree by 504856x920823 mapindex 1
SYSERR: Feb  7 21:11:04.368087 :: Show: cannot find sectree by 504760x921216 mapindex 1
SYSERR: Feb  7 21:11:04.368102 :: Show: cannot find sectree by 505653x920686 mapindex 1

help

I've this problem too in every core, help pls ^^

Share this post


Link to post

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
Sign in to follow this  
  • Recently Browsing   0 members

    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.