Rust cannot start on console

Questions
1

20:45:33

Non-managed instances exist, autoconfigure cannot guarantee that the configuration is valid!

20:45:50

Waiting for AMP instance to start…

AMP instance Rust01 is now running.

20:46:00

Instance Rust01 has stopped

ADS logged stopped instance Rust01 - exit code -1 (CATASTROPHIC_FAILURE)

@CubeCoders-Bot

2

Yikes! It looks like your Rust server instance is having a bit of a meltdown. The error with the “CATASTROPHIC_FAILURE” and “exit code -1” usually means there’s something seriously wrong with the instance configuration or startup process.

First things first, let’s try to get more details about what went wrong by checking the latest logs. You can do this via the AMP web interface by right-clicking on the instance “Rust01” and selecting “View Logs”. Look for anything specific that might give us more context about the crash.

Once you’ve got some log details, feel free to share them (just the text part, not screenshots) and we can narrow down what’s causing the catastrophe. :sweat_smile:

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

Cannot manage this instance

The specified instance is not running

4

Got it. The “specified instance is not running” message can be a bit confusing, especially if you were expecting it to be up and running. Let’s see if we can make some magic happen :magic_wand:

Try these steps:

  1. Ensure it’s not running elsewhere: Sometimes the instance might be running but not showing up properly in the interface. Check if there’s any AMP or Rust process still going on in your task manager (Windows) or with top/ps on Linux.

  2. Logs, logs, logs: We still need some logs to diagnose the issue better. If the instance won’t start, there might still be some clues in the most recent logs before it shut down.

  3. Check instance configuration: Back in the AMP interface, use the search function to check the instance configuration and make sure everything looks correct, especially the pathing and any port settings.

Let me know how it goes or if we need to dive into more specific settings! :mag:

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

[12:51:33] [Program Info/1] : Starting AMP version 2.5.1.6 (Callisto), built 16/08/2024 03:11
[12:51:33] [Program Info/1] : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[12:51:33] [Core Warning/1] : Current time zone is set to 台北標準時間 - It is recommended you switch to UTC+0 to avoid time-zone related issues
[12:51:33] [Program Info/1] : OS: Windows / x86_64
[12:51:33] [Program Info/1] : CPU: AMD Ryzen Threadripper 3960X 24-Core Processor (24C/48T)
[12:51:33] [Program Info/1] : RAM: 196503MB
[12:51:33] [Program Info/1] : AMP Instance ID: 185689a4-eb58-4b7b-8065-a3a7259b8708
[12:51:33] [Loader Info/1] : Loaded RustModule version 1.0.0.0 by CubeCoders Limited
[12:51:33] [Core Info/1] : Metrics publishing is enabled at udp://localhost:12820.
[12:51:33] [Loader Info/1] : Loaded FileManagerPlugin by CubeCoders Limited
[12:51:33] [Loader Info/1] : Loaded EmailSenderPlugin by CubeCoders Limited
[12:51:33] [Loader Info/1] : Loaded WebRequestPlugin by CubeCoders Limited
[12:51:33] [Loader Info/1] : Loaded LocalFileBackupPlugin by CubeCoders Limited
[12:51:33] [Loader Info/1] : Loaded CommonCorePlugin by CubeCoders Limited
[12:51:33] [Loader Info/1] : Loaded AnalyticsPlugin by CubeCoders Limited
[12:51:34] [Loader Info/1] : RustModule requests dependency steamcmdplugin…
[12:51:34] [Loader Info/1] : Loaded steamcmdplugin by CubeCoders Limited
[12:51:34] [Loader Info/1] : RustModule requests dependency RCONPlugin…
[12:51:34] [Loader Info/1] : Loaded RCONPlugin by CubeCoders Limited
[12:51:34] [Core Info/1] : Licence Present: AMP Professional Edition - Lifetime Licence
[12:51:34] [FileManager Notice/1] : No SSH keypair available for embedded server, generating new keypair…
[12:51:34] [FileManager Notice/1] : Generated new keypair with fingerprint v9TLE1/OAhFijn+ef462pEDBCXa3loRk1Wvv4tBnfJA=
[12:51:34] [FileManager Notice/1] : Using keypair with fingerprint v9TLE1/OAhFijn+ef462pEDBCXa3loRk1Wvv4tBnfJA=
[12:51:34] [FileManager Info/1] : SFTP Server started on 0.0.0.0:8211
[12:51:34] [Webserver Info/1] : Websockets are enabled.
[12:51:34] [Webserver Info/1] : Webserver started on http://0.0.0.0:8211
[12:51:34] [Webserver Info/11] : RouterTimer@10Hz with 2 jobs started
[12:51:34] [ErrorReporter Error/8] : Socket exception - Trivial error / user error. Will not be submitted.
[12:51:34] [Core Info/13] : Checking for AMP updates…
[12:51:34] [ErrorReporter Error/8] : [Error] — Begin Exception Data —

6

Alright, it looks like we’re in the midst of some action here! The log snippet reveals a couple of important pieces of info:

  1. You’re running AMP version 2.5.1.6, not 2.5.1.0. This might be a version issue messaging.
  2. There’s a timezone warning. Although this might not be directly related to the server starting issue, switching to UTC+0 can sometimes help avoid weirdness.
  3. The main culprit might be the “Socket exception” which, although labeled as a trivial error, could still be part of the shutdown problem.

We should focus on two things here:

  1. Timezone Change (Optional): Try switching to UTC+0 if possible, just to eliminate any timezone-related shenanigans.
  2. Network Settings: Check your network/firewall settings to make sure nothing’s blocking the required ports. Ensure AMP is managing these settings as expected.

If you’ve got more logs or if anything specific sticks out, share away! Sometimes it’s the tiny details that throw us a curveball. :baseball:

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

[12:45:50] [InstanceManager:admin Notice/50] : AMP instance Rust01 is now running.
[12:46:00] [InstanceManager Activity/44] : Instance Rust01 has stopped
[12:46:00] [ADS Info/44] : ADS logged stopped instance Rust01 - exit code -1 (CATASTROPHIC_FAILURE)
[12:46:18] [System:admin Info/28] : docker: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head “http://%2F%2F.%2Fpipe%2Fdocker_engine/_ping”: open //./pipe/docker_engine: Access is denied.
[12:46:18] [System:admin Info/28] : See ‘docker run --help’.
[12:46:18] [InstanceManager:admin Warning/56] : Failed to configure new instance Rust01 - Startup failure: Docker returned error code 125
[12:46:25] [System:admin Info/22] : docker: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head “http://%2F%2F.%2Fpipe%2Fdocker_engine/_ping”: open //./pipe/docker_engine: Access is denied.
[12:46:25] [System:admin Info/22] : See ‘docker run --help’.
[12:46:35] [System:admin Info/31] : docker: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head “http://%2F%2F.%2Fpipe%2Fdocker_engine/_ping”: open //./pipe/docker_engine: Access is denied.
[12:46:35] [System:admin Info/31] : See ‘docker run --help’.
[12:46:46] [InstanceManager:admin Info/19] : Waiting for AMP instance to start…
[12:46:46] [InstanceManager:admin Notice/19] : AMP instance Rust01 is now running.
[12:46:53] [InstanceManager:admin Activity/19] : Instance Rust01 has stopped
[12:46:53] [ADS:admin Info/19] : ADS logged stopped instance Rust01 - exit code -1 (CATASTROPHIC_FAILURE)
[12:47:00] [ADS:admin Activity/19] : Upgrading instance Rust01
[12:47:11] [ADS:admin Activity/34] : Deleting instance 76bf66fa-68ef-46ae-bf2b-f1cbd4713a60
[12:47:11] [InstanceManager:admin Info/37] : Deleting directory D:\AMPDatastore\Instances\Rust01…
[12:51:16] [InstanceManager:admin Warning/5] : Non-managed instances exist, autoconfigure cannot guarantee that the configuration is valid!
[12:51:32] [InstanceManager:admin Info/42] : Waiting for AMP instance to start…
[12:51:32] [InstanceManager:admin Notice/42] : AMP instance Rust01 is now running.
[12:51:43] [InstanceManager:admin Activity/54] : Instance Rust01 has stopped
[12:51:43] [ADS:admin Info/54] : ADS logged stopped instance Rust01 - exit code -1 (CATASTROPHIC_FAILURE)
[12:55:42] [ADS:admin Activity/30] : Upgrading instance Rust01
[12:55:52] [ADS:admin Activity/30] : Upgrading instance Rust01
[12:56:01] [InstanceManager:admin Info/30] : Waiting for AMP instance to start…
[12:56:01] [InstanceManager:admin Notice/30] : AMP instance Rust01 is now running.
[12:56:09] [InstanceManager:admin Activity/10] : Instance Rust01 has stopped
[12:56:09] [ADS:admin Info/10] : ADS logged stopped instance Rust01 - exit code -1 (CATASTROPHIC_FAILURE)
[12:56:30] [ADS:admin Activity/34] : Upgrading instance Rust01
[12:56:40] [InstanceManager:admin Info/15] : Waiting for AMP instance to start…
[12:56:40] [InstanceManager:admin Notice/15] : AMP instance Rust01 is now running.
[12:56:53] [InstanceManager:admin Activity/15] : Instance Rust01 has stopped
[12:56:53] [ADS:admin Info/15] : ADS logged stopped instance Rust01 - exit code -1 (CATASTROPHIC_FAILURE)

8

Whoa, it seems like Rust01 is stuck in a loop of doom: starting up, crashing with a “Catastrophic Failure,” and trying an upgrade. :scream: This is like a bad Groundhog Day scenario. Let’s break it down:

  1. Instance Deletion/Creation: I noticed a “Deleting instance” log message, which indicates there might have been an attempt to reset the instance. Was this intentional?

  2. Non-Managed Instances: The “Non-managed instances exist” message suggests there are parts of the setup that aren’t being controlled by AMP. This could mean previous manual modifications or incomplete configurations are tripping things up.

Let’s troubleshoot step by step:

  • Instance Reset: If you haven’t already, you might want to intentionally delete and recreate the instance after backing up any necessary configs.
  • Configuration Check: Ensure that the Rust server’s configuration and required dependencies (like SteamCMD) are correctly set from the AMP interface.
  • Logs During Crash: When the instance stops, if possible, look for more detailed logs during that brief running period to catch any hints of what’s causing the crash.

The goal is to stabilize the instance boot process without it defaulting to upgrades. Let me know how it goes or if you want to try any specific steps!

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

I tried to create a new instance, but after it failed to start, I tried to update the instance. After the update, I still couldn’t start the instance, so I deleted the instance.

10

Ah, the dreaded cycle of creating, failing, updating, and repeating. Been there, done that! Let’s snap out of this loop and get your server up and running.

Since you’ve already tried nuking the old instance, here’s a fresh approach:

  1. Create a Clean New Instance:

    • Go into the AMP interface and create a brand-spanking-new Rust server instance. Make sure to follow the prompts for creating it without any legacy settings carrying over.

  2. Default Configuration:

    • When setting it up, stick with the default settings initially. This means avoiding custom tweaks until we’re sure it runs on the default.

  3. Run Once Before Updating:

    • Before applying any updates or modifications, try starting the instance simply with its out-of-the-box configuration. This will help identify if a base config issue is causing the hitch.

  4. Check Logs Immediately on Failure:

    • If the start fails, try to capture the logs right then and there for anything that hasn’t been revealed so far.

If this approach causes any mischief or you get more logs, throw them my way. We’ll crush those catastrophic failures into kitty purrs. :cat:

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

[12:56:41] [Program Info/1] : Starting AMP version 2.5.1.6 (Callisto), built 16/08/2024 03:11
[12:56:41] [Program Info/1] : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[12:56:41] [Core Warning/1] : Current time zone is set to 台北標準時間 - It is recommended you switch to UTC+0 to avoid time-zone related issues
[12:56:41] [Program Info/1] : OS: Windows / x86_64
[12:56:41] [Program Info/1] : CPU: AMD Ryzen Threadripper 3960X 24-Core Processor (24C/48T)
[12:56:41] [Program Info/1] : RAM: 196503MB
[12:56:41] [Program Info/1] : AMP Instance ID: 185689a4-eb58-4b7b-8065-a3a7259b8708
[12:56:41] [Loader Info/1] : Loaded RustModule version 1.0.0.0 by CubeCoders Limited
[12:56:41] [Core Info/1] : Metrics publishing is enabled at udp://localhost:12820.
[12:56:41] [Loader Info/1] : Loaded FileManagerPlugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : Loaded EmailSenderPlugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : Loaded WebRequestPlugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : Loaded LocalFileBackupPlugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : Loaded CommonCorePlugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : Loaded AnalyticsPlugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : RustModule requests dependency steamcmdplugin…
[12:56:41] [Loader Info/1] : Loaded steamcmdplugin by CubeCoders Limited
[12:56:41] [Loader Info/1] : RustModule requests dependency RCONPlugin…
[12:56:41] [Loader Info/1] : Loaded RCONPlugin by CubeCoders Limited
[12:56:41] [Core Info/1] : Licence Present: AMP Professional Edition - Lifetime Licence
[12:56:42] [FileManager Notice/1] : Using keypair with fingerprint v9TLE1/OAhFijn+ef462pEDBCXa3loRk1Wvv4tBnfJA=
[12:56:42] [FileManager Info/1] : SFTP Server started on 0.0.0.0:8211
[12:56:42] [Webserver Info/1] : Websockets are enabled.
[12:56:42] [Webserver Info/1] : Webserver started on http://0.0.0.0:8211
[12:56:42] [Webserver Info/11] : RouterTimer@10Hz with 2 jobs started
[12:56:42] [ErrorReporter Error/8] : Socket exception - Trivial error / user error. Will not be submitted.
[12:56:42] [Core Info/13] : Checking for AMP updates…
[12:56:42] [ErrorReporter Error/8] : [Error] — Begin Exception Data —
[Error] OS: Windows (x86_64/None)
[Error] Module: RustModule, Version: AMP 2.5.1.6
[Error] Release spec: Mainline - built by CUBECODERS/buildbot on CCL-DEV
[Error] Instance ID: 185689a4-eb58-4b7b-8065-a3a7259b8708
[Error] SocketException
[Error] [0] (SocketException) : 一次只能用一個通訊端位址 (通訊協定/網路位址/連接埠)。
[Error] at Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at Net.Sockets.Socket.Bind(EndPoint localEP)
at Net.Sockets.TcpListener.Start(Int32 backlog)
at m.Http.HttpBackend.()
[Error] — End Exception Data —
[Warning] Last error was raised less than 60 minutes ago, error report will not be submitted.

[12:56:42] [ErrorReporter Info/8] : ####################################
[12:56:42] [ErrorReporter Info/8] : # Self Diagnostics #
[12:56:42] [ErrorReporter Info/8] : ####################################
[12:56:42] [ErrorReporter Info/8] : The IP and Port combination requested by the socket is already in use by another application. Either end the other application or re-bind this AMP instance to a different IP/port.
[12:56:43] [Core Info/19] : AMP is up to date.

12

Aha! We’re finally seeing the culprit: the dreaded “Socket exception” indicating that the IP and port combo AMP is trying to use is already being hogged by another application.

Let’s tackle this:

  1. Port Change: In the AMP interface, use the search functionality to find the network or port settings for your Rust instance. Try assigning a different port that you know isn’t in use.

  2. Port Check: Alternatively, check Windows’ task manager or use netstat -aon in command prompt to find out which app is currently using the port and decide if you can stop it.

Once you’ve made the changes or found the sneaky port-thief, give starting the instance another shot. Let me know if it springs to life or needs more TLC!

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

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