-
|
Hello everyone, First of all, I understand that this is primarily the FEX-Emu GitHub repository and might not be the most specialized place to troubleshoot Project Zomboid dedicated server issues. However, since I'm using FEX-Emu to run it, I thought this would be a relevant place to post. If anyone could review the steps I've taken and offer assistance in resolving my problem, it would be incredibly appreciated. Thank you for your understanding and assistance. Let's get started! Here are the details about how I installed Project Zomboid Dedicated Server on an ARM64 Linux Server, specifically on an Oracle's Ampere VM.Standard.A1.Flex shape (4 cores, 24GB RAM) server, using FEX-Emu:Machine: Oracle Ampere VM.Standard.A1.Flex I SSH'd in as These were all the steps I followed (with the exception of the modification of the ProjectZomboid64.json file, explained at the end of this post).
Scenario 1: NO MODS Most of the time, I can successfully run a server with NO MODS. However, I occasionally encounter errors that prevent the server from running. The most common errors are: "A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007ffff7926638, pid=16491, tid=16491": This error indicates a segmentation fault (SIGSEGV) in the libc.so.6 library during the execution of the Project Zomboid server with FEX-Emu. It signals an unauthorized memory access issue. When this error occurs, the server's loading crashes. "ERROR: ld.so: object 'libjsig.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.": This repeated error indicates that the libjsig.so library specified in LD_PRELOAD is either not found or cannot be loaded. (This error is ignored most of the time, but I'm wondering how to resolve it.) Scenario 2: WITH MODS When I try to run the Dedicated Server WITH MODS, it usually crashes with the following error: When it manages to continue, it usually freezes during the server loading files stage, or it freezes after loading all the files (it takes 20+ minutes to become available). When a player tries to connect, the screen goes black (on the player's side), the server stops responding, and no player can connect (from another Project Zomboid client). I've modified the amount of available memory and tried routing some Java libraries manually, but it didn't resolve the problem. These are the .ini config file of the server, the ProjectZomboid64.json config, and the .log file for the last time I tried to run the server. Panitas.V3.ini.txt |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hey guys! I figured out how to solve the issue! I was importing the files incorrectly from my local server to the VPS. Here are the steps I followed, and now it's running stably with approximately 200 mods and 4 players at the same time (current max config is for 6 players). These steps should be followed after the ones I provided: Additional steps to import an existing server to Oracle Cloud: Inside the VPS console, start a new server with the desired name (using the console, add this at the end of the script: -servername NameOfYourServer.ini). Once it is running, join the server with a player to verify its functionality. Close the server, edit the .ini file on the VPS, and add the mod IDs (previously verified manually). Start the server again, ensure that at least one player joins to verify functionality, then exit and shut it down once more. Compress the following folders located inside the Zomboid folder on the local server: C:\Users\UserName\Zomboid\db Edit the .ini file on the VPS and add the necessary configurations to match those of the local server. Upload the previously compressed file to the VPS and extract it into the corresponding directories on the cloud server, replacing the existing files. With these additional steps, it's now working perfectly. Note: The error loading 'libjsig.so' has not yet been resolved. Good luck, guys! If you have any questions or issues, I'll be keeping an eye 🚀 |
Beta Was this translation helpful? Give feedback.
Hey guys! I figured out how to solve the issue! I was importing the files incorrectly from my local server to the VPS. Here are the steps I followed, and now it's running stably with approximately 200 mods and 4 players at the same time (current max config is for 6 players).
These steps should be followed after the ones I provided:
Additional steps to import an existing server to Oracle Cloud:
Inside the VPS console, start a new server with the desired name (using the console, add this at the end of the script: -servername NameOfYourServer.ini). Once it is running, join the server with a player to verify its functionality.
Close the server, edit the .ini file on the VPS, and add the mod I…