Rust instance not connecting to Rust RCON server, causing server to not finish loading.

  • 79 Views
  • Last Post 2 weeks ago
  • Topic Is Solved
duckster18 posted this 4 weeks ago

OS Name/Version: Windows 10 Pro x64 Build 1803

Product Name/Version: AMP Release "Hawking Starman" v1.7.3.0

Problem Description: Rust server instance does not connect to Rust RCON server. Computer will show running and get up to around 1,667 MB of RAM used and then CPU usage will drop to 0%. If instance is left running and server is not stopped, AMP will endlessly try to connect to RCON. If the server is left running, but AMP instance is stopped, server will finish starting up and is accessible.

Steps to reproduce: Install Rust Instance. Leave all setting default

Actions taken to resolve so far: I've re-created the instance multiple times. I've modified the RustModule.kvp and RCONPlugin.kvp to use different RCON ports including the Rust default ports. I've allowed AMP to download and install the server, created a Start_Server.bat in the AMP instance and run with the same arguments that AMP uses with no issues, server starts up and is accessible. I've downloaded a server manually via SteamCMD and copied files over to AMP instance.

Here is the log file from AMP:

[16:14:59] [Core:Anonymous Activity] : Authentication success [16:15:13] [System:Admin Activity] : Starting the application. [16:15:13] [Rust:Admin Debug]     : Starting process ./rust/258550\RustDedicated.exe [16:15:13] [Rust:Admin Debug]     : Working Directory: ./rust/258550 [16:15:13] [Rust:Admin Debug]     : Arguments: -batchmode -nographics -logFile . +rcon.password "39a6ec6aeb2048ef84cfd3782188064b" +server.port "28015" +rcon.port "5678" +server.ip "0.0.0.0" +server.seed "6738" +server.hostname "A Rust server" +server.level "Procedural Map" +server.description "My Rust server - powered by AMP" +server.headerimage "" +server.url "" +server.maxplayers "100" +antihack.enabled "False" +server.worldsize "4000" +server.saveinterval "4000" +server.pve "False" +rcon.web "False" [16:15:13] [Rust:Admin Debug]     : Started process with ID 1832 [16:15:24] [System:Admin Debug]   : Source RCON connecting to 127.0.0.1:5678... [16:15:35] [System:Admin Debug]   : Source RCON connecting to 127.0.0.1:5678... [16:15:46] [System:Admin Debug]   : Source RCON connecting to 127.0.0.1:5678... [16:15:57] [System:Admin Debug]   : Source RCON connecting to 127.0.0.1:5678...

Order By: Standard | Newest | Votes
Mike posted this 4 weeks ago

Rust takes a really long time to start. I mean an utterly reduculous, ungodly long time to start. It will eventually start, and once it does AMP will finally be able to connect to the RCON. Rust really is an server that requires an SSD to run, it can take several minutes to start even on NVMe based storage - on standard hard drives it's not uncommon for it to take 25-30 minutes to start.

duckster18 posted this 4 weeks ago

I let it sit for over 24 hours and it was stuck on startup trying to connect to RCON

duckster18 posted this 4 weeks ago

I created a batch file to start the server and used the exact arguments that AMP sends and it starts up fine in about 10 min

Mike posted this 4 weeks ago

Does the server show as listening in Netstat?

duckster18 posted this 4 weeks ago

No the server port is not showing up on Netstat

Mike posted this 4 weeks ago

Is the instance running as a service?

duckster18 posted this 4 weeks ago

Not right now, I have tried installing the service for it, but it doesn't really install since its managed by ADS, once I have to restart the instance the Service is no longer installed.

Mike posted this 4 weeks ago

Try with the latest (1732) build.

duckster18 posted this 4 weeks ago

Only ADS is updating to 1.7.3.2, all my instances are staying at 1.7.3.0 even when I create a brand new one. With ADS on 1.7.3.2 I have the same issue with Rust

Mike posted this 4 weeks ago

You need to update the instances, empty out the AMPCache files from the datastore and use ampinstmgr upgradeall

duckster18 posted this 4 weeks ago

Same thing after updating all instances to 1.7.3.2. Also the ampinstmgr upgradeall did not update the actual instances, they would still show up as on 1.7.3.0, had to manually copy the files from the AMPCache-1732.zip to each instance on my computer.

Mike posted this 3 weeks ago

We're they showing as an old version in 'ampinstmgr info'?

duckster18 posted this 3 weeks ago

yes the should as being version 1.7 3.0 and would download the package and say its extracting but didnt

duckster18 posted this 2 weeks ago

Any update?

Close