Host Your Own Ark Survival Ascended Server in LINUX with my Management Script!

[BasemanX]

So still the same issue.

But I did find this when looking into the crashstack logs.

cat 11.28-19.16.11.crashstack 
LowLevelFatalError [File:E:\dave_WC-PURPLERAIN_NVidia\Projects\ShooterGame\Source\ShooterGame\Private\ShooterGameInstance.cpp] [Line: 705] 
Requested mods failed to load on server.

CL: 452763 
0x000000017401329e kernelbase.dll!RaiseException() [Z:\usr\src\packages\BUILD\dlls\kernelbase\debug.c:302]
0x0000000143c79c77 ArkAscendedServer.exe!UnknownFunction []
0x0000000143c26220 ArkAscendedServer.exe!UnknownFunction []
0x00000001433f9ab8 ArkAscendedServer.exe!UnknownFunction []
0x0000000140e306bb ArkAscendedServer.exe!UnknownFunction []
0x0000000140e22de6 ArkAscendedServer.exe!UnknownFunction []

From a quick Google search I found this on reddit from 1 day ago:

 

Quote

Bwuaaa

·1 day ago

use the following console command: ark.ver****** 1 (i dont remember the full command, but ark.ver should autofill)

(you need to use this each time you boot the game)

edit: ark.VertexCountScaling 1

But this seems to be some client side stuff as you will have to enter this into console in the game.

Edited November 29, 2023 by BasemanX

[acekorneya]

4 minutes ago, BasemanX said:

So still the same issue.

But I did find this when looking into the crashstack logs.

cat 11.28-19.16.11.crashstack 
LowLevelFatalError [File:E:\dave_WC-PURPLERAIN_NVidia\Projects\ShooterGame\Source\ShooterGame\Private\ShooterGameInstance.cpp] [Line: 705] 
Requested mods failed to load on server.

CL: 452763 
0x000000017401329e kernelbase.dll!RaiseException() [Z:\usr\src\packages\BUILD\dlls\kernelbase\debug.c:302]
0x0000000143c79c77 ArkAscendedServer.exe!UnknownFunction []
0x0000000143c26220 ArkAscendedServer.exe!UnknownFunction []
0x00000001433f9ab8 ArkAscendedServer.exe!UnknownFunction []
0x0000000140e306bb ArkAscendedServer.exe!UnknownFunction []
0x0000000140e22de6 ArkAscendedServer.exe!UnknownFunction []

From a quick Google search I found this on reddit from 1 day ago:

 

 

IF you remove the mod does it work if that the case is the mods that are crashing it an not letting start up 

[BasemanX]

The thing is this isn't a mod that I have installed. I believe this is something which is in the game files of the server. Here are the results when looking for that CL number mentioned:
 

grep -Rnw 'arkserver/' -e '452763'
grep: arkserver/ASA/Binaries/Win64/ArkAscendedServer.exe: binary file matches
grep: arkserver/ASA/Binaries/Win64/ArkAscendedServer.pdb: binary file matches

So this is something to do with ASA itself.

[BasemanX]

Just for the sake of testing, I created a new folder and did a fresh install without any mods. It worked perfectly fine.

And then I started looking into the mods. It turns out that the mod Deinonychus with ID 941658 has been deleted from Curseforge.

So to anyone experiencing the same in the future, start googling for "ark mod id" (for example: ark mod 941658) and see if the mods you use still exists on Curseforge.

Thank you @acekorneya for your help, and sorry for not discovering this sooner. It seems your new update and the deletion of the mod from Curseforge happened almost at the same time. Anyway, all good now! Your docker ASA server is working fine! 😀 Thank you for your time and effort!

[BasemanX]

@acekorneya Do you know if it is possible for the docker container give information on which mod(s) are failing if it suddenly doesn't exists on Curseforge anymore? If it is possible to put this information in a logfile to make it easier for people to see what prevents the server from starting.

Edited November 29, 2023 by BasemanX

[acekorneya]

30 minutes ago, BasemanX said:

@acekorneya Do you know if it is possible for the docker container give information on which mod(s) are failing if it suddenly doesn't exists on Curseforge anymore? If it is possible to put this information in a logfile to make it easier for people to see what prevents the server from starting.

Yeah, that would be a nice addition. I will look into it to see if it is possible to somehow show the user why the server couldn't start up or if it was because of a mod issue, etc.

[acekorneya]

On 11/21/2023 at 2:30 PM, HylianSeven said:

I managed to figure out my issue I mentioned earlier was a case of PEBCAK (Problem Exists Between Chair And Keyboard): One of the stick of RAM in my machine had died and I had to remove it, and I thought they were both 16GB. I misread, and they were part of a pack of two 8GB sticks, so I was down to 8GB and the server would not start.

However I'm having another issue right now, and this could be an issue with ASA itself and not necessarily the docker image. My server does not show up in the list, yet I know the ports are forwarded and on top of that I can reach it through a dynamic DNS URL. I see it on BattleMetrics.com too. I can join the server by opening the console and typing "open ipOrURL". However I want the server to be password protected, so I modified the GameUserSettings.ini and added ServerPassword=mypassword. I still can't see it in the list (but still see it on BattleMetrics), but any attempt to join it always results in "Invalid Password". This even happens with the correct password, I attempt to join from console by typing "open ipOrURL?passwordHere"

 

Any ideas? Is this just an ASA problem?

just added the ability for user to be able to set up a server password but i believed you issue was that you needed to check on the bottom "Show Password Protected Servers" to be able to see server with password set up 

[acekorneya]

Changelog

New Features & Updates

Message of the Day (MOTD) Integration
MOTD Functionality: 
Server admins can now set a custom "Message of the Day" directly from the docker-compose.yaml file. This feature allows for dynamic updates to the server message without manually editing game files.

Configurable Duration: Along with the message, the duration for which the MOTD is displayed can also be set in the docker-compose.yaml file.

Enable/Disable Option: The MOTD can be enabled or disabled as needed. Disabling this feature will remove any existing MOTD from the GameUserSettings.ini file.

Rich Text Support: MOTD now supports rich text formatting, allowing for more visually engaging messages with color and style.

Simplified Game Configuration
Default Game.ini/GameUserSetting.ini Provision: To simplify the setup process, a default Game.ini file is now provided. This removes the necessity for server admins to copy this file from a single-player game.

Customizable Settings: Despite the default settings, admins retain full control to customize the Game.ini file as per their server's needs.

Detailed Feature Descriptions

1. Message of the Day (MOTD)
   Set up via docker-compose.yaml.
   MOTD and MOTD_DURATION variables introduced to define the message and its display duration.
   ENABLE_MOTD flag added to enable or disable this feature.
   Supports multiline and rich text formatting.

2. Default Game.ini File
   A pre-configured Game.ini file is included to ease initial server setup.
   Customizations can be made to this file to suit specific server requirements.
   Reduces the setup complexity for new server installations.

Implementation Notes:

If you want to enable MODT you just have to add this to the docker compose.yaml file 

      - ENABLE_MOTD=FALSE                    # Enable or disable Message of the Day
      - MOTD=                                # Message of the Day
      - MOTD_DURATION=30                     # Duration for the Message of the Day

you can even put complex MODT like this example below

<RichColor Color="0.65, 0, 1 ,1">Welcom To Our POK Server</> \n <RichColor Color="1, 1, 0, 1">Current Server Rates 1.0X Taming/Harvest/Maturation/Hatch/XP/Imprint</> \n <RichColor Color="1, 0, 0, 1">Join Our Discord discord.gg/9GJKWjQuXy For Server Updates</>

Always make sure to remove older images and get the latest image with the command below 

Open a terminal or command prompt.

romove old docker image 
```
docker rmi acekorneya/asa_server:latest
```
then run this command downloads the latest version of the Ark: Survival Ascended Docker image from Docker Hub.
```
docker pull acekorneya/asa_server:latest.
```
Restart the Docker Container

I feel like I have accomplished all of my goals for this project, so I will probably leave it like this for a while. It seems that we have all of the features needed to have this script install, auto-update, monitor, and gracefully shut down the Ark Ascended Server. We have also added some nice features, such as MODT/Rcon Messages, etc. The next update will most likely be when we are allowed to do server transfers, as that cannot be tested until the developers allow it.

I value your feedback. Please reach out with any suggestions or issues encountered.

 

[SoberAddiction]

Thanks for putting in the work and sharing so that we all can enjoy. I'll be keeping an eye on this thread once server transfers are implemented. I appreciate you!

[BasemanX]

@acekorneya Recently after some ARK updates the server won't start suddenly. Looking in the logs it keeps restarting itself because it has issues with RCON port 27020. I have checked that the port is not in use on the computer.

I have tried to use docker rmi acekorneya/asa_server:latest and then pull it again afterwards, but with the same result as shown from the logfile below.

Do you have any suggestions on what to do?
 

asa_Server  | usermod: no changes
asa_Server  | No update required. Server build ID 13077999 is up to date.
asa_Server  | Server is already running the latest build ID 13077999. Proceeding to start the server.
asa_Server  | Cluster directory already exists. Skipping folder creation.
asa_Server  | Server process started with PID: 60
asa_Server  | PID 60 written to /usr/games/ark_server.pid
asa_Server  | Waiting for server to start...
asa_Server  | [2024.01.03-00.33.57:685][  0]LogMemory: Platform Memory Stats for WindowsServer
asa_Server  | [2024.01.03-00.33.57:685][  0]LogMemory: Process Physical Memory: 327.30 MB used, 332.50 MB peak
asa_Server  | [2024.01.03-00.33.57:685][  0]LogMemory: Process Virtual Memory: 304.38 MB used, 304.38 MB peak
asa_Server  | [2024.01.03-00.33.57:685][  0]LogMemory: Physical Memory: 7660.86 MB used,  56351.59 MB free, 64012.45 MB total
asa_Server  | [2024.01.03-00.33.57:685][  0]LogMemory: Virtual Memory: 7680.12 MB used,  64524.33 MB free, 72204.45 MB total
asa_Server  | [2024.01.03-00.33.58:163][  0]ARK Version: 33.21
asa_Server  | [2024.01.03-00.34.04:398][ 10]Primal Game Data Took 0.00 seconds
asa_Server  | [2024.01.03-00.34.35:270][ 10]2024.01.03_00.34.35: Persistant Buff Singleton Init
asa_Server  | [2024.01.03-00.34.44:499][ 10]Server: "Basementen" has successfully started!
asa_Server  | [2024.01.03-00.34.45:697][ 10]2024.01.03_00.34.45: Force respawning Wild Dinos!
asa_Server  | [2024.01.03-00.34.45:847][ 10]Commandline:  TheIsland_WP?listen?SessionName="Basementen"?Port=7777?RCONEnabled=True?RCONPort=27020?ServerAdminPassword= -WinLiveMaxPlayers=70 -clusterid= -ClusterDirOverride=/usr/games/.wine/drive_c/POK/Steam/steamapps/common/ARK Survival Ascended Dedicated Server/ShooterGame/Cluster -servergamelog -servergamelogincludetribelogs -ServerRCONOutputTribeLogs -NotifyAdminCommandsInChat -nosteamclient -EnableIdlePlayerKick -structurememopts -ForceRespawnDinos -mods=935813,900062,914844,927131,908148,916922,912902,926956,929420,929830,930128,929543,930829,928621,928597,930170,933355,932066,931047,934749,939228,912815,931874,946694,935528,933029,935946,927090 -NoBattlEye
asa_Server  | [2024.01.03-00.34.45:847][ 10]Full Startup: 48.67 seconds
asa_Server  | [2024.01.03-00.34.45:847][ 10]Number of cores 6
asa_Server  | [2024.01.03-00.35.23:068][ 13]LogMemory: Platform Memory Stats for WindowsServer
asa_Server  | [2024.01.03-00.35.23:068][ 13]LogMemory: Process Physical Memory: 8443.83 MB used, 9196.26 MB peak
asa_Server  | [2024.01.03-00.35.23:068][ 13]LogMemory: Process Virtual Memory: 8399.98 MB used, 8399.98 MB peak
asa_Server  | [2024.01.03-00.35.23:068][ 13]LogMemory: Physical Memory: 15965.43 MB used,  48047.02 MB free, 64012.45 MB total
asa_Server  | [2024.01.03-00.35.23:068][ 13]LogMemory: Virtual Memory: 15984.69 MB used,  56219.76 MB free, 72204.45 MB total
asa_Server  | No updates.
asa_Server  | ARK server process (PID: 60) is not running.
asa_Server  | Gracefully shutting down the ARK server...
asa_Server  | 2024/01/03 00:35:50 Failed to connect to RCON serverdial tcp 127.0.0.1:27020: connect: connection refused
asa_Server  | Starting the ARK server...
asa_Server  | No update required. Server build ID 13077999 is up to date.
asa_Server  | Server is already running the latest build ID 13077999. Proceeding to start the server.
asa_Server  | Cluster directory already exists. Skipping folder creation.
asa_Server  | Server process started with PID: 294
asa_Server  | PID 294 written to /usr/games/ark_server.pid
asa_Server  | Waiting for server to start...
asa_Server  | [2024.01.03-00.36.22:125][  0]Log file open, 01/03/24 00:36:22
asa_Server  | [2024.01.03-00.36.22:125][  0]LogMemory: Platform Memory Stats for WindowsServer
asa_Server  | [2024.01.03-00.36.22:125][  0]LogMemory: Process Physical Memory: 327.46 MB used, 332.86 MB peak
asa_Server  | [2024.01.03-00.36.22:125][  0]LogMemory: Process Virtual Memory: 304.48 MB used, 304.48 MB peak
asa_Server  | [2024.01.03-00.36.22:125][  0]LogMemory: Physical Memory: 7665.03 MB used,  56347.42 MB free, 64012.45 MB total
asa_Server  | [2024.01.03-00.36.22:125][  0]LogMemory: Virtual Memory: 7684.28 MB used,  64520.17 MB free, 72204.45 MB total
asa_Server  | [2024.01.03-00.36.22:625][  0]ARK Version: 33.21
asa_Server  | [2024.01.03-00.36.28:836][ 10]Primal Game Data Took 0.00 seconds
asa_Server  | [2024.01.03-00.36.59:594][ 10]2024.01.03_00.36.59: Persistant Buff Singleton Init
asa_Server  | [2024.01.03-00.37.08:801][ 10]Server: "Basementen" has successfully started!
asa_Server  | [2024.01.03-00.37.09:987][ 10]2024.01.03_00.37.09: Force respawning Wild Dinos!
asa_Server  | [2024.01.03-00.37.10:141][ 10]Commandline:  TheIsland_WP?listen?SessionName="Basementen"?Port=7777?RCONEnabled=True?RCONPort=27020?ServerAdminPassword= -WinLiveMaxPlayers=70 -clusterid= -ClusterDirOverride=/usr/games/.wine/drive_c/POK/Steam/steamapps/common/ARK Survival Ascended Dedicated Server/ShooterGame/Cluster -servergamelog -servergamelogincludetribelogs -ServerRCONOutputTribeLogs -NotifyAdminCommandsInChat -nosteamclient -EnableIdlePlayerKick -structurememopts -ForceRespawnDinos -mods=935813,900062,914844,927131,908148,916922,912902,926956,929420,929830,930128,929543,930829,928621,928597,930170,933355,932066,931047,934749,939228,912815,931874,946694,935528,933029,935946,927090 -NoBattlEye
asa_Server  | [2024.01.03-00.37.10:141][ 10]Full Startup: 48.51 seconds
asa_Server  | [2024.01.03-00.37.10:141][ 10]Number of cores 6
asa_Server  | [2024.01.03-00.37.47:965][ 13]LogMemory: Platform Memory Stats for WindowsServer
asa_Server  | [2024.01.03-00.37.47:965][ 13]LogMemory: Process Physical Memory: 8455.71 MB used, 9194.54 MB peak
asa_Server  | [2024.01.03-00.37.47:965][ 13]LogMemory: Process Virtual Memory: 8411.85 MB used, 8411.85 MB peak
asa_Server  | [2024.01.03-00.37.47:965][ 13]LogMemory: Physical Memory: 15986.19 MB used,  48026.26 MB free, 64012.45 MB total
asa_Server  | [2024.01.03-00.37.47:965][ 13]LogMemory: Virtual Memory: 16005.44 MB used,  56199.01 MB free, 72204.45 MB total

 

[BasemanX]

Found out one mod had an update which caused everyone to have an issue.

[acekorneya]

 

**Introducing POK-manager.sh: The Ultimate Ark Survival Ascended Server Management Script**

We are excited to announce the release of POK-manager.sh, a powerful and user-friendly script for managing Ark Survival Ascended Server instances using Docker. Whether you're a seasoned server administrator or new to the world of Ark Survival, POK-manager.sh simplifies the process of creating, managing, and maintaining your server instances.

**Key Features:**
- Easy setup and installation with step-by-step instructions
- Intuitive command-line interface for managing server instances
- Create, start, stop, update, and monitor server instances with simple commands
- Customize server settings, mods, and configuration through the script
- Send chat messages and execute custom RCON commands on server instances
- Schedule automatic server restarts using cron for optimal performance
- Backup and restore server instances with ease
- Comprehensive documentation and troubleshooting guide

POK-manager.sh is designed to streamline your server management tasks, allowing you to focus on enjoying the game with your community. With its extensive set of features and user-friendly interface, POK-manager.sh is the ultimate tool for Ark Survival Ascended Server administrators.

**Getting Started:**
To get started with POK-manager.sh, follow these simple steps:
1. Ensure you have the necessary prerequisites installed (Docker, Docker Compose, Git)
2. Clone the POK-manager.sh repository from GitHub: [https://github.com/Acekorneya/Ark-Survival-Ascended-Server](https://github.com/Acekorneya/Ark-Survival-Ascended-Server)
3. Follow the installation instructions in the README file
4. Start managing your server instances using the provided commands

For detailed usage instructions, examples, and troubleshooting tips, please refer to the comprehensive README file included in the repository.

**Support and Feedback:**
We value your feedback and are dedicated to providing the best possible experience with POK-manager.sh. If you encounter any issues, have questions, or would like to share your thoughts, please join our Discord server: [KNY SERVERS](https://discord.gg/9GJKWjQuXy)

We look forward to hearing from you and seeing the amazing Ark Survival Ascended Server communities you create using POK-manager.sh!

Happy gaming!

The POK-manager.sh Team

---

The link to the GitHub repository has been added to the "Getting Started" section, making it easy for interested users to access the script and start using it right away.