sv_protect 1 stops clients from connecting to the server after several days of uptime #541
Labels
🐞 Bug
Something isn't working
cat: server
Category engine (server)
❓ Feedback
Further information is requested
P3: Normal
Priority 3
Milestone
Comments
ETLegacyTeam
added
🐞 Bug
|
From: @IR4T4 (IR4T4) That bug doesn't surprise me. See comment of linux Sys_Milliseconds() and usage of this function in SVC_RateLimit. note: see if sv_protect 2 (OpenWolf style server protection) is also affected |
|
From: @JanSimek (Radegast) sv_protect 2 works so far, but so does sv_protect 1 for several days (weeks) before it breaks. Just to be safe I'll set sv_protect to default to 0 before tagging 2.70rc4 |
|
From: @jackeri (Jacker) This should now be fixed, please test. |
This was referenced Mar 5, 2020
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Author: @JanSimek (Radegast)
Date: 2014-05-24
Redmine Issue: 541, https://dev.etlegacy.com/issues/541
Any client trying to connect to the server will be dropped:
Setting @sv_protect@ to 0 lets clients connect again.
This happens on our test server which is running 2.71rc3.
Related commit(s):
c5aa721 - misc: sv_protect default values - refs 541
4da5a39 - server: possibly fixed sv_protect 1 and added chan..
8120de3 - server: Never set lastTime=0 for leaky buckets as..
The text was updated successfully, but these errors were encountered: