PvP Server Kiralama & Oyun Sunucuları
0 Giriş Yap Kayıt Ol

Solution to "Core Dumped" Error on Metin2 Servers

Yazdır

Solution to "Core Dumped" Error on Metin2 Servers

One of the errors most feared by Metin2 PVP server administrators and causing sudden closure of channels (CH) "Core Dumped" (Core Crash) comes. This error occurs when the server shuts down itself as a result of encountering a faulty code that it cannot process in memory (RAM), an invalid database query, or a corrupt file. Below you can find how to solve this problem step by step.

Step 1: Detecting Which File Crashed

When you get the Core dumped error, the server is placed in the crashed folder.game.coreordb.coreIt leaves a large file named . First we need to find the source of the problem:

  • Connect to your server with Filezilla and navigate to the directory where the channels are located (Ex:/usr/game/cores/channel1).
  • in folder game.core If you see the file, the error is caused by an in-game system (C++ source codes or the use of an incorrect map/item).
  • if/usr/game/cores/dbin db.core If you see it, the problem is completely caused by a corrupt table or incorrect proto entry in the Navicat database.

Step 2: Capturing Erroneous Syserr Output

The Core Dumped error leaves a critical log in the syserr.txt file at the exact second it occurs. To solve the error:

  1. In the folder that gives core dumped (Ex: channel1) syserr Open the file.
  2. Going to the bottom lines of the fileCRASH,Segmentation FaultorAssertion failedSearch for the words.
  3. The function name or item code written here will directly show you which system crashed the server. Check by disabling the last system or quest you added.

Step 3: Analyzing Core File with GDB (Technical Method)

If nothing is written in the syserr file, you can use GDB (GNU Debugger) on FreeBSD to find the line of C++ code causing the crash:

  • Enter the directory where the crash occurred via Putty:
    cd /usr/game/cores/channel1
  • Start the debugger by running the following command in the terminal:
    gdb game game.core
  • When the command line is opened, it appears on the screenbtorwhereType it and press Enter.
  • In the list that will appear on the screen, the source code file and line number that caused the error (e.g.:char_item.cpp:1452) will be listed. You should re-build by correcting this line in the Source section.

Step 4: Review Common Mistakes

If you haven't made any code changes recently, check these two cases:

  • Table Corruption: The tables in the Navicat player database may be corrupted. Selecting all tables and right clicking Maintain -> Repair Tables -> Extended do it.
  • Stack Overflow: A bug made by the players (e.g. unlimited hitting cheat, pet bug) may inflate the server's memory and cause core dumping. Use up-to-date protection infrastructures (Guard).

This article is specially prepared for PvPServer.

Bu cevap yeterince yardımcı oldu mu?

Oyla

overlay spinner