Hello,
Last couple of weeks I have been having issues with trying to load a large modpacks.
I've used the PBO filler mod from a previous pbo issue to test it, but also used workshop mods.
Issue seems when enabling Battleye it block's the ability for a player to join a server.
When disabling Battleye and using the exact same mods players can join fine.
This does happen however when a number of PBO's have been met.
Set up a machine with Debian (possibly also happens with other distributions). I used Debian 9 (4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64) for my own local testing,
While I also got a dedicated server running Debian 7 (3.2.0-4-amd64 #1 SMP Debian 3.2.96-2 x86_64) where the same happens.
Run some mods (filler mod found here) 1000 should do the job.
Make sure Battleye is running in server.cfg
BattlEye = 1; battleyeLicense=1; // Possibly not needed
Start server running the mod(s) and using the config.
And join server and see that you will get stuck on a never ending loading screen trying to get into the lobby/mission select screen.
Now disable Battleye,
BattlEye = 0; battleyeLicense=0; // Possibly not needed
Start server again same mods and edited settings.
Join server and now you will/should be able to join.
Few logs files (rtp) of some runs on Debian 9 Local VM Server.
Few logs on Debian 7 Dedicated server (using actual Workshop content)
Hello there! We do experience that problem on the 1.84, ubuntu 18
file limits are set:
'/etc/security/limits.conf'
hard nofile 500000
root hard nofile 500000
root soft nofile 500000
same issue on Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-33-generic x86_64).
is not a open files limit problem - i have set all parameters correctly:
/etc/sysctl.conf:
fs.file-max = 2097152
/etc/security/limits.conf:
'* hard nofile 500000'
'* soft nofile 500000'
/etc/systemd/system.conf:
DefaultLimitNOFILE=500000
arma3server@linux:~$ cat /etc/pam.d/common-session|grep limits
session required pam_limits.so
arma3server@linux:~$ ulimit -a
core file size (blocks, -c) 100000
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 128564
max locked memory (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files (-n) 500000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 128564
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Arma3 Server Log:
...
10:00:07 BEServer: cannot find channel #1084005264, users.card=0
10:00:07 BattlEye Server: Connected to BE Master
10:05:10 BEServer::finishDestroyPlayer(1084005264): users.get failed
RE: "Thank you for the report. We will see what can be done.":
the solution is very simple: modify FD SETSIZE to 65535 in "beserver.so".
do you always react so slowly to the critical errors?
Could you please run under strace with and without BE?
e.g.
strace -f -o armaserver.w_be -s 999 -t ./arma3server <blah-blah>
strace -f -o armaserver.wo_be -s 999 -t ./arma3server <blah-blah>
log onto lobby, ensure you've got "users.get failed" with BE, kill server and share both files?
Well, i've managed to reproduce issue with ~610-620 PBOs
and it's definitely not related to limits -
https://paste2.org/HYwPJw63
it seems like it dies when client fd gets onto range > 1024
https://paste2.org/f0YsMDUV
In attached trace file problem can be found somewhere around 7:02:29
@tsipa740, thank you for reproducing this error.
we have the same result.
we have determined the following limit for the amount of your own PBO files: 640 - 643 PBO
we wait until the BIS development accepts and solves the problem.