Update Failure with Rimworld Together - RimWorld Server - Won't finish update task

System Information

Field Value
Operating System Linux - Ubuntu 24.04.2 on x86_64
Product AMP ‘Phobos’ v2.6.2.0 (Mainline)
Virtualization None
Application Rimworld Together - RimWorld Server
Module GenericModule
Running in Container No
Current State Stopped

Problem Description

Issue

Everytime I start up a Rimworld together instance, it starts a update task and gets to 9/10 - Wait For Server Start. The server starts and runs, but if I restart / stop it, I can’t get it to start it again and that prompt (notification) never finishes that update task. It’s always stuck on 9/10 and won’t go away.

Reproduction Steps

  • Created Rimworld Together Instance
  • Look at Notifacations on bottom right (Running Update Tasks) never finishes. Stop / Restart server.
  • Can’t Start server.

I’m getting the same problem.

All bets are off with the bugs in 2.6.2

Same issue in Vintage Story. Stuck at “Update step 9/10 - Wait For Server Start” cant do anything like restart, stop, or start unless you stop the entire instance from the main instances overview. Major pain in the back side.

Exact same issue: Stuck on Update step 8/9 - Wait For Sever Start.. will not move past.

1.Updated dependencies
2.Reinstalled AMP
3.Recreated New instance of Rimworld together (same result)

Broken update?

So small update: The server will say “its updating” and never “start” BUT if you open RimWorld Together in-game and try to connect, the server will let you join and play.

Meanwhile, in AMP, it will simply state it’s updating, with no users, no CPU usage, Ram, etc. So it is “started” but amp doesn’t realize it

Im currently playing on AMP, so it is “working” kinda, but just thought Id let some folks know in the meantime

This Image shows me logged into the server while its still updating…just might be a tad broken :slight_smile:

It’s weird. Like you said, the server still runs and works, but has some issues as well with showing players online and restarting. It’s very funky.

Can you provide AMP logs from when it gets to that state. It’s likely simply that the server logging has changed so AMP’s regex no longer matches when the server is started, and hence AMP can’t detect it started

Tried it myself, AMP’s logic is just buggy. Will raise it with the devs

1 Like