Weekly Stuck on "BOOM' For 3 Weeks

[fwfdf1reman]

As title says, we are perplexed to get this one figured out. We have one of our 8 KF2 servers set permanently to "Weekly" and it has been stuck on "BOOM" for 3 weeks now, and does not change to a new scenario after the week is up.

Any ideas on what the issue might be?

 

[®omano]

You need to restart server to update new weekly challenge.

 

[fwfdf1reman]

Lemme check that. Thx Romano

I checked, it was set to restart at 3a.m. every morning. Set a couple more restart times to see if it straightens up.

 

[®omano]

I don't know why it is like that but server needs the weekly restart. Are you saying it restarts already every morning at 3am? I'm confused.

 

[fwfdf1reman]

Yes, every morning there is a restart. There was only one, at 3 a.m., but I have added another during the day to see if it clears this up.

 

[®omano]

So I don't think that will solve the problem.

Do you have the NTP port opened/available (port 123)? http://wiki.tripwireinteractive.com/index.php?title=Dedicated_Server_(Killing_Floor_2)#Ports

 

[fwfdf1reman]

I am assuming it is opened. We run a Dedicated server through NFO. By default, port 123 UDP is suppose to be open.

Our Weekly server worked flawlessly up until a couple of months ago, then we started running in to this issue.

 

[®omano]

If you have no control over firewall/router/ports config, then I suggest to reach out your client support to ask them about this exact issue, tell them that your server needs this port to be available in order to have the weekly game mode working. If it suddenly stopped working without you doing anything (and I don't see what you could have done honestly), then It may be a problem on their side regarding the communication on this port not being able to work (the server needs to check the external time server to check which weekly it must run so I suppose this is most likely the problem).


edit: wait I read again, you have a dedicated server so you should have full control then. Maybe share a log to see if we can see something weird in it (remove any sensitive info of course like passwords in command line)

 

[®omano]

I started my server on Weekly game mode, here is interesting part I see:

[0012.87] Log: Initializing Game Engine...
[0012.90] Log: *** Updating timed game events
[0012.90] Log: **** Current Time: 2018 4 12 23 49 9
[0012.90] Log: **** World start in seconds: 1492466400
[0012.90] Log: **** Current time in seconds: 1523569749
[0012.90] Log: **** Intended weekly index: 51

 

[fwfdf1reman]

Will do some more checking Ramano. Thx for all the info. Going to wait a week or two and see if it straightens out. After setting new restart times, the server is now on "Bobblehead" for the weekly. Let me see if it changes for the next weekly. If not, then I will probably submit a ticket to discuss this issue with NFO. Again,thx for your time and expertise.

 

[®omano]

Bobble Zed is the current Weekly so it seems to be OK.

edit: maybe your planned restarts were not occurring and now they do? You can check that by looking in the log folder, should be one log per day if it properly restarted, with the Launch-Backup-xxxxx logs having the date of when the new Launch.log was created.

 

[fwfdf1reman]

I did check that and restarts only appear in the log from the 11th on. I am thinking, that perhaps after the Spring update, restart times got re-set? I had all of our instances of KF2 set to restart every morning. Like I said, will keep an eye on it for the next couple of weeks and see if the issue is fixed.

 

[fwfdf1reman]

OK, verified with other friends and here is the issue. Even though the Weekly Event Title changes, if you join and play, you actually play "Boom". So it appears the Title for the Weekly Event changes every weeki, but the gameplay remains BOOM!

 

[®omano]

Any chance you share a log or something?

 

[fwfdf1reman]

Yeah...

 

[®omano]

Immediately seeing a problem:

[0010.14] Log: *** Updating timed game events
[0010.14] Log: **** Current Time: 1900 1 1 0 0 0
[0010.14] Log: **** World start in seconds: 1492491600
[0010.14] Log: **** Current time in seconds: -1
[0010.14] Log: **** Intended weekly index: -2467

Big problem with the remote time request apparently and so the Weekly challenge index is erroneous (-2467 here when it currently should be 51).

I still think you have a problem with the time request, the NTP service. I don't know how you could find why it breaks.

 

[fwfdf1reman]

After reading your post, I changed that server back to "Survival" game mode and restarted it. Once it was up and running and verified, I changed it back to Weekly. Checked the log file and still has THOSE numbers for the time stamp. I currently have a support ticket in to NFO to have them run a Repair Script on that server. Will check afterwards.

 

[fwfdf1reman]

Repair script did not fix the issue. I am at a loss.

 

[®omano]

Foster Parent could you check if there are other similar reports of the issue with weekly servers not able to get the remote date/time and have unproper weekly challenge on server start please?

 

[fwfdf1reman]

Tom. morning I will remove all Steam Workshop Maps from that server and run only stock maps to see if that clears it up. No mutators running on the server, just some custom maps. If that does not fix the issue, then will probably configure it as a our third "Endless" server as those seem to be very popular right now.