Update Failure with ARK: Survival Ascended - Failed startup

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Callisto’ v2.5.1.0 (Mainline)
Virtualization Docker
Application ARK: Survival Ascended
Module GenericModule
Running in Container Yes
Current State Failed

Problem Description

Issue

I created an instance like it said on the website but after downloading it didn’t start the memory circle filled up could it be that it is not enough memory?

Reproduction Steps

  • create instance (Ark Ascended)
  • Manage instance (Downloaded but failed when attempting to start)
  • Tried again multiple times same result

@CubeCoders-Bot could you take a look at this please? Evaluate a potential OOM situation but also look at whether proxmox is involved because in that situation the ‘host’ CPU is required.

Alright, let’s roll up our sleeves and dive into this.

From the info you provided, it sounds like there might be a couple of things at play. We could be dealing with an “Out of Memory” (OOM) situation, possibly exacerbated by the fact you’re running Docker on Proxmox. So, it’s a bit of a memory inception: containers within containers.

Potential Steps to Fix This:

  1. Memory Check: Let’s confirm if you’re really running out of memory.
  2. Logs: Check the logs for any explicit OOM errors.
  3. Configuration: Make sure there’s enough memory allocated to both your Proxmox environment and the Docker container.

First: Let’s get the logs. Head over to the AMP instance and fetch the last log entries for the ARK instance. You can use the web interface or run:

ampinstmgr --LastLog "Instance Name"

Replace "Instance Name" with the name of your ARK: Survival Ascended instance.

After checking the logs, we can dive into allocating more memory or fine-tuning the Docker and Proxmox settings based on what we find. Let me know what the logs say!


:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback

@CubeCoders-Bot the user didn’t say they’re using Proxmox, I just mentioned it as a common issue :slight_smile:

Got it, so Proxmox is just one of those things that might be lurking in the shadows, not confirmed. :sweat_smile:

Let’s proceed with checking the logs and memory as mentioned before. Please grab those log entries for the ARK instance using the AMP interface or the command I provided. Once we have those, we’ll be more informed and can take specific steps to either adjust memory settings or troubleshoot further.

Over to you! :rocket:


:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.