Hi, I´ve been reading some threads in the forum about this error. There is no solution already? It causes heavy lag spikes on players.
This error happens a lot while players are farming with hatchets and pickaxes.
If anyone have some ideas to solve it or avoid those lag spikes it would be nice...
Thanks!
Sent invalid attack error spam
Discussion in 'Rust Discussion' started by DavomutCZ, Jun 19, 2016.
-
I don't think thinks that these errors causing the lag spikes, but your server is lagging and that's why it's showing you the error.
-
That´s all I know, I´ve been testing it with players and when they go farm that happens and show the error. It never lags instead of this spikes.
-
Do you have Oxide installed?
What plugins do you use?
Where is your server hosted/server spec? -
Xeon processors are no good at running the server. You need a gen 5 or gen 6 Core i7.
-
-
My server runs fine on a xeon with 25-40 players daily and 500 slots with 80 plugins.
-
I know there have been other threads on this , but they are old and the solution they give only sort-of works
I keep having this error
Gyazo - b37e9bdc7f091c6c59d8f904dd845df7.png
even after doing "antiHack.projectile_protection 0" in console
Does anyone know how i could fix this please , it seems to be the cause of bad lag on my server. Thanks
note : i do have 136k entities on the map , but i dont think this is a problem ? -
Anyone else having this issue? I'm not sure if its just when my players use the rock or if other items cause this error. It has been causing some lag on the server. Please let me know if anyone has a fix for this or if this is a facepunch issue. Thank you
Here is the error,
sent invalid attack: Initiator too far away (rock.entity on pinetall-1 with 23.87737m > 3.28125m in 0.2375s)
[DOUBLEPOST=1483735191][/DOUBLEPOST]I confirmed it is happening with multiple items.
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.3341675s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1358643s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.33078s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.1302185s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.09725952s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.07092285s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.07092285s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.07092285s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.07092285s left on rock.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.4671936s left on torch.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.4671936s left on torch.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.4671936s left on torch.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.4671936s left on torch.entity)
Sunnybear[24519/76561198346357826] sent invalid attack: Cooldown (0.4399719s left on torch.entity -
I too am getting this and it's ruining the fun on my server. Is there a fix to this yet? This is actually game breaking!
-
-
My friends and I are testing it. It is in fact what i said. I have two of them battle with guns and it is spamming the console and causing rubber band lag badly when they are fighting. When no one is fighting, it runs smooth. I did in fact disable the anihack and did server.secure 0
But it is still happening. This is a serious issue. -
-
Hey Guys,
I am getting the same Errors and Lags ingame, but this is not a problem caused by the server.
You need to pay attention to your server specs especially on your CPU.
I used Linux first and i thought its a problem with linux rust, that i have so high CPU Load in general.
Then i switched to Windows and found out, that the Server is only managed by one Core :
Screenshot
This explains the server lags and you really need to check, that you get 3GHZ+ E5 or an i7 from the new Generations.
I heard that Rust ist Monothreaded, but i didnt understand this until now
[DOUBLEPOST=1483789831][/DOUBLEPOST]This may be Off Topic, but got anyone experience with the Games Minecraft/Arma 3 on these low clock CPU´s ? Is it Arma 3 and MC also "Mono-threaded" ? -
I am trying to help somebody with the same errors.
His server is vanilla (no plugins, no mods) and has about 60 people on it from various nations. I ran around and experienced only one little lag, which did not matter to me.
Sometimes, after an error wave/lag, about 20 of the people get kicked. He is using a server with an i7 and 32GB of ram...
I do not have that problem on my servers (I have three running on an AMD FX-8150 with 16GB of ram), on the other hand, I did not have over 20 players yet.
Any proper and secure solutions for a high-pop-server? -
Hey,
We just changed our server and we moved to MyLoc, with a 3,6 GHz CPU 64 GB Ram and SSD.
We dont have the Problems anymore which i told you above in my thread.
But our players are having hard ingame laggs :
Screenshot
While we experience these type of laggs, Cpu is on 10% / Ram 6/64 GB and the network connection is also ok.
These only occures when our servers have over 200-300 players in general. The laggs Spikes are 30-60 Seconds and then they end, so we thought about ddos, but our network interface shows no high incoming traffic?
We are hosting several server entities on the same root and if these laggs happen, also the other servers are lagging and the same errors show up.
Maybe we should move to another Provider ?
Or maybe you guys could help me out.
Thx -
A) Check the CPU-load exactly while that errorspam occurs.
B) Check the ping of the players in the error-messages - especially while they trigger errorspam.
I have no clue what the problem (let alone the solution) could be, I checked various things. -
Hey,
We recently checked all the things you mentioned in your post.
Here are t hese stats, when we experience the problems :
Our CPU-load is on 20 % , each core has the same load and there are no peeks at all.
We use Rusty to kick all the players with a ping higher than 200ms, so there is are no players with high ping in general.
The Network Traffic is 20Mbit incoming and 30-40 Mbit outgoing.
Every Player got a ping from 10-50 , some people over 80.
Maybe you could help us -
same error i have
how can i solve it?