How to Read and Solve Syserr Errors in Metin2 Pvp Servers?
It is the cause of almost all technical problems encountered in Metin2 PVP server management, such as core (channel) drops, game kicks, NPC windows not opening or systems not working. syserr reserved in files. In this guide, you'll learn how to read syserr files to detect server-side errors and how to fix the most common errors.
1. Where to Find Syserr Files?
In the Metin2 files structure, each core has its own error log. Depending on the stage at which the problem occurs, the syserr file in the relevant directory should be examined:
- For Login Problems (Auth):
/usr/game/cores/auth/syserr - For Channel Problems (CH1, CH2 etc.):
/usr/game/cores/channel1/syserr - For Common Maps (Game99):
/usr/game/cores/game99/syserr - For Database Errors (DB):
/usr/game/cores/db/syserr
2. Most Common Syserr Errors and Solutions
Syserr files work with log logic and the bottom lines always show the most recent error. Here are the most popular error patterns:
A) Database Error Giving Resume/Refuse (C_QueryResult)
DirectQuery failed(_query_...) - table 'player.item_proto' doesn't exist
Solution: This error indicates that the table being attempted to be queried has been deleted in Navicat or has an incorrect name. You need to restore the table from backup (backup SQL file) or repair it via Navicat.
B) Bad Column or Value Error (GetServerFactor)
Putty / Game: ConvertStringToTable() - ... Column count is illogical
Solution: on Navicatitem_protoormob_protoIt indicates that you left a missing column (tab key shift) when adding a new row to the tables or if you are using txt-based files, you disrupted the row order in the proto files. Check the last line you added.
C) Quest Not Working Error (QUEST)
syserr: QUEST: wrong argument count for ...
Solution: A missing or incorrect argument has been used in the functions of a lua or quest file you uploaded to the server. You must open the relevant quest code, correct the parameters in parentheses, and read it again via Putty.
3. Things to Consider When Reading Syserr
- Not every syserr output is a critical error. at the beginning
[NOTICE]or lines containing warnings for informational purposes only will not crash the game. - If your channels (CHs) are closed suddenly, the syserr line immediately before the second of the closing "CRASH" or "Fatal Error" You should search for the phrases.
This article is specially prepared for PvPServer.
