Allow server to have at least a couple of seconds grace period before applying whitelist.txt
It seems the server is checking that file all the time, and when it is saved the server checks it even at the moment when the contents are replaced and thus inaccessible.
Let the server detect the changes, but give it a 5 seconds timeout before applying. So after 2-5 seconds, the correct whitelist.txt is here and accessible.
Description
Description
Details
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Server
Steps To Reproduce
- Run server
- Connect to server
- Open whitelist.txt in the editor, change, save
- All players kicked with the error "you are not in whitelist"
Event Timeline
Comment Actions
Hello zvukoper.
Did this issue appear with the 1.13 release or is this issue related to the 1.12 version as well?
Regards,
Geez
Comment Actions
This still happens on stable 1.16. I am using a Playstation server on nitrado and provided detailed reports at https://forum.nitrado.net/thread/19762-whitelisted-players-kicked-out-of-server-with-not-whitelisted-error-when-game-se/
It seems whitelist.txt is at time read when the file is "locked", thus it reads an empty file (or fails to read). DayZ server detects it, and repeats the loading of the whitelist.txt right after.
However, this is enough to kick out all players.
This is an example of the RPT log entrie:
19:36:46.757 Reloading Userlist ban.txt
19:36:46.757 Reloading Userlist whitelist.txt
19:36:46.757 Player <hidden1> (<hidden1>) kicked from server: 12 (You are not whitelisted on this server.)
19:36:46.757 Player <hidden2> (<hidden2>) kicked from server: 12 (You are not whitelisted on this server.)
19:36:46.757 [Disconnect]: Client <hidden1> early disconnect
19:36:46.757 [Disconnect]: Client <hidden2> early disconnect
19:36:46.773 Reloading Userlist whitelist.txt
19:36:46.773 [Disconnect]: Start script disconnect <hidden1> (dbCharacterId 1 dbPlayerId 1) logoutTime 5
19:36:46.773 [Disconnect]: Start script disconnect <hidden2> (dbCharacterId 31 dbPlayerId 31) logoutTime 5
Comment Actions
Thank you for your reports.
We will take a look at what can be done to prevent these kicks.
Regards,
Geez
Comment Actions
After 1.18 I tried editing whitelist on live server. It did not kick me. And removing myself from whitelist has no effect too.
Fixed: Banlist, whitelist and prioritylist were cleared when the accompanied file was failed to be opened by the game
It looks like the same issue. Can you confirm it is fixed and related?