SkiperTheBoss
New member
- Joined
- Feb 19, 2024
- Messages
- 14
Hello everyone,
I've developed a website for managing my Palworld Server, making it easier for my friends and me to control the server. You can see the current state of the page here:
. The site was built using Node.js, utilizing the child_process.execFile() function for operations.
Initially, I attempted to start the server using PalServer.exe. However, this approach didn't offer full control, as PalServer.exe launches another process named PalServer-Win64-Test-Cmd.exe (there's also a PalServer-Win64-Test.exe, but I'm unclear on the differences). This required implementing a wait mechanism to ensure the process started correctly and periodically checking if the process was still running.
Subsequently, I experimented with directly running PalServer-Win64-Test-Cmd.exe, bypassing PalServer.exe, which proved successful. As a result, I developed a second version of the management system that functions flawlessly.
As depicted in the provided image, there are several methods to restart the server on the website. One such method is the Remote Shutdown, which executes an RCON Script to send the /DoExit command to the server. This process triggers an exit call in Node.js, returning an exit code of 3.
Currently, I'm encountering an issue where the server unexpectedly shuts down after 1-2 hours of operation, also returning an exit code of 3. I'm seeking advice, suggestions, or insights from anyone who may have experienced similar issues or has ideas on how to resolve this problem.
I've developed a website for managing my Palworld Server, making it easier for my friends and me to control the server. You can see the current state of the page here:
Initially, I attempted to start the server using PalServer.exe. However, this approach didn't offer full control, as PalServer.exe launches another process named PalServer-Win64-Test-Cmd.exe (there's also a PalServer-Win64-Test.exe, but I'm unclear on the differences). This required implementing a wait mechanism to ensure the process started correctly and periodically checking if the process was still running.
Subsequently, I experimented with directly running PalServer-Win64-Test-Cmd.exe, bypassing PalServer.exe, which proved successful. As a result, I developed a second version of the management system that functions flawlessly.
As depicted in the provided image, there are several methods to restart the server on the website. One such method is the Remote Shutdown, which executes an RCON Script to send the /DoExit command to the server. This process triggers an exit call in Node.js, returning an exit code of 3.
Currently, I'm encountering an issue where the server unexpectedly shuts down after 1-2 hours of operation, also returning an exit code of 3. I'm seeking advice, suggestions, or insights from anyone who may have experienced similar issues or has ideas on how to resolve this problem.
Last edited: