Jump to content

Edit History

Please note that revisions older than 365 days are pruned and will no longer show here
KaldaraFox

KaldaraFox

Okay, I've added ports 27027 and 27043-27045 to my router table.

 

I've run sudo uwf deny on ports 27015 and 27031-27033 on the Linux box running my servers.

 

I've run sudo uwf allow on ports 27027 and 27043-27045 on the Linux box running my servers.

 

I deleted and redefined the server I'm trying to get up and running (again - it was running just fine (now) three days ago)) and started it.

 

The log file (https://pastebin.com/n3Ry1yw7) shows that the Server Port is now 27027.

 

Yet I'm still getting that same error on first login.

 

I need help, guys. If this isn't where I go to get it, I need to know where I can go. No response for half a day on the Discord, the server software folks (AMP) say it's a TFP issue (I think they mean "it's not us so it must be someone else" but that might be Steam/Valve).

 

I'm up against it here.

 

I can't do this alone and there doesn't seem to be anyone who will respond with anything useful.

 

It's certainly not the "don't use 27015" issue because I'm no longer using that one and the error has not changed.

 

I kind of knew that was going to be the result because I've been using 27015 for months with no problem until day before yesterday.

 

I've been at this non-stop for about 18 hours now and I'm at the end of my rope.

 

Where is support? If not here, where do I go for it?

What is happening here? Why is it just happening now (I've made no changes to my system or my game parameters other than trying to add a new map and this last failure was using a generic, pregen map (Navezgane)). Something was changed somewhere in the chain of execution between my desktop server and where the game gets started and sets up communication and I can't even find out who is responsible for let alone ask them how to fix it.

 

The actual error text is here (it's in context in the log file, but I thought it might be simpler to give just that part here).

13:23:28
 
=================================================================
src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (3514) : Trying to close low level socket support, but we still have sockets open!
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.
=================================================================
=================================================================
Native stacktrace:
=================================================================
0x7ff4a3d15062 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/294420/7DaysToDieServer_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so :
0x7ff4a3cbdd3d - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/294420/7DaysToDieServer_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so :
0x7ff4a3c43250 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/294420/7DaysToDieServer_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so :
0x7ff4aa51c520 - /lib/x86_64-linux-gnu/libc.so.6 :
0x7ff257dd97bb - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff2578ff103 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257906190 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257b26214 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257b22b89 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d71303 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d7221a - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d73103 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d73b61 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256c2cbb0 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256e2acbd - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f9a3c2 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f97128 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f99928 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f99f58 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a8046a - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a7e541 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a7ec3b - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a82a05 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff4aa56eac3 - /lib/x86_64-linux-gnu/libc.so.6 :
0x7ff4aa600a40 - /lib/x86_64-linux-gnu/libc.so.6 :
=================================================================
Telemetry Dumper:
=================================================================
Thread 0x7ff28cffd640 may have been prematurely finalized* Assertion at mono-threads.c:702, condition `info' not met, function:mono_thread_info_current,
src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (3514) : Trying to close low level socket support, but we still have sockets open!

Shutdown handler: cleanup.

System info is displayed in the log file, but I'll repeat it here as well:

 
2023-11-02T18:23:32 0.486 INF System information:
2023-11-02T18:23:32 0.486 INF OS: Linux 5.15 Ubuntu 22.04 64bit
2023-11-02T18:23:32 0.504 INF CPU: AMD Ryzen 5 1600 Six-Core Processor (cores: 12)
2023-11-02T18:23:32 0.505 INF RAM: 32034 MB
2023-11-02T18:23:32 0.505 INF GPU: Null Device (128 MB)

2023-11-02T18:23:32 0.509 INF Graphics API: NULL 1.0 [1.0] (shader level 5.0)

If there's anything else I need to provide, please let me know.

 

I did redact my server's actual IP address every time it showed in the log. I can't imagine that's necessary and it seemed a bad idea to publish that openly.

 

KaldaraFox

KaldaraFox

Okay, I've added ports 27027 and 27043-27045 to my router table.

 

I've run sudo uwf deny on ports 27015 and 27031-27033 on the Linux box running my servers.

 

I've run sudo uwf allow on ports 27027 and 27043-27045 on the Linux box running my servers.

 

I deleted and redefined the server I'm trying to get up and running (again - it was running just fine (now) three days ago)) and started it.

 

The log file (https://pastebin.com/n3Ry1yw7) that the Server Port is now 27027.

 

Yet I'm still getting that same error on first login.

 

I need help, guys. If this isn't where I go to get it, I need to know where I can go. No response for half a day on the Discord, the server software folks (AMP) say it's a TFP issue (I think they mean "it's not us so it must be someone else" but that might be Steam/Valve).

 

I'm up against it here.

 

I can't do this alone and there doesn't seem to be anyone who will respond with anything useful.

 

It's certainly not the "don't use 27015" issue because I'm no longer using that one and the error has not changed.

 

I kind of knew that was going to be the result because I've been using 27015 for months with no problem until day before yesterday.

 

I've been at this non-stop for about 18 hours now and I'm at the end of my rope.

 

Where is support? If not here, where do I go for it?

What is happening here? Why is it just happening now (I've made no changes to my system or my game parameters other than trying to add a new map and this last failure was using a generic, pregen map (Navezgane)). Something was changed somewhere in the chain of execution between my desktop server and where the game gets started and sets up communication and I can't even find out who is responsible for let alone ask them how to fix it.

 

The actual error text is here (it's in context in the log file, but I thought it might be simpler to give just that part here).

13:23:28
 
=================================================================
src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (3514) : Trying to close low level socket support, but we still have sockets open!
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.
=================================================================
=================================================================
Native stacktrace:
=================================================================
0x7ff4a3d15062 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/294420/7DaysToDieServer_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so :
0x7ff4a3cbdd3d - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/294420/7DaysToDieServer_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so :
0x7ff4a3c43250 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/294420/7DaysToDieServer_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so :
0x7ff4aa51c520 - /lib/x86_64-linux-gnu/libc.so.6 :
0x7ff257dd97bb - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff2578ff103 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257906190 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257b26214 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257b22b89 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d71303 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d7221a - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d73103 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256d73b61 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256c2cbb0 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256e2acbd - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f9a3c2 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f97128 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f99928 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff256f99f58 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a8046a - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a7e541 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a7ec3b - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff257a82a05 - /home/amp/.ampdata/instances/PhodgePodge7DTDZombieWarMap01/seven-days-to-die/linux64/steamclient.so :
0x7ff4aa56eac3 - /lib/x86_64-linux-gnu/libc.so.6 :
0x7ff4aa600a40 - /lib/x86_64-linux-gnu/libc.so.6 :
=================================================================
Telemetry Dumper:
=================================================================
Thread 0x7ff28cffd640 may have been prematurely finalized* Assertion at mono-threads.c:702, condition `info' not met, function:mono_thread_info_current,
src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (3514) : Trying to close low level socket support, but we still have sockets open!

Shutdown handler: cleanup.

System info is displayed in the log file, but I'll repeat it here as well:

 
2023-11-02T18:23:32 0.486 INF System information:
2023-11-02T18:23:32 0.486 INF OS: Linux 5.15 Ubuntu 22.04 64bit
2023-11-02T18:23:32 0.504 INF CPU: AMD Ryzen 5 1600 Six-Core Processor (cores: 12)
2023-11-02T18:23:32 0.505 INF RAM: 32034 MB
2023-11-02T18:23:32 0.505 INF GPU: Null Device (128 MB)

2023-11-02T18:23:32 0.509 INF Graphics API: NULL 1.0 [1.0] (shader level 5.0)

If there's anything else I need to provide, please let me know.

 

I did redact my server's actual IP address every time it showed in the log. I can't imagine that's necessary and it seemed a bad idea to publish that openly.

 

×
×
  • Create New...