Windows Strange error in dedicated server

S

Spadje

Refugee
After updating today I started seeing this warning message in the console

2025-09-29T19:07:52 53.599 WRN [EOS] [LogEOSRTC - Warning] TickTracker Tick is delayed. TimePeriod=[10.039716s] TickIntervalThreshold=[0.100000s] MaxTickInterval=[0.377759s] MaxExecutionTime=[0.000170s] TicksCount=[193] ExpectedTicksCount=[1003]

Is there something I did wrong or is this something I can just ignore?

The dedicated server specs are
AMD 3900x
64GB DDR4
Western Digital Black 1TB NVME
nVidia 1080
Gigabit internet and LAN, hardwired to router

Thanks!
 
If you're on 2.4, you can try restoring a backup and downloading the update again plus verifying your game files. If that doesn't work, then it might be something the devs have to fix on their end.
 
Oh my god, I'm so relieved I'm not the only one having this problem.
I was worried it was due to my self-developed mods.

It's been showing up in my logs since the last update to 2.4.

We'll see if TFP addresses this or perhaps fixes it.

But I am using Linux dedicated server ... so this is not only affecting os=windows ...
 
Same error in logs since updating to v2.4(b5). Windows x64, NO EAC, verified files, unmodded, new game, offline (SP). Just an educated guess, but looks like Epic (EOS) has some realtime clock or communication (RTC) related bugs in their software, that are at least 3 years old? AFAIK EOS handles cross-platform play, authentication and server listings.

Removing EOS from the "crossplatform=" line in "7 Days to Die\platform.cfg" had the following results:

Eliminated the OP's error entirely, but...
Also threw a warning about EOS being a dependency for Discord integration (I don't use this feature) and
Corrupted my save - was still in the same world map at the same time, but had fully reset character's position and data to a fresh toon starting state. Can only assume this means most character data is being saved to the EOS cloud, but the world map is still local data.
 
Last edited:
I'm getting the same on my server, ever since the 2.4 update. AI suggested to run "settargetfps 60" in the server's console, to improve (not sure if it works for your server, depending on specs, so use at your own risk). It improved the times in the warning, but it still spams my console.
 
Update: After disabling EOS, also noticed another error that was repeatedly popping up at unspecific intervals (sometimes repeatedly)

WRN [MultiBlockManager][Alignment] SetTerrainAlignmentDirty failed; no terrain-aligned block has been registered at the specified world position:

The map was generated using v2.4b5 RWG
 
Probably unrelated, but kinda curious if anyone else having the EOS TickTracker warnings/bug also has the latest version of the optional Epic Online Services App v3.0.4 installed - not the Epic Games Launcher, the optional services for it. Should look like this in Windows 11 Settings -> Apps -> Installed apps:
 

Attachments

  • EOSApp.jpg
    EOSApp.jpg
    6.6 KB · Views: 6
Last edited:
Same on my server, and one my single player client. If I open the console. I have just been playing normally. No problems yet...
 
Cernwn said:
Hopefully TFP are using the latest SDK, and NOT older ones with known vulnerabilities:
Click to expand...
No offense but you don't trouble shoot something by stabbing 20 places in the dark, test one thing at a time. Not to sound rude but most of your posts aren't helpful. Be patient, TFP's won't let us down.
 
Hello,
My server runs on a root server, and since version 2.4, I've been getting these messages in the console: "WRN [EOS] [LogEOSRTC - Warning] TickTracker Tick is delayed. TimePeriod=[10.009870s] TickIntervalThreshold=[0.100000s] MaxTickInterval=[0.858560s] MaxExecutionTime=[0.000013s] TicksCount=[549] ExpectedTicksCount=[1000]" How can I fix this?
 
Since my update to 2.4 I get the tick error as well and the server will not even launch. I am hoping to see a fix here. I can upload logs but it is the exact same issue reported here. The server just repeats the error and does not fully launch.
 
thedeathofsanity said:
Since my update to 2.4 I get the tick error as well and the server will not even launch. I am hoping to see a fix here. I can upload logs but it is the exact same issue reported here. The server just repeats the error and does not fully launch.
Click to expand...
The tick message is just a warning, not an error, and shouldn't cause servers/worlds from working. Sounds like there might be another issue going on.
 
You must log in or register to reply here.
Back
Top