attempting to update 18.1(b2)

Status
Not open for further replies.
B

bloodstone

Refugee
I cant seem to find where the dedicated version for linux is I am using the steamCMD and it is giving me version

Alpha 18 (b155) Compatibility Version: Alpha 18, Build: Linux 64 Bit

this is on a system that was able to run 17.4 no problem and this is a line the program kicks out when started.

Specs:

OS: Linux 4.15 Ubuntu 18.04 64bit

CPU: Intel® Xeon® CPU X5660 @ 2.80GHz (cores: 24)

RAM: 20066 MB

important lines of the config file: serverconfig.xml

<property name="GameWorld" value="Navezgane"/>

<property name="WorldGenSeed"value="dfiwwy"/>

<property name="WorldGenSize" value="4096"/>

<property name="GameName" value="waffle"/>

Unfortunately there is very little information on 18.1 server information out, because its fairly new.

Any suggestions on getting the system to get 18.1(b2) would be greatly appreciated. :fat:

 
Last edited by a moderator:
You need to add -beta latest_experimental when installing via SteamCMD. A18.1 isn't stable yet, but experimental.

./steamcmd.sh +login anonymous +force_install_dir <directory> +app_update 294420 -beta latest_experimental -validate +quit

 
ok got that to update, is there any known issue with building maps? I had the system sit for 8 hours and it never build the map. I am going to include the full serverconfig.xml and log.

severconfig.xml = https://pastebin.com/Tg9a9JXq

output.log = https://pastebin.com/Gz5tgdEu

unable to telnet to the server, even though I Have been able to before once the server is running. I don't get the password request. If i change RWG to anything else the telnet server seems to load but again never actually builds the region files.

 
It's normal for the RWG needing loots of time at this point without giving further response ...

Code: 
WorldGenerator:Generating Detail Data
... you may check by monitoring your cpu usage, it should be maxed at this point.

Though waiting for 8 hours is already a long time, you may check with a smaller map size at least for testing purposes?

Btw., if you didn't already fake your (telnet-) password before publishing your config file, you may want to change it now. ;-)

 
already did change the passwords and its behind nat anyhow no active path to the port. I will test again and see if it actually loads with a smaller map.

 
This is the output after running the server for 12 hours, still cant connect via client to the server as it says its still initilizing, there are no files in the regon folder as would be expected and it will allow a shutdown via telnet.

output-log=https://pastebin.com/sH6ESAZV

 
going through the logs and looking at the older 17.4 I noticed that there is a discrepancy in how the files were loaded from steam

here is the error in the logs:

Fallback handler could not load library /media/Disk2/7d2d/steamcmd/7dtd_server/7DaysToDieServer_Data/Mono/libKernel32

Fallback handler could not load library /media/Disk2/7d2d/steamcmd/7dtd_server/7DaysToDieServer_Data/Mono/libKernel32.so

Fallback handler could not load library /media/Disk2/7d2d/steamcmd/7dtd_server/7DaysToDieServer_Data/Mono/Kernel32

Fallback handler could not load library /media/Disk2/7d2d/steamcmd/7dtd_server/7DaysToDieServer_Data/Mono/libKernel32

Fallback handler could not load library /media/Disk2/7d2d/steamcmd/7dtd_server/7DaysToDieServer_Data/Mono/libKernel32.so

Fallback handler could not load library /media/Disk2/7d2d/steamcmd/7dtd_server/7DaysToDieServer_Data/Mono/libKernel32

there is no generated mono folder in the 18.1 (b2) there is a folder called, MonoBleedingEdge

also looking at the backup I made of the entire 17.4 there is a folder called mono, but no folder called MonoBleedingEdge

 
Last edited by a moderator:
Not sure since I can't access the server right now, , but I think these lines are in my log too. Nothing to worry about.

Also I don't think "Could not initialize GameServer" is a good sign. Maybe turn off EAC and test again.

 
Well even trying the default that come with the system is not generation region files. at this point there is something broken with the Linux server, and until I hear otherwise I am shelving this version. I don't have days to mess around with a server software that is clearly not working as intended. I feel I have put in enough time trying to get this to work. I cleared out all steam and 7d2die files and reloaded steam, patched steam, and downloaded the experimental build that should have been released with the client build 18.1 (b2). Or had at lease some information that there are some issues with it. Disabling features that are clearly on with the default server config is not a realistic solution. The aggravation level with this is increasing to the point where I will move on to another game shortly unless someone offers a viable suggestion/solution. Not to mention that even having them build can take a hour or more. Not that I have seen any region files build in the linux version, this is the same server I was using before with 17.4 clearly something has changed, even the 18.1 (b155) version does not generate region files.

 
Yeah, your Server isn't initializing. Had this problem too ... tried to reinstall Steam and 7DTD dedicated server itself multiple times, and also starting fresh games after deleting all save files. I didn't had a chance and no hints by others could help to solve the problem.

As a last step I decided to reinstall the whole server operating system (including switching to containers, just as a side note) ... now the 7dtd server intializes and works again.

Sorry, but I can't be of better help myself.

 
Well even trying the default that come with the system is not generation region files.
Click to expand...
There is no world generation if you use pregenerated worlds (if that's what you talking about).

at this point there is something broken with the Linux server, and until I hear otherwise I am shelving this version. I don't have days to mess around with a server software that is clearly not working as intended. I feel I have put in enough time trying to get this to work. I cleared out all steam and 7d2die files and reloaded steam, patched steam, and downloaded the experimental build that should have been released with the client build 18.1 (b2). Or had at lease some information that there are some issues with it. Disabling features that are clearly on with the default server config is not a realistic solution. The aggravation level with this is increasing to the point where I will move on to another game shortly unless someone offers a viable suggestion/solution. Not to mention that even having them build can take a hour or more. Not that I have seen any region files build in the linux version, this is the same server I was using before with 17.4 clearly something has changed, even the 18.1 (b155) version does not generate region files.
Click to expand...
I can understand your aggravation, but it isn't at all clear what the problem is, my and lots of other servers have been working flawlessly with all versions of A18.

As far as I can see you tried to generate a 16k world (which may have unknown critical bugs and probably needs days to generate on a server depending on CPU and without GPU support). And you tried to use a pregenerated world and didn't see any generation (as would be expected). If you use navezgane or one of the PREGENS, there won't be any world generation.

You might try generating a 4k or 8k world to check if worldgen works but it won't help with the main problem.

You can find the world data for PREGEN01 in <7d2d-dir>/Data/Worlds/PREGEN01, by the way.

--------

Your central problem though is really the line

Code: 
 2019-10-27T22:46:40 1001.511 ERR [steamworks.NET] Could not initialize GameServer
Just guessing, but it seems to me your server may not be able to connect and authenticate with steam. In my logs I see this instead:

Code: 
2019-10-27T17:46:48 73.341 INF StartGame done
2019-10-27T17:46:49 74.188 INF [steamworks.NET] GameServer.Init successful
2019-10-27T17:46:50 74.829 INF [DECO] written 429/603
2019-10-27T17:46:50 75.146 INF [steamworks.NET] GameServer.LogOn successful, SteamID=xxxxxxxxxx, public IP=xxxxxxxx
Could there be a firewall problem?

I also checked the error messages you got. "Fallback handler could not load library ...". These errors were harmless when I had them, BUT I did have them only in A18.0 b149.

I also got a MonoBleedingEdge directory.

Since seraphin mentioned a complete server reinstall: I use debian. Shouldn't be a reason, but you never know

 
Last edited by a moderator:
I did notice that the steamclient.so file that is downloaded from steam is about 26,243 KB the one that is installed into the base directory is 21,453 KB I have tried the default serverconfig.xml file that come with the bare install and that doesn't generate region files. I am also use the 64 bit version 7DaysToDieServer.x86_64 with a 64bit OS, the really annoying thing is that I can restore the 17.4 version from a save and it works. the system is installed on an Ubuntu server 18.10

I am thinking something has changed. what I have no idea, but if steam isn't running when it should be, that sounds like a configuration to me. Since there is no configuration for steam in 7d2die server that I am aware. what can I do to validate that that is the issue or that its not configured properly. i have used this link (https://unixblogger.com/setup-7-days-to-die-server/) as a general guide to set it up, what should be different from this?

 
I think I found the issue using a suggestion in another thread with a strace : I found these

openat(AT_FDCWD, "/lib/x86_64-linux-gnu/steamclient.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

15490 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/tls/steamclient.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

15490 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/steamclient.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

15490 openat(AT_FDCWD, "/lib/steamclient.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

So I went over to the first folder listed and made a symbolic link to the steamclient.so

ln -s /media/Disk2/steamcmd/bin/linux64/steamclient.so /lib/x86_64-linux-gnu

this allowed the server to show up in the server listings

 
I think I found the issue [...]
Click to expand...
Thank you very much for sharing your solution and your knowledge.

As I already mentioned, I already re-installed my homeserver using containers (Ubuntu 19.10 Server as host).

First try in a container (Ubuntu 16.04 LTS, steamcmd from multiverse repository, default installation path) it already worked.

Second try in another container (Ubuntu 19.10, steamcmd from multiverse repository, custom path for 7dtd dedicated server) it didn't work again, caused by this initialization error. Thanks to your post, I've been able to solve this problem on first try.

Most likely this would have solved the problem before re-installing my homeserver too, though I propably wouldn't have started to experiment with containers then.

Anyway, thank's again for sharing your solution.

 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top