Jump to content

Improvements for the dedicated server


Alloc

Recommended Posts

Most likely your issue wasn't the permissions of the features but your own permission that should be higher (i.e. make yourself an level 0 admin). Maybe that's what you meant by your edit though ;)

Link to comment
Share on other sites

Yes, same as with everything else save related (especially admins.xml): Use different savegamefolders.

 

 

If i set in the serverconfig.xml the folder

 

 

<property name="AdminFileName" value="serveradmin.xml"/> <!-- Server admin file name -->

 

into

 

 

<property name="AdminFileName" value="Server2\serveradmin.xml"/> <!-- Server admin file name -->

 

then the server 2 use the webpermission in folder Server2\ ? right ?

Link to comment
Share on other sites

Crash Dump. Any help would be great

 

[s_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.Setting breakpad minidump AppID = 251570


Native stacktrace:


   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x91772) [0x7f458759a772]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x348a5) [0x7f458753d8a5]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10) [0x7f4588b28d10]
   /lib/x86_64-linux-gnu/libpthread.so.0(pthread_mutex_lock+0x4) [0x7f4588b21c84]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x135843) [0x7f458763e843]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(mono_object_new+0x7) [0x7f4587640090]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(mono_exception_from_name_domain+0x35) [0x7f45875fca7e]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(mono_exception_from_name_msg+0xc) [0x7f45875fcb91]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x347ec) [0x7f458753d7ec]
   /lib/x86_64-linux-gnu/libc.so.6(+0x352f0) [0x7f4587d4e2f0]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x12af0) [0x7f4588b2aaf0]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x953ed1) [0x7f44e9e68ed1]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x95164c) [0x7f44e9e6664c]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x9481f9) [0x7f44e9e5d1f9]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x948265) [0x7f44e9e5d265]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x76aa) [0x7f4588b1f6aa]
   /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f4587e1feed]


Debug info from gdb:




=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

 

 

Here is the full log

http://pastebin.com/gXDU7w52

Link to comment
Share on other sites

Hi Alloc,

 

Was wondering if you could shed some light on a little quirk we're having. I thought that once all the players left the server, time stopped and all entities were despawned. For some strange reason there are several persistent zeds that will not go away.

 

"Sometimes" the killall command won't get rid of them. I'll do the killall to kill them and then hit it again to get rid of the bodies. If I hit it a third time, those "phantom" Zombies I just killed may or may not be on the map, but they are listed in the killall return text even when the le command says nothing. If I do the le command, the highlighted zombieArlene in the picture below is not in the list. She shouldn't even be there since that chunk has never been loaded.

 

They even come back after a reboot.

 

Log file via PM if requested.

 

pELfsD8.png

Link to comment
Share on other sites

Hi Alloc,

 

Was wondering if you could shed some light on a little quirk we're having. I thought that once all the players left the server, time stopped and all entities were despawned. For some strange reason there are several persistent zeds that will not go away.

 

"Sometimes" the killall command won't get rid of them. I'll do the killall to kill them and then hit it again to get rid of the bodies. If I hit it a third time, those "phantom" Zombies I just killed may or may not be on the map, but they are listed in the killall return text even when the le command says nothing. If I do the le command, the highlighted zombieArlene in the picture below is not in the list. She shouldn't even be there since that chunk has never been loaded.

 

They even come back after a reboot.

 

Log file via PM if requested.

 

 

I also have this ghost zombies on my server, but they are gone with the daylie restart.

Link to comment
Share on other sites

Anyone have any clue how to fix this? Not sure if its causing problems or not.

 

WRN [EAC] Log: [Cerberus] Connection attempt to the back-end failed! Reconnecting in 60 seconds..

 

Ubuntu 15.04

No fix but it's also no issue. That's normal output for now.

 

 

 

Crash Dump. Any help would be great

 

Native stacktrace:
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x91772) [0x7f458759a772]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x348a5) [0x7f458753d8a5]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10) [0x7f4588b28d10]
   /lib/x86_64-linux-gnu/libpthread.so.0(pthread_mutex_lock+0x4) [0x7f4588b21c84]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x135843) [0x7f458763e843]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(mono_object_new+0x7) [0x7f4587640090]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(mono_exception_from_name_domain+0x35) [0x7f45875fca7e]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(mono_exception_from_name_msg+0xc) [0x7f45875fcb91]
   /home/sdtd/engine/7DaysToDieServer_Data/Mono/x86_64/libmono.so(+0x347ec) [0x7f458753d7ec]
   /lib/x86_64-linux-gnu/libc.so.6(+0x352f0) [0x7f4587d4e2f0]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x12af0) [0x7f4588b2aaf0]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x953ed1) [0x7f44e9e68ed1]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x95164c) [0x7f44e9e6664c]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x9481f9) [0x7f44e9e5d1f9]
   /home/sdtd/engine/7DaysToDieServer_Data/Plugins/x86_64/steamclient.so(+0x948265) [0x7f44e9e5d265]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x76aa) [0x7f4588b1f6aa]
   /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f4587e1feed]

Hm, think that one is new ... Does this happen regularly or was it just that one time?

 

 

 

Was wondering if you could shed some light on a little quirk we're having. I thought that once all the players left the server, time stopped and all entities were despawned. For some strange reason there are several persistent zeds that will not go away.

Have heard of this before (think it was Devidian ;) ). No idea, haven't had this myself so hard to debug. It's not an issue in the mod as it simply uses the data provided by the game. Which makes me even more curious as this *could* be an actual issue ...

 

They even come back after a reboot.

And that's the really strange part. I mean they shouldn't be in a random location on the map in the first place but after restarting the server there is even less reason for them.

 

Are you sure though that this location has *really* never been visited? No map tiles at all? No offline user shown there?

Link to comment
Share on other sites

Hm, think that one is new ... Does this happen regularly or was it just that one time?

 

No this is happening all the time. There are a few spots in the map that will no longer load. (Everything around the chunk loads but not that square section. if a player steps into the chunk the world stops loading for all others players until i teleport them out. Also if they log off while in this chunk when they log back in they will be stuck at the "Starting Game" screen since the server will not send any map info to them. again the world will stop loading for all other players during this time.

Link to comment
Share on other sites

Ok, then please create a new thread in bugs and PM me the link. This is definitely not about the server mod and will only clutter this topic.

 

Also I'm seeing two things here: You said you got crashes of the server but lately you've been talking about loading issues. Please detail both more in that topic, as well as ideally provide multiple logs of the crashes. Also, if the loading issue is reproducible by a player being around a certain location please upload that region file and give me the coordinates where this happens.

Link to comment
Share on other sites

Wow. Did you check what was most of this data? E.g. was it like 90% the <steamid> -> <entityid> output in the logs on player connects or something like that?

 

I didn't check the data, I'd seen how long it took to open a 15MB log on my system and didn't fancy my chances with a 13GB one. I have a good idea what the error message was though, as I had my nose in the log files alot at the time:

 

2016-07-01T19:38:20 13098.991 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.991 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.993 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)

Link to comment
Share on other sites

I didn't check the data, I'd seen how long it took to open a 15MB log on my system and didn't fancy my chances with a 13GB one. I have a good idea what the error message was though, as I had my nose in the log files alot at the time:

 

2016-07-01T19:38:20 13098.991 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.991 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.992 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)
2016-07-01T19:38:20 13098.993 ERR Block on position 2066, 121, -6571 with value id=1455 px=1 py=0 pz=-2 should be a parent but is not! (3)

 

I see this a lot on my server too. From what I can tell, it is usually a car that someone started to disassemble. We had one near our community base that would spam the log every time someone walked passed it.

 

If I notice one of these cars in the log, I'll tp over and blow it up with a rocket to prevent the log spam.

Link to comment
Share on other sites

I didn't check the data, I'd seen how long it took to open a 15MB log on my system and didn't fancy my chances with a 13GB one.

If you get another such log (> 1 GiB I'd say) I wouldn't mind having a look if you can provide it :)

Link to comment
Share on other sites

If I notice one of these cars in the log, I'll tp over and blow it up with a rocket to prevent the log spam.

 

Ah interesting. I had no idea what it was, but as the logs often have stuff like this in, I just let it go. Next time I see it I will try what you have suggested.

 

- - - Updated - - -

 

If you get another such log (> 1 GiB I'd say) I wouldn't mind having a look if you can provide it :)

 

Sure, no problem :)

Link to comment
Share on other sites

pELfsD8.png

 

I also have this ghost zombies on my server, but they are gone with the daylie restart.

 

If you get this again can you please check the coordinate of the zombie shown and send me both log + that coord please?

Link to comment
Share on other sites

If you get this again can you please check the coordinate of the zombie shown and send me both log + that coord please?

 

Someone finally visited that area and now she's gone. I have no one on the map right now, yet there are 19 Hostiles spread out all over the place. I thought they were supposed to despawn if no one is online. Is that still true?

Link to comment
Share on other sites

Someone finally visited that area and now she's gone. I have no one on the map right now, yet there are 19 Hostiles spread out all over the place. I thought they were supposed to despawn if no one is online. Is that still true?

I think if they are honed in on a player they do not.

Link to comment
Share on other sites

Someone finally visited that area and now she's gone. I have no one on the map right now, yet there are 19 Hostiles spread out all over the place. I thought they were supposed to despawn if no one is online. Is that still true?

 

If the chunk is unloaded (which it should when no one is around) they should theoretically be unloaded, yes.

Link to comment
Share on other sites

If you get this again can you please check the coordinate of the zombie shown and send me both log + that coord please?

 

Here ya go Alloc. I've got two zombies that are out in the radiation zone, but they do not show up with the list entities command. The coords for the worst one is roughly 6700S 9100E. After getting the screenshots, I did a killall command. She was removed, but the killall command still reports back about 30 zombies and/or their corpses. Link to log file.

 

6KsJIZC.png

 

dAk11kx.png

Link to comment
Share on other sites

Hey Alloc :)

I read somewhere (illy.bz?) that you are changing the way you integrate Coppis into your server fixes. Are you removing it completely, or not updating it, or integrating it, or?

We use tcch to hide our chat hooks, will we need to install Coppis DLL separately or will tcch functionality remain in the server fixes Mod?

 

Thanks :)

 

 

------------------

Edit after coffee:

(from the latest changeset on illy.bz)

* CoppisAdditions removed: Including that will cause all sorts of trouble/confusion as they're also updated by Coppi himself. Download can be found in [https://7daystodie.com/forums/showthread.php?44835-Coppi-MOD-New-features his thread]

------------------

Edited by zigstum (see edit history)
Link to comment
Share on other sites

I recently started a new seed on my server and upgraded to Valmod 3.25. Now when I use the web map's "inventory viewer" the server restarts...it's not like a crash as we lose no time and no forges are bugged. There are no errors in the logs, but nor are there shutdown messages. This is very odd behavior....anyone else seen this?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...