I thought i was the only one having this issue.
Everytime i start my headless client, even if he does nothing, when we reach more than 100 players, after few minutes everyone gets kicked.
That's why i stopped using HC.

any comment from BI on this. seem as normal you guys hide under rocks ?

We are experiencing this at around 100+ players, some times it is fine but other times BE randomly starts kicking at around 105~ players...

My server has mass kicks very frequently, so tonight I tried running it without any BE filters. We lasted 4 hrs 15 mins with 70+ players and no issues, then I turned the filters on and within 40 minutes a mass kick occurred.

I'll do more tests tomorrow removing individual filters to see if its a specific type of filter causing my problems and then post my results here.

We completed testing with no filters, I don't think they are the issue

Do you have any messages in the log before kicks?

Nothing logged other than the log of the kick

@Wilco Asylum is keeping an eye on this. Seems based on our internal experiments that a hard restart alleviates the issue, but if left unchecked the server will continue to kick every time it fills back up (every 15 mins or so) until it naturally hard restarts.

This can either mean a single instance if an Admin is on a server when it kicks and hard restarts it, or dozens of times in a few hours if nobody is around and monitoring the servers.

We suspect it has something to do with server memory, and the amount of data being held in memory by Arma for variables, but haven't been able to actually validate that in any substantial way.

Our life servers are suffering from this as well. Some servers suffer from it more than others even though they all run the same mission. We tried disabling BE filters but we still suffered mass kicks regularly. This is a very serious issues since when mass kicks happen players lose progress and money in game.

Please fix this Bohemia thank you.

Gaming Asylum has extensive logging inside of Splunk of data around the times this issue occurs. I'm happy to provide data to BIS as necessary.

This is one of the largest issues facing the modding community though, and I'm sure anyone with a large server would be more than happy to assist you in tracking this down.

After a few more days of tests I'd like to clear up my last message.
I do still get mass kicks without battleye filters, they are just not as frequent.
As you guys have said its clearly not the cause of the problem, just me shooting myself in the foot with the amount of filters I had.

This issue is hugely affecting our Arma 3 community and servers. Would love to hear Bohemia's answer on this.

Can you guys give us a hand here? @Alwin @razazel @Jawsh

Bohemia pls

Bohemia have commented on this via twitter saying they are still investigating the issue

As mentioned on the Twitter we are looking into the issue together with BE developers, searching for a suitable solution. Unfortunately that is the only info I have for now, I'll try to keep this updated with the progress (once I know something).

We get this issue on a rarer occasion than Wilco above, that said, it's the exact same errors and the same actions taken.

I personally believe it has nothing to do with Battleye too, we see it even more whilst using our headless client, fortunately, we're rewriting its system so get the kick less, however it all points to network activity as shown in the logs above.

I implore @razazel and @Dwarden to take the offers from communities such as Asylum, and get tests done you can't do in-house. We offer our services too!

To echo what has been said today, please let me know what sort of reporting you need from us to help you track down this issue. We keeps logs of virtually everything, and have them going back for several years. I am personally happy to help getting this tracked down as it has plagued our community going back to May of last year.

@Wilco let me dig through the logs a touch. Looks like it actually began before May. It's been so long since I pinpointed the start date - and I had May in my head for some reason.

Things like this REALLY need to be posted by BIS in the tracker, otherwise, what's the point of it?

Not the first time we get answers through twitter.

*crickets*

Soon™

maybe one day

@Dwarden hey cucklord, any response?

https://dev.arma3.com/post/sitrep-00204

We also have some more information regarding a BattlEye mass-kicking, which happened to some communities over these past few months. It seems we finally found a potential solution to this problem with our senior programming staff working on it as we speak. However, it might still take us some time, because the changes require low-level and potentially risky netcode changes. For this reason the implementation and testing needs to be handled with extreme care. It means we don't have a specific date yet, but we hope to release the change in one of the upcoming Main Branch updates. Please bear with us!

As happy as I am to finally have had something said about it, it took them far too long to even comment on it. Running a server is stressful as it is, chasing the producer of the game certainly doesn't help this.

This really should have been something that was 'being worked on' the day it started happening

unban tyrone

I assume that this is due to poor configuration of basic.cfg.
https://community.bistudio.com/wiki/basic.cfg
Also look at the research on the forum.
Also try to disable BattlEye. I'm sure the problem will remain

Unfortunately not.

See my quote from the SITREP above.

We faced the same problem. But the correct setting of basic.cfg helped. I do not know why, but I also had off battleye. It seems that because of the dll.

Hey guys, have you by any chance tried the latest RC build? The potencial fix mentioned in the SITREP is already there so, it might be worth a shot giving it a try and reporting back in case something is still broken :)

Still getting the issue:

20:06:33 BEServer: registering a new player #1577864936
20:06:37 NetServer: cannot find channel #1577864936, users.card=46
20:07:06 Server: Network message 115523 is pending
20:07:06 Server: Network message 115523 is pending
20:07:07 NetServer: cannot find channel #516779254, users.card=46

The latest update does not appear to have fixed the BE mass kick issue for Asylum. In the last 72 hours we have had approximately 13 such mass kicks with the same messaging as before the 1.78 patch.

Some servers seem to have "found their own fix" you'll have seen them posting here prior but no longer mentioning it (rpuk)

hope you don't mind Bamf, i'm quoting you on our forums as people are saying its "just us"

Actually managed to get a wireshark capture as it crashed, was doing it for my ISP to see if there was anything their end... @Dwarden I can provide if needed.

In T124802#1657269, @Neology wrote:

Some servers seem to have "found their own fix" you'll have seen them posting here prior but no longer mentioning it (rpuk)

hope you don't mind Bamf, i'm quoting you on our forums as people are saying its "just us"

Zero-One still have them too.
https://i.gyazo.com/f9c9845ae0e7fea211052b5a2f7a4a1a.png

Thats 5 communities that is suffering with this some have been suffering for over 12 months, can we get some sort of acknowledgement that this issue still exists, you contact bohemia to report it and they say post here, when you do nobody ever responds....

@Neology Haha, feel free. I largely just stopped answering our community and began directing them to this ticket.

RoleplayUK and Grand Theft Altis both have this issue solved. There are many servers out there that are having this issue, Even Bohemia have been looking into it, would be nice if they threw a lifeline. The downside is, these servers are gaining popularity as they haven't got the kicks anymore, why would they want competition?

Seeing as they dont do it themselves:

[7:17 PM] Dwarden: good news about the BE troubles ... and bad news about the BE troubles ...
[7:17 PM] Dwarden: will know more after next DEV branch tomorrow 😁
[7:18 PM] Dwarden: fixed some if not all of it ... lot of brave programmers fallen on the battlefield today

Posted 05/12/2017 (dd/mm/yyyy)

So, GTA never had the issue, they re-coded their mission so much, they cant pinpoint what fixed it because they never had it.

All the Destination unreachables are port 2306
This was captured with Firewall OFFLINE.

An example of log before everyone is kicked:

19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:27 Server: Network message 5789380 is pending
19:58:28 Server: Network message 57896cf is pending
19:58:28 Server: Network message 57896cf is pending
19:58:28 Server: Network message 5789d5e is pending
19:58:28 Server: Network message 578a84d is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:30 Server: Network message 578e1cd is pending
19:58:32 NetServer: cannot find channel #1373936035, users.card=72
19:58:32 Message not sent - error 0, message ID = ffffffff, to 1373936035 (ツ| Flames  )
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 57909d3 is pending
19:58:32 Server: Network message 5790d50 is pending
19:58:32 Server: Network message 5790d50 is pending
19:58:32 Server: Network message 5790d52 is pending
19:58:32 Server: Network message 5790d52 is pending
19:58:32 Server: Network message 5791043 is pending
19:58:33 Server: Network message 57923c3 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending
19:58:33 Server: Network message 57923c4 is pending

having the exact same problem. anyone know a fix?

The main issue that caused this was corrected by bohemia months ago... any further issues are usually related to a bad basic.cfg

You need to send more detail on;

• how many players were online at the time?
• What type of mission are you running?
• who's the server host? (e.g hetzner, ovh, etc)
• server's connection.

and anything else you feel is relevant.

In T124802#1611747, @reekoj wrote:

I thought i was the only one having this issue.
Everytime i start my headless client, even if he does nothing, when we reach more than 100 players, after few minutes everyone gets kicked.
That's why i stopped using HC.

3 years later, still the same problem with a different mission.
And still a lot of "Network message 57923c3 is pending" in the logs.
With 100+ players , on a dedicated OVH server
I tried different parameters in basic.cfg but it doesn't seem to make any difference

What type of mission are you running?

We run a Exile server and have the same problem and i can't find any possible reason for this problem.

We had this problem on 3 different hosters now and all 3 servers had a Gigabit connection. It started happening in April this year before we had no problems.
It starts happening with 45+ players and after arround 2 hours mission runtime.

Hoster: OVH

Current hardware:
-AMD Ryzen 7 3800X - 8c/ 16t - 3.9 GHz/ 4.5 GHz
-64 GB DDR4 ECC 2666 MHz
-2x960 GB SSD NVMe Soft RAID

Most mass kicks now relate to a bad basic.cfg setup.

https://community.bistudio.com/wiki/basic.cfg

Hi, is this ticket still relevant or can it be closed?

Closed as far as we're aware, @Biground