82ndAB_Bravo17 Posted June 24, 2016 Report Share Posted June 24, 2016 We have noticed that when we get very bad server lag that requires a restart we often find a line like this in the rpt file: 22:58:00 Warning: 200002 ms spent in callExtension calling name: "epochserver", function: "820||EpochMod.com Autoban" (The GUID really was blank, probably because the banned 'player' was an AI) The cause for this one seems to have been : 2016-06-22 22:54:40 Farid Tanwir (): EH: InventoryOpened 2 and 23:01:23 Warning: 200001 ms spent in callExtension calling name: "epochserver", function: "820|xxxxxxxxxxxxxxxxxxxxx|EpochMod.com Autoban" (GUID masked) The cause for this one seems to have been: 2016-06-22 22:58:03 xxxxxxxx ( xxxxxxxxxxxxxxxxxxxxx ): EH: InventoryOpened 3 or 2016-06-22 23:01:23 xxxxxxx ( xxxxxxxxxxxxxxxxxxxxx ): EH: InventoryOpened 4 (Both names and GUIDs were the same, and this player was not hacking, it seemed to happen when he was revived?) Interesttingly the Autoban that was triggered at 22:58:03 didn't seem to give the Warning about the time spent in the callExtension. At one point we were able to reliably reproduce the issue with the autoban and it did seem that it was the Autoban call to callExtension that triggered the lag, rather than the lag causing the delay in callExtension. We removed the cause of the autoban (150 crypto being deducted for running over an AI in A3EAI) and the issue went away, But it re-emerged a couple of days ago with the InventoryOpened reason. So I guess that this is really 2 bug reports, one for the callExtension causing the lag, which is serious, and the second for the InventoryOpened seeming to cause the Autoban in the first place, which is less serious, but annoying for the person banned. Link to comment Share on other sites More sharing options...
vbawol Posted June 25, 2016 Report Share Posted June 25, 2016 I have changed the hive call used for banning in 0.3.9 to another method we have that uses the BE protocol that should be more reliable. https://github.com/EpochModTeam/Epoch/blob/experimental/Sources/epoch_server/init/server_securityfunctions.sqf#L596-L639https://github.com/EpochModTeam/Epoch/blob/experimental/Sources/epoch_server/compile/epoch_server/EPOCH_serverCommand.sqf About the InventoryOpened autoban. Are you using your own custom InventoryOpened addEventHandler? if not it is likely a false positive as you said. I will try and reproduce it. Link to comment Share on other sites More sharing options...
82ndAB_Bravo17 Posted June 25, 2016 Author Report Share Posted June 25, 2016 As far as I know we don't have a custom InventoryOpened handler - it would only be if it is in one of the addons that we use - SEM 0.8.3, A3EAI and Blackeagles Missions. If we did have one I would expect to get more errors than just those 3, and we don't seem to be doing so. vbawol 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now