Hello, hopefully someone can shed some light on my issue:
Server runs normally and then suddenly kicks everyone. There are no errors in the logs, not even an indication that people have disconnected.
That's basically it. 30 people get disconnected and when they try to reconnect, they get Steam Auth Timeout.Code:xxx[xxx] has entered the game xxx[xxx] was suicide by Suicide xxx[xxx] has entered the game [Manifest] URI IS "https://api.facepunch.com/api/public/manifest/?public_key=xxx" xxx:1077/xxx/xxx Rejecting connection - Steam Auth Timeout xxx:1077/xxx/xxx kicked: Steam Auth Timeout xxx:5972/xxx/xxx Rejecting connection - Steam Auth Timeout xxx:5972/xxx/xxx kicked: Steam Auth Timeout xxx:63457/xxx/xxx Rejecting connection - Steam Auth Timeout xxx:63457/xxx/xxx kicked: Steam Auth Timeout xxx8:25496/xxx/xxx Rejecting connection - Steam Auth Timeout xxx:25496/xxx/xxx kicked: Steam Auth Timeout
According to witnessess, the intial kick message is "timed out".
I'm running the latest Oxide with three plugins: "Logger, CombatLogger and Whisper". Oxide logs are practically empty.
What are the possible causes for this? I'm running a dedicated linux server with 1gbit fibre. CPU (25%) and RAM (about 5 GB) usage remains normal during the ordeal. +240 FPS.
I've been thinking it might have something to do with network, is there a good way to monitor this?
Connection to the server works seemingly normally during the issue.
Server kicks everyone without crashing
Discussion in 'Rust Discussion' started by Evret, Jul 26, 2018.
-
client issue
-
-
-
I have looked at other local servers during the issue and they seem unaffected, so it isn't a global steam problem. -
There have been bugs in the past server side that have caused this but im quite sure they have been patched. Does this happen regularly or was it just the one off? Steam recently released a large patch maybe that could have been the cause. Otherwise get players to check if they can connect to other servers and if they can reconnect straight away when this happens.
-
One person reported that he could connect to other servers during the issue.
Another thing that I forgot to mention that is probably significant: Restarting the server program fixes the issue instantly and after that players can connect normally.
I have done a manual restart two times to fix the issue. I wasn't there to witness the third and fourth occurrences, but it apparently fixed itself within two hours. I have looked around battlemetrics to see if other local servers have the issue during the same timeframe - they don't. -
so your seed is 1 what is the map size
-
-
-
-
-
-
in case you want to see it first -
Ive had it last week aswell, Whas a one time thing, Restarted server and never happend again, Its wierd