Startup Issue with Application Deployment - One instance keeps crashing for no reason

Technical Support
, ,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 11 on x86_64
Product AMP ‘Callisto’ v2.5.1.0 (Mainline)
Virtualization QEMU_KVM
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

The Survival instance keeps crashing and I can’t seem to find out why. I have removed all the Server files all the plugins started from scratch and nothing seemed to work I need urgent help

Reproduction Steps

  • Start the Server
  • Join the Proxy
  • join the survival world
  • wait abt 5 mins
  • server crashes
2

@CubeCoders-Bot could you help this user take a look at their logs? Get them to check the diagnostics information from inside the instance (This ticket was opened from ADS, not the actual game instance it seems)

3

Alright, let’s get to the bottom of this. First up, we need to check the diagnostics info from the instance.

Go to your AMP interface, find the Survival instance in question, and navigate to the Support tab. In there, you’ll see a section called Diagnostics. Click on the button that says “Copy data to clipboard”. Paste that info here as plain text, and we’ll take a look.

Let’s crack this mystery! :man_detective:

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

Navigation
Support and Updates
Search…
Hostinger
Get Support
Server provided by Hostinger | Support Home

Open a support ticket
Hostinger provides unmanaged VPS hosting. An unmanaged VPS hosting service is a solution that is completely under the control of the customer. If you have adjusted the server and it cannot work anymore, you can Rebuild the VPS from Hostinger Servers tab section.

Updates
Hooray! AMP is up-to-date.

Currently running version 2.5.1 - 20240706.3

View Release Notescontract Upgrade this instancesystem_update_alt
Diagnostics
Copy data to clipboardcontent_copy
OS Linux
Platform Debian GNU/Linux 11
System Type x86_64
CPU Model AMD EPYC 9354P 32-Core Processor
CPU Layout 1S/4C/4T
Installed RAM 16011
Virtualization QEMU_KVM
Network Mode Standard
Module ADSModule
Module Application Application Deployment
Loaded Plugins FileManagerPlugin, EmailSenderPlugin, WebRequestPlugin, LocalFileBackupPlugin, CommonCorePlugin, AnalyticsPlugin
Application Name AMP
Application Version 2.5.1.0
Codename Callisto
Tools Version 2.5.0.14
Release Stream Mainline
Build Spec Release
Build Date 06/07/2024 22:13
InstanceID eb26c249-0d58-4c36-a7b4-8481dc325611
Last Executable
Last Arguments
Last Process ID 84062

5

Alright, thanks for that :muscle:. Next, let’s dive into the logs to see what’s tripping up the server.

Head over to the AMP interface:

  1. Right-click on the Survival instance.
  2. Click “View Logs”.

Copy and paste the latest log entries here (as text, not a screenshot or a link). This should give us some insight into what’s causing those crashes.

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

The log is too long to paste

7

Got it, it’s log overload! Let’s make it easier. Instead of pasting the entire log, copy and paste just the last 50-100 lines of the log here. That should give us enough detail without causing a text explosion. :volcano:

Deal? :raised_hands:

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

ChunkHolderManager] Saved 1158 block chunks, 1227 entity chunks, 0 poi chunks in world ‘world’ in 1.97s
[12:13:07] [Server thread/INFO]: ThreadedAnvilChunkStorage (world): All chunks are saved
[12:13:07] [Server thread/INFO]: Saving chunks for level ‘ServerLevel[world_nether]’/minecraft:the_nether
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world ‘world_nether’
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Halted chunk system for world ‘world_nether’
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Saving all chunkholders for world ‘world_nether’
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Saved 39 block chunks, 30 entity chunks, 0 poi chunks in world ‘world_nether’ in 0.07s
[12:13:07] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved
[12:13:07] [Server thread/INFO]: Saving chunks for level ‘ServerLevel[world_the_end]’/minecraft:the_end
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world ‘world_the_end’
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Halted chunk system for world ‘world_the_end’
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Saving all chunkholders for world ‘world_the_end’
[12:13:07] [Server thread/INFO]: [ChunkHolderManager] Saved 1 block chunks, 27 entity chunks, 0 poi chunks in world ‘world_the_end’ in 0.01s
[12:13:07] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved
[12:13:07] [Server thread/INFO]: ThreadedAnvilChunkStorage: All dimensions are saved
[12:13:07] [Server thread/INFO]: Flushing Chunk IO
[12:13:07] [Server thread/INFO]: Closing Thread Pool
[12:13:07] [Server thread/INFO]: Closing Server

9

It looks like the server is going through its usual shutdown sequence, but since it’s crashing unexpectedly, we need to dig deeper.

Check the steps below to get more detailed logs:

  1. From the “View Logs” screen in AMP for your Survival instance, filter for errors or exceptions.
  2. Look for any obvious crash messages, error codes, or stack traces.
  3. Copy and paste those error details here.

That should help us identify the root cause. :mag:

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

llector.java:116)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeScalarNode(Composer.java:241)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:205)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeValueNode(Composer.java:369)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeMappingChildren(Composer.java:348)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:323)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:209)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.getNode(Composer.java:131)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:157)
[12:07:26] [Server thread/WARN]: at org.yaml.snakeyaml.Yaml.compose(Yaml.java:575)
[12:07:26] [Server thread/WARN]: at org.bukkit.configuration.file.YamlConfiguration.loadFromString(YamlConfiguration.java:104)
[12:07:26] [Server thread/WARN]: … 17 more

11

Looks like you’ve got a YAML issue going on there. The server’s having trouble parsing a YAML file, which might be causing the crash. Here’s what you can do:

  1. Check Configuration Files: Go through your configuration files, especially those in YAML format (*.yml), and look for any syntax errors or inconsistencies. Common mistakes include:

    • Missing colons.
    • Improper indentation.
    • Special characters causing issues.

  2. Validate YAML: Use an online YAML validator to check your configuration files. This can help pinpoint any syntax errors.

After fixing any potential issues, restart your server and see if the crash still happens. Let me know how it goes!

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

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