On 5/26/2022 at 11:12 AM, ich777 said:

This is really strange, most people that are having issues are on AMD systems…

 

Please check if the container data is spread over multiple disks if they are spread over multiple disks delete the container and the directory for the game, pull a fresh copy from the CA App and change the path to the gamefiles to /mnt/diskX/appdata/vrising (change X to the disk where you want to have the data on) and see if it works.

 

Thanks for that! I was about to prepare a server for the game release and I had a similar issue with the container restarting in loop. That trick seems to have done the job.

 

You're busy enough I'm sure, but I'd be curious as to why if you had a simple explanation. Too complicated and I won't understand anyway haha

29 minutes ago, Logidroid said:

how can I access it at /mnt/cache/... via SMB it's quite complicated to understand at this level 😅

You don't have to access /mnt/cache/... you have to fix how things are working on your server.

 

Please read my comment from above again...

Make sure that your appdata share stays on the cache in the Share settings from your appdata share and are not moved over to the Array, that's it.

5 minutes ago, matmat07 said:

You're busy enough I'm sure, but I'd be curious as to why if you had a simple explanation. Too complicated and I won't understand anyway haha

Some games have issues when you use the FUSE file path (/mnt/user/...) for the game files and refuse to start or they are segfaulting (mostly Source games and a few others like V-Rising).

To solve that you have to use the real file path to the game files (/mnt/cache/... /mnt/diskX/... or wherever the gamefiles are located) so that the server is actually able to start, that's why by default in most of my templates /mnt/cache/appdata/... is used instead of /mnt/user/appdata/... to avoid such issues <- this has also another benefit of avoiding the FUSE filesystem and saving a bit of CPU power.

getting a weird issue where a version check is saying the server is a different version from the client. 

I am running modded, Tried to force update the container but for some reason its carring a 1- in front of it.. not sure that is actually what's breaking it but at this point it seems likely. Anyone got ideas?

2 hours ago, ich777 said:

Some games have issues when you use the FUSE file path (/mnt/user/...) for the game files and refuse to start or they are segfaulting (mostly Source games and a few others like V-Rising).

To solve that you have to use the real file path to the game files (/mnt/cache/... /mnt/diskX/... or wherever the gamefiles are located) so that the server is actually able to start, that's why by default in most of my templates /mnt/cache/appdata/... is used instead of /mnt/user/appdata/... to avoid such issues <- this has also another benefit of avoiding the FUSE filesystem and saving a bit of CPU power.

Well, I spoke too fast. After I restarted the container once it keep restarting by itself once again. 

I'll check some more tomorrow morning, but I'm done for the day on this I believe

TES3MP binds to port 9707, despite the port not appearing anywhere in the config for TES3MP, the container, or port forwarding. Everything is set to the default of 25565.

@ich777 Hey man your https://hub.docker.com/r/ich777/beamng-mp-server is failing to download and install. I did some digging and believe this issue is caused by the beammp devs changing how each release is named. I think your code looks for the latest version named "BeamMP-Server-linux" no such file exists anymore. I'm trying to dig further into docker to understand what your code is doing but I figured i'd let you know here so you can fix it faster.

1 hour ago, MrTroll said:

I'm trying to dig further into docker to understand what your code is doing but I figured i'd let you know here so you can fix it faster.

You don't have to, I'll fix that later today. Thanks for the report.

 

EDIT: Please update the container itself, pushed a fix already.

6 hours ago, duum said:

TES3MP binds to port 9707, despite the port not appearing anywhere in the config for TES3MP, the container, or port forwarding. Everything is set to the default of 25565.

Good catch, I will look into that but it was working back then when I created the container.

I will look into that.

 

EDIT: What I find actually funny is that the container listens on port 25565:

9 hours ago, xangetzu said:

I am running modded

I assume we are talking about Valheim? Maybe this is caused because it's a modded server, I really can't help with modded servers because I can only support the basic functionality.

 

However, have you yet tried to remove this mod from your local computer and see if it works afterwards:

58 minutes ago, ich777 said:

EDIT: Please update the container itself, pushed a fix already.

@MrTroll have you seen that I already pushed an update? It should now work as it should.

 

They dropped the static linux build for whatever reason but as said, it is working again and is now also on my latest Debian Bookworm baseimage.

Is V-Rising Game Server ready for the new version?

(V-Rising just left the Early Acc. a few hours ago...)

1 hour ago, majo23 said:

Is V-Rising Game Server ready for the new version?

(V-Rising just left the Early Acc. a few hours ago...)

It doesn't appear to be. I just tried running mine and it seems to start alright, but I can't connect to it, even though I verified that the container was working yesterday with the previous version.

 

The only thing in the server logs that I'm seeing to give any indication so far are the following lines:

Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.

 

1 hour ago, majo23 said:

Is V-Rising Game Server ready for the new version?

26 minutes ago, paralyze296 said:

It doesn't appear to be. I just tried running mine and it seems to start alright, but I can't connect to it, even though I verified that the container was working yesterday with the previous version.

Everything is working over here and I can connect just fine with a fresh set up container.

 

Did both of you restart the container and did the container pull the update? Are you also sure that your client is up to date?

 

Are both of you are sure that "ListOnSteam" and "ListOnEOS" is set to true in your game config?

 

I have created a server which is visible on the list as you can see here (I already stopped it when you read this):

(as you can also see I have a character on the server because I tested if everything is working, so to speak I was able to connect )

33 minutes ago, ich777 said:

Everything is working over here and I can connect just fine with a fresh set up container.

 

Did both of you restart the container and did the container pull the update?

Are both of you are sure that ListOnSteam and ListOnEOS is set to true in your game config?

 

I have created a server which is visible on the list as you can see here (I already stopped it when you read this):

(as you can also see I have a character on the server because I tested if everything is working, so to speak I was able to connect )

I have restarted the container, as well as completely deleted all appdata and pulled it fresh

 

The "ListOn..." settings were not present in the server settings I copied from the server I made on desktop, and I noticed that the desktop files used numbers for most of the settings, rather than true/false or other values.

 

I think I've managed to get it working by editing the default config, rather than copying the config from the file created on desktop. For some reason there was also an error with the complex password I was using, even though it was identical to what I had yesterday when I checked to ensure it was working. I might try and troubleshoot that further but probably not, to be honest.

 

Thanks for the tip

Now I wonder what went wrong with my installation. I did not configure any file in it yet, but I doubt this would be what makes it reboot.
That PID thing, is it because it's looking for a process that never started? Anyway...

8 hours ago, paralyze296 said:

The "ListOn..." settings were not present in the server settings I copied from the server I made on desktop

It sure is in there after the first start from the container, are you sure you where in the correct directory? It is located at: .../vrising/save-data/Settings/ServerHostSettings.json and by default it is set to false:

 

 

8 hours ago, matmat07 said:

That PID thing, is it because it's looking for a process that never started? Anyway...

Did you maybe had BepInEx enabled, seems like it is currently not working and needs to be updated to support V Rising 1.0+

On 5/7/2024 at 9:27 PM, ich777 said:

Is this a conpletely new installstion?

 

Are you sure that you don‘t use a specific version on the client, so to speak your PC?

I'm sure I've been playing normal CS2 online for the last few days and found the problem. After uninstalling it, I simply deleted the CS2 folder and reinstalled everything. Now it works, why I didn't think of it right away.
But thanks anyway for the quick answer

@ich777

Thanks, everything works fine! I can play, and the performance is really good.

 

Has anyone successfully changed the "TeleportBoundItems" rule? I modified it in the JSON file, but the change didn't take effect. 😮

 

G

4 minutes ago, majo23 said:

Has anyone successfully changed the "TeleportBoundItems" rule?

Yes me, when the game was still in beta I had this working as expected.

Hey guys, i got a little bit stuck trying to set up an Ark:Survival Ascended Server. I used to run several Ark:Survival Evolved servers without any problems, but i have the problem with the ASA server, that i cannot connect to it. I cannot see it in the server browser neighter in the game nor in steam. In the logs i see no error and it says that the server started correctly. I also tried to define an additional port 27015 as query port but the server didnt show up. At this point every help is appreciated.

Thanks in advance

Would love a good version of UT2004 with the gamespy patch done. Also I setup Quake3 arena and the game doesn't see the server on my LAN. I ran the container, stopped it, put the pak files in the appdata and all that. Still doesn't see the server on my LAN. Any help?

3 minutes ago, Unibrowser said:

Would love a good version of UT2004 with the gamespy patch done.

Sorry, I don't accept any requests for dedicated game servers anymore.

 

3 minutes ago, Unibrowser said:

Still doesn't see the server on my LAN. Any help?

Any logs? How do you connect? Have you changed anything in the Docker template?

7 minutes ago, mclis said:

At this point every help is appreciated.

Any logs?

Did you change anything in the template or the config?

The logfiles are attached.

In my first step i changed the server-name, the password and the admin-pw. I also set my steam login credentials, thats all. 

As i could not find the server, i added the additional port 27015 and added "?QueryPort=27015" to the commandline. Unfortunately that did not work either.

In my last try I set up the container and all i added was the steam credentials.

Maybe you find something in my logs.

 

game_83374_2024.05.09-17.57.46.250.log Console log.txt