Jump to content
  • 0
Sign in to follow this  
Energritz_

UNDER REVIEW [YLD-8973] Server goes into Negative Values

Question

This all happened while i was asleep, during graveyard hours.

Just another strange Early Access occurrence

At some point after someone logged on, server threw this error:

[EX] [01:48:17.87] System.NullReferenceException:
	TerrainEngine.GameObjectPoolInfo.CloseObject (GameObject)
	ylands.DelayedUnpooler.LateUpdate ()[MM] 17
[WN]U [-10:-03:-51.-92] Can not play a disabled audio source
[EX] [-10:-02:-45.-26] System.NullReferenceException:
	TerrainEngine.GameObjectPoolInfo.CloseObject (GameObject)
	ylands.DelayedUnpooler.LateUpdate ()[MM] 7
[IN] [-09:-58:-42.-59] Response #125: 400 44B ...
	

Now the server has Negative values? error is thrown twice and Response code is now #400, which means unable to connect

to Ba servers, prior to this all connections are #200.. there is a player that is still connected, but doesn't stay online for long.

These negative values i have never seen before,  at some point it has steam issues..

[IN] [-07:-42:-17.-86] Response #258: 400 44B ...
[ER] [-07:-42:-04.-68] SteamServersDisconnected result=k_EResultNoConnection
	ylands.SteamIntegration.SteamManager.OnSteamServersDisconnected (SteamServersDisconnected_t)
	Steamworks.Callback`1[Steamworks.SteamServersDisconnected_t].OnRunCallback (IntPtr, IntPtr)
	Steamworks.NativeMethods.SteamGameServer_RunCallbacks ()
	Steamworks.GameServer.RunCallbacks ()
	ylands.SteamIntegration.CommonSteamApi.RunCallbacks ()
	ylands.SteamIntegration.SteamManager.Update ()
[IN] [-07:-41:-48.-95] SteamServersConnected
[IN] [-07:-41:-16.-59] Response #259: 400 44B ...
[IN] [-06:-56:-49.-66] Response #302: 400 44B ...
[ER] [-06:-56:-03.-11] SteamServersDisconnected result=k_EResultNoConnection
	ylands.SteamIntegration.SteamManager.OnSteamServersDisconnected (SteamServersDisconnected_t)
	Steamworks.Callback`1[Steamworks.SteamServersDisconnected_t].OnRunCallback (IntPtr, IntPtr)
	Steamworks.NativeMethods.SteamGameServer_RunCallbacks ()
	Steamworks.GameServer.RunCallbacks ()
	ylands.SteamIntegration.CommonSteamApi.RunCallbacks ()
	ylands.SteamIntegration.SteamManager.Update ()
[IN] [-06:-55:-47.-36] Response #303: 400 44B ...
[ER] [-06:-55:-30.-06] SteamServerConnectFailure result=k_EResultNoConnection
	ylands.SteamIntegration.SteamManager.OnSteamServerConnectFailure (SteamServerConnectFailure_t)
	Steamworks.Callback`1[Steamworks.SteamServerConnectFailure_t].OnRunCallback (IntPtr, IntPtr)
	Steamworks.NativeMethods.SteamGameServer_RunCallbacks ()
	Steamworks.GameServer.RunCallbacks ()
	ylands.SteamIntegration.CommonSteamApi.RunCallbacks ()
	ylands.SteamIntegration.SteamManager.Update ()
[IN] [-06:-55:-10.-91] SteamServersConnected
	

Negative goes into Positive eventually

[IN] [-01:-01:-24.-48] Response #646: 400 44B ...
[IN] [-01:00:-23.-18] Response #647: 400 44B ...
[IN] [00:00:40.42] Response #648: 400 44B ...
[IN] [00:01:41.68] Response #649: 400 44B ...
	

Still the #400 persists, meaning either the error has broken the server or there is some kind of issue at Ba

I load up the game to see if the server was appearing on the list, it wasn't there.., And a final shutdown error:

[IN] [01:27:45.42] DsState: Quitting
[WN] [01:27:45.43] NullPersistentStorageManager WriteFile
	ylands.NullPersistentStorageManager.WriteFile (String, Byte[], StorageType)
	Analytics.OnSessionQuit (EventSessionQuit)
	EventDispatcher.DispatchEvent[EventSessionQuit] (EventSessionQuit)
	ylands.SessionLifecycle.DoExit (String)
	ylands.SessionLifecycle.Exit (String)
	ylands.Quitter.GracefulQuit ()
	ylands.HeadlessServerManager.Shutdown ()
	ylands.HeadlessServerManager+<DelayedShutdownCoro>c__Iterator1.MoveNext ()
	UnityEngine.SetupCoroutine.InvokeMoveNext (IEnumerator, IntPtr)
	

 

 

Share this post


Link to post
Share on other sites

2 replies to this bug / suggestion

Recommended Posts

  • 0

Update for this:

Found out my host does things with the system clock, meaning once i set the clock for Sydney time, disconnect from the VM, not log after the time is changed back...

which then in turn causes the server to act weird, like what you see above, since the time is being reset to UTC rather than +10 AEDT, its subtracting those hours in between.

followed by going into #400 error when posting and receiving a response.

I have contact the host, they told me they run everything at UTC.. offered a fix which did not work, and now I've just left the clock alone, even though its wrong.

Upon finding this out, correcting to the correct time, the server attempts a revival function, and fixed itself.

However this is still rather bad.. i don't think the system clock should be able to kill the server like that...

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×