AMP
AMP copied to clipboard
VRising Linux Server Not Starting
Hey Guys, I'm wanting to start up the linux version of a V-Rising server. I've replaced the config file to allow adding the server as an instance. However, after updating and downloading the necessary files, starting the server just loops and download/verification of files a few times before saying it succeeds and not actually running the server.
I'm using Debian 11 with AMP version 2.3.3
I've tried ensuring that Steam uses my account when updating the files to no avail. In the console is says "Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'" and when I check the file, each line is met with "flock LOCK_EX request but file is not opened for writing, ignoring:" for each file. The instance console also says "CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 1 items discarded." at some point in the loop as well but I'm not sure what it means. I've tried deleting and readding the instance multiple times and still don't have anything. Any reason why it could be doing this?
Are you using a Docker container within AMP? Or running it natively?
I'm pretty sure I'm just using native.
I suggest making a Docker instance of it. That will avoid the possibility that you're missing a dependency somewhere.
Alright, I've installed Docker Desktop and linked it to AMPs file sharing. AMP now makes the new instances using Docker. However, it still doesn't go through. If I start the instance, a container briefly appears and disappears. I can't delete or manage the V-Rising instance anymore. In the main AMP console this message repeatedly appears: Tried to get version number for instance DankyCraftVRising but the manifest data could not be found."
So I'm at another standstill here. I'm pretty new to linux so a lot of this is very trial and error for me (And lots of googling)
Ahh if you didn't have Docker you can use the install script for AMP but append installaDocker to the end. A new release is coming shortly. Try it when it comes and see if that works better for you.
Update: Just updated AMP today to v2.3.4 and there's a new loadout that includes both windows and linux like the other server options. I've deleted the old instance and recreated a new one (Not using Docker). After installing everything for the instance, trying to start the server gives a "Application State: Preparing to Start" in the instance status console. This message has been left for hours with nothing in the regular console as well. I've tried using Docker for it again but the instance just freezes and can't be deleted through AMP.
So, essentially at another standstill. I can't be the only one experiencing this can I?
You aren't the only one having trouble, you're the only one not following the instructions to fix it. ;)
bash <(wget -qO- getamp.sh) installDocker after removing any Docker you've installed yourself. Then change Configuration->New Instance Defaults to create it in a container. This will include all dependencies. Otherwise you'll need to install all the Wine and Xvfb dependencies yourself outside of Docker.
Yep I deleted the old docker and installed the new one exactly like you said, and set AMP to create new containers for instances. But when I try to create the VRising instance it fails because it can't find docker. I only did what you said because I don't know if there are any other steps in between.
What is the output from running that command? Are you running it as root?
Yeah it only runs when I do it as root. The output is shockingly short: Please wait while GetAMP examines your system and network configuration... Installing Docker... Done
Be sure you restarted the server before creating an instance. Also, as the amp user show the output from docker version to make sure it has access properly.
K it doesn't look like it has access because it gives me "bash: docker: command not found". How would I do that?
Restarting also doesn't change the error.
Where do you see that?
This is in the regular terminal, when I try running "docker version" as the amp user.
I apologize! This dropped off my radar. Are you still having issues?
No, unfortunately I haven't been able to make any progress on it.
Are you on the Discord server?
I am not. Where can I join?
Edit: Nevermind, it was easy to find.
Ping me on there and we can take a look. It's just easier for me to track on there.
Looks like a configuration issue and not a bug. Closing unless I hear otherwise.