7Days 18 Stable - VM Redux - Server Still Initiallizing (Even with 24GB Ram, 4 Cores)

Status
Not open for further replies.
T

TallTim

Refugee
I swear, how much does 18 Stable want. I have a new rig that I'm using to run other things, and I'd like to run a Virtual Machine on top for my friend and I to play in. I've set up VM's for 17 before and they work, but 18 is another beast entirely.

My Rig Specs:

CPU: AMD Ryzen 9 3900X 12-Core 4.0 GHz

RAM: 64GB

OS: Windows 10 Pro

HD: 4TB Western Digital

Virtualbox 6.0 VM Setup:

CPU: 4 cores

RAM: 24GB

HD: 50GB allocated (dynamic) / Only used 17GB so far

OS: Ubuntu 64 bit 18.04

I start up my dedicated server using 18 Stable then look for the "INF Startgame Done" to fire up my client and see if I can log into it.

I do so, and the client says "Server is still initializing, try again in a minute"

LIES.

Here's my output from the "Startgame Done" part until I get kicked for it not being ready:

2019-11-19T15:32:21 125.117 INF StartGame done

2019-11-19T15:32:21 125.453 ERR [steamworks.NET] Could not initialize GameServer

2019-11-19T15:32:26 130.581 INF Calculating hashes took 5859 ms (world size 683 MiB)

2019-11-19T15:34:41 265.607 INF NET: LiteNetLib: Connect from: 192.168.1.11:62390

2019-11-19T15:34:41 265.613 INF Started thread NCS_Reader_0_0

2019-11-19T15:34:41 265.614 INF Started thread NCS_Writer_0_0

2019-11-19T15:34:41 265.618 INF Started thread NCS_Reader_0_1

2019-11-19T15:34:41 265.618 INF Started thread NCS_Writer_0_1

2019-11-19T15:34:41 265.619 INF [NET] PlayerConnected EntityID=-1, PlayerID='', OwnerID='', PlayerName=''

2019-11-19T15:34:41 265.622 INF NPCID.Write

2019-11-19T15:34:41 265.693 INF NPPL.Read

2019-11-19T15:34:41 265.732 INF PlayerLogin: Maxx/Alpha 18.1

2019-11-19T15:34:41 265.732 INF Client IP: 192.168.1.11

2019-11-19T15:34:41 265.733 INF Kicking player (Server is still initializing): EntityID=-1, PlayerID='76561197971026909', OwnerID='', PlayerName='Maxx'

So the server sees the player, but just decides "Oops, I'm not ready yet" and kicks me out.

This is really frustrating -- any ideas? I know the system requirements aren't it -- you telling me with 24GB this game won't fully initialize? And get this, I'm just trying to test it out with the "Navezgane" default map, too.

What the hell man... so maddening.

 
Last edited by a moderator:
you telling me with 24GB this game won't fully initialize?
Click to expand...
No one is saying this.

Look elsewhere for the problem, it's not your ram.

This is where things seem to go wrong,

2019-11-19T15:32:21 125.453 ERR [steamworks.NET] Could not initialize GameServer

but more info from output logs and server config files would be needed to figure it out.

 
With only 4 cores, it's going to take a long time to make the map. Probably you started one, and stopped it before it was finished because you thought the process was hung. So the map wasn't made, but it was done enough that the folder with some of the data exists.

I'm just guessing though since there isn't enough data to make a solid determination.

 
Sure, I can post that.

Server Config -- https://pastebin.com/iTUKWiwt

Output.log -- https://pastebin.com/dnMm11Gz

My favorite part is where it says "INF Startgame Done" and yet the client logging in gets the message of "Server hasn't initialized yet - try again in a few minutes". If it wasn't started, then why does the log have that output?

It baffles and frustrates me.

- - - Updated - - -

With only 4 cores, it's going to take a long time to make the map. Probably you started one, and stopped it before it was finished because you thought the process was hung. So the map wasn't made, but it was done enough that the folder with some of the data exists.
I'm just guessing though since there isn't enough data to make a solid determination.
Click to expand...
Nope - using Navezgane as the test for this VM, so it exists just fine. Output log has the entry -- "INF World.Load: Navezgane" which tells me it loaded okay.

Also - I've had steam errors in the log before and it matters little with the 17 VM I built - I can connect local to that just fine.

 
2019-11-19T16:38:47 0.162 WRN Localization: Duplicate key "xuiWater" found! Please check Localization file. Skipping entry...

That's an issue we created and is fixed for a future update. It's harmless for the most part.

Try enabling steam networking by removing steam networking in your serverconfig file

From:

<property name="ServerDisabledNetworkProtocols" value="SteamNetworking"/>

To:

<property name="ServerDisabledNetworkProtocols" value=""/>

Also make sure your ports are forwarded correctly for the VM. (Honestly not sure how VM's work, never used it, but worth a shot)

I've had a few issues like this with my local dedi on my 2nd PC and these tips have helped.

Good luck!

 
2019-11-19T16:39:34 46.799 ERR [steamworks.NET] Could not initialize GameServer

Ah, damn, after looking at your serverconfig files again, it looks like you do have SteamNetworking enabled already. That means you've got an issue registering your server with Steam. Again, I have no clue about setting up a VM, but probably something to do with it's network settings.

 
Your error is on line 31. You have corrupted client files.
Click to expand...
The line you refer to is:

"WRN Localization: Duplicate key "xuiWater" found!"

I performed a completely new install after wiping the client files and validated via steam -- "All files successfully validated."

So I don't think that is it.

 
2019-11-19T16:39:34 46.799 ERR [steamworks.NET] Could not initialize GameServer
Ah, damn, after looking at your serverconfig files again, it looks like you do have SteamNetworking enabled already. That means you've got an issue registering your server with Steam. Again, I have no clue about setting up a VM, but probably something to do with it's network settings.
Click to expand...
I've tried both variants, with the "SteamNetworking" in the parameters and without, with no success. I don't know how 7Days interacts with Steam, but I do know that my VM is a bridged connection in full promiscuous mode - it sees everything on my local LAN. I can ping it, and it can ping and do DNS lookups just fine.

There are no ports involved here because it isn't NAT, its like plugging in a cable on a network hub - all ports are in the same "collision domain" from a network standpoint.

I'll go over my settings again, but I'd really like to nail this down. I even did a "strace" stack and had someone look at it, but it didn't produce anything obvious.

I just don't understand how I can fully configure a 7 Days v17 dedicated server under the same VM software with zero problems, and all of a sudden using 18 Stable with the SAME PROCEDURES in building and setting it up that it doesn't want to work.

If there was a steam problem, why was I able to use steamcmd in the very same VM to download 18 Stable in the first place? It accepted my login to Steam and I was verified and okay.

Just baffling to me...

(Edit: I just checked my 7Days 17 VM setup and the networking portion is ALSO bridged -- and that works fine.)

As a follow up I checked the ports Steam wants to use here:

https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711

I have all of them forwarded through my router - so I don't get what the problem is.

Further edit: Was looking into the steamclient.so error on shutdown and got to this reference -- https://developer.valvesoftware.com/wiki/SteamCMD#Unable_to_locate_a_running_instance_of_Steam

But when you attempt to do a symbolic link as it suggests, that fails. Some other searching indicates that as far back as 2003 SteamPipe has been throwing this error and it can be ignored.

 
Last edited by a moderator:
Just as a test, in your serverconfig.xml try:

1) set: <property name="ServerVisibility" value="1"/>

to: "2" instead of "1"

2) set: <property name="ServerDisabledNetworkProtocols" value=""/>

to: <property name="ServerDisabledNetworkProtocols" value="SteamNetworking"/>

restart and see if your connection experience is any different/better.

 
This is what I have and it works here, I think it was the only way I got it to work, haven't changed it since A17 came out.

<property name="ServerVisibility" value="1"/> <!-- 1 = friends only -->

<property name="ServerDisabledNetworkProtocols" value=""/>

 
Beelzybub, I tried what you suggested and it still says the server isn't initialized yet, even though the log output says the that its done loading. Steamworks.NET still complains, but I have that happening in my v17 VM and it works fine. Beats me, man. Something materially different about 18 somehow.

- - - Updated - - -

shelter, this is how I had it set up originally and it wasn't working -- you're right, it will work in v17, just don't know what is so messed up about 18 that it won't even work.

 
Just tried 6 cores for the hell of it in the VM setup with the 24GB of RAM -- same result. Visibility is "1" for the server and there's nothing disabled in networking protocols.

Any ideas?

While I was taking a break I installed tensorflow and the Nvidia NNCuda libraries on another box -- and that was easier than getting this server running properly.

Sobering, don't you think?

 
I'd try another OS since they're east to spin up in VM. I can run A18.x dedi in Linux Mint 19

without any problems. Also I've seen some reports that LiteNetLib can be wonky with ipv6,

so maybe try disabling that.

 
Beelzybub, I'll give that a go when I feel like burning more time. For now I decided to try out a hosted service. The funny part? The moment I uploaded a generated map to my server it started rebooting like mad. Now its THEIR problem and they have to figure out why v18 is being a pain in the ass :)

I wonder if they'll figure it out...lol

 
Linux Mint was a no-go. Privilege escalation errors, and when run under "sudo su" it craps out with fault.

7 Days 18 "stable" sure is a fun thing to get running on a VM. Oh, I was using 20GB and 4 cores. Still haven't heard back from the hosting service, I guess they're going crazy trying to get 18 to run too.

Can't believe Unity is that much of a pain in the ass.

 
I just tried to replicate this but wasn't able to.

Created a Linux Mint 19.2 VM in Virtualbox

Installed 7D2D dedi. (18.1)

Ran server.

Connected from another machine no problem. Server name showed up in the

game client when choosing "Join a Game". Connected to the game and played

for a bit.

Server log: View attachment 30735

Maybe you can compare this to your output log and figure out where things

go wrong. Also, dunno why but linux doesn't do eof normally, but the log

looks ok if you use notepad++.

I would guess that you are not having a game issue, but a network issue.

output_log__2019-11-25__01-38-01.txt

 

Attachments

Last edited by a moderator:
I'd need to know more about your VM setup -- number of cores, RAM, Network (NAT or Bridged?)

I'll look at the output log in the meantime. Just seems that Linux mint wants to restrict user privilege escalation at all costs.

 
I'd need to know more about your VM setup -- number of cores, RAM, Network (NAT or Bridged?)
I'll look at the output log in the meantime. Just seems that Linux mint wants to restrict user privilege escalation at all costs.
Click to expand...
It's a single connection, bridged, I tried NAT but it was too much trouble. 2 cores, 4 gigs.

I didn't change any user permissions on the Mint VM, everything is just as it was iinstalled.

I installed, ran updates, installed Steam, installed 7D2D dedi, created new RWG game.

That's it.

 
Status
Not open for further replies.
Back
Top