AMP
AMP copied to clipboard
ARK server doesn't restart properly
Bug Report
System Information
- Operating System (Including distribution name and version number) Ubuntu Linux 18.04.4 LTS
- AMP version and build date (Always use the version number, 'latest' is not valid!) AMP Release "Lapetus" v1.9.9.8, built 28/05/2020 10:37
- Which AMP release stream you're using (Mainline, Nightly or FastTrack) Mainline
I confirm:
- [x] that I have searched for an existing bug report for this issue.
- [x] that I am using the latest available version of AMP.
- [x] that my operating system is up-to-date.
Symptoms
The ARK server stops, but when it starts back up its not reachable, neither with RCON neither in game. The button under the graph instead of "stop" and "restart" show "kill". If restarting by a scheduled interval, the instance goes in a "blocked" state, and unable to stop the server. Only way is to stop the instance.
Reproduction
Start the ARK server, then restart. Or, start the ARK server, schedule a restart and wait.
Please confirm if this still applies to 2.0.6.2.
I can confirm that any kind of the restarting (button or schedule) is not working (AMP 2.1)
Going to piggy back on this as i'm getting a similar issue as well:
v2.3.2.4, built 22/02/2022 10:57 Ubuntu 20.04
after AMP downloads and installs the ARK server, when you click to start the server, it will just perpetually spin:
along with nothing in the console log:
ARK is one of the titles that does take an obnoxiously long time to start and gives no output of any kind until the startup completes, so I'd actually just let it sit there for an hour.
I have the same trouble, but after 5 minute, my server is online and working but doesnt have output log in console and everything work haha for the moment is good for me !
I run a server in amp for ark and I can't repro this, I think this one is resolved since it has such simple repro steps
To be honest, this issue was created more than 3 years ago. I haven't been using AMP for 2+ years now (I have switched to a competing solution, mostly because the other solution is more light on resources, and has a better CPU/RAM limiter), so I can't verify that this still happens.
If you want me to spin up AMP once again to just test it out sure, but the setup will be different from 3 years ago.
I appreciate the interest that everyone has put into this issue, but I think the fix was either implemented a long time ago or it just fixed itself.
Can the issue be closed? ARK has been reimplemented with the generic module since and AMP has had many other changes. Any ongoing issues should be raised in a new issue