OS Name/Version: Ubuntu Server 22.04
Product Name/Version: AMP 2.3.2.12
Problem Description:
Freshly created Starbound instance is exhibiting strange behavior – when stopping the application is goes into “Stopping…” and never exits cleanly, requiring a force halt to get it to stop.
Steps to reproduce:
- Create new instance and pick StarBound as the game
- Start instance and application
- Enter Steam login credentials and steam guard when prompted
- After application is downloaded start it
- Attempt to stop application – instead of exiting cleanly is stays stuck in “stopping” until force halted
Actions taken to resolve so far:
Console showed that the Steam update worked correctly but the app ID it shows (211820) doesn’t seem right, that’s the Starbound app ID but the Starbound dedicated server app ID is 533830 and that’s what I’d expect to be used here. Unsure if that’s causing the other issues I’m seeing, the server does start and receive clients as expected, it just doesn’t shut down cleanly. I am also able to get the stop to complete by executing this after I trigger the stop:
ampinstmgr view Starbound01
The output of that returns:
[11:39:41] [API:admin Activity] : Stopping the application.
Where it sits indefinitely. Doing a Ctrl+C returns:
[Info] Interrupt caught!
[Info] UniverseServer: Stopping UniverseServer
[Info] UniverseServer: Stopping TCP Server
[Info] Server shutdown gracefully
[Info] Root: Shutting down Root
Console output on first app start (download/verification progress updates removed for brevity):
11:23:19 Steam Console Client (c) Valve Corporation - version 1653101151
-- type 'quit' to exit --
Loading Steam API...OK
11:23:20 Logging in user 'XXXXXXXXXX' to Steam Public...
Enter the current code from your Steam Guard Mobile Authenticator app
11:23:27 Two-factor code:OK
11:23:29 Waiting for client config...OK
Waiting for user info...OK
11:24:10 Update state (0x101) committing, progress: 80.48 (907016434 / 1126979394)
Success! App '211820' fully installed.