User Details
- User Since
- Jul 7 2024, 12:15 PM (38 w, 2 d)
Sun, Mar 30
I gave 1.27 from experimental a quick try and it seems this issue is solved there already. Thanks for the quick fix!
Wed, Mar 26
@cwagn are you using Linux on your server?
Glad to hear @Corse!
Tue, Mar 25
@Geez fyi: Append is broken for File and FileStream
@Corse I only know the expansion atm mod, that's writing JSON files with a single write, that always worked. All mods that append data were broken, including basic things like log files. They were entry dinner a long time, so I think aliens for simple files was broken since a longer time.
With the workaround in CF in place it's not super critical anymore, at least if you don't have other mods that append data to Filestreams.
You can check your log, stderr should have a line for each modified function call.
Mon, Mar 24
The workaround I've posted in https://feedback.bistudio.com/T190201 also fixes that error for me.
https://github.com/bzed/dayz-append-fix/ - here is a workaround until its fixed properly.
@Geez I don't want to put pressure on you - but currently every linux server is broken due to that. When are you going to fix it?
Sat, Mar 22
Fri, Mar 21
So with the following code
FileHandle handle; for (int i = 0; i < 2; i++) { handle = OpenFile("$profile:testraw.bin", FileMode.APPEND); if (handle) { Print("DEBUG APPEND - TEST"); FPrint(handle, "TEST APPEND"); CloseFile(handle); } else { Print("DEBUG FAILED TO OPEN FOR APPEND"); } }
@Geez More testing (thanks to @lava76 ) shows that append is also broken for a normal FileHandle.
Also a plain vanilla chernarus seems to have issues with persistance (things don't despawn in time and similar things), so my impression is its broken for the server in general. This is a really major issue, please fix it asap!
Thu, Mar 20
+1 from me, just stumbled upon this ticket. I rarely play on official due to cheaters. There are good and well working community servers that take care of the issues.
BE is not really helping, they don't seem to be able to track cheaters properly and I also know about false positives - and there is no way to get this issue solved.
Its far from optimal - and without community servers I would not be playing DayZ anymore.
Wed, Mar 19
I've moved that into https://feedback.bistudio.com/T190201 - the muzzle error is a bug on its own.
I think this might need to go into a bug report on its own, this one is really about a bug in weapon/muzzle handling.
@lava76 I've changed the code to
+ FileSerializer s = new FileSerializer(); + s.Open("$profile:test2.bin", FileMode.WRITE); + s.Write("TEST"); + s.Close() + for (int i = 0; i < 2; i++) + { + s.Open("$profile:test2.bin", FileMode.APPEND); + s.Write("TEST"); + s.Close(); + }
My first observation is: test.bin does not get written at all on s.Close() - its still empty after the server started.
The server crashes on shutdown and the file is gone (!)
After the restart, the file is empty again...
@lava76 indeed that case crashes on linux. I've debugged that in an older version of https://steamcommunity.com/sharedfiles/filedetails/?id=3381664818 and the mod was rewritten to use proper constructors and super calls as you would do it in c++, which fixed the segfault. The original constructor was in the form as mentioned above, rather simple, some variables in the child class, and the access to the base class segfaulted.
In 1.26 and 1.27 I regularly see a segfault when dayz is shutdown with the rcon shutdown command, but it doesn't seem to appear (or at least less...) when I send a TERM signal. Haven't seen a double free on shutdown yet.
Tue, Mar 18
@Geez I can provide memory dumps / rpt files, or if it helps I can keep the linux core file next time so you can load it into gdb
I had just a crash (after updating to the last release today), with the same origin. Not a vanilla server though:
@fraky what you are describing sounds like https://github.com/Arkensor/DayZ-CommunityFramework/issues/183 - which actually points to https://feedback.bistudio.com/T189290. The Muzzle error is - at least in my experience - not related to that.
Fri, Mar 14
Wed, Mar 12
@RPowerSpeed @Geez Indeed, completely support that. Loosing players might not be such an issue for those servers that have a long queue usually - but I have lost 90% of the usual players. Regular crashes, necessary wipes (especially due to CF being also broken, with the fix for it needing a wipe), module creators having to work around bugs in DayZ / the server - thats just super annoying. And a big waste of time for those who run the servers. I would rather create something nice for players instead of having to move players or even delete them because they can't login anymore - or with crashing servers its affecting everybody. There are too many open bugs in the client and the server, and its getting more and more frustrating.
Mon, Mar 10
Hi @Geez!
Its happening on two servers, they only share CF as mod. There is https://github.com/Arkensor/DayZ-CommunityFramework/issues/183 which only seems to happen during restarts, but I can investigate.
Sun, Mar 9
We are seing this regularly on a slightly modded server. Using an admin backpack with 1000 slots crashes sooner or later for sure. Also picking up crates (mmg in this case) seems to trigger it.
Sat, Mar 8
Thu, Mar 6
Sun, Mar 2
Also I came up (actually with the help of chatgpt) with a script (its a hack, yes) that replaces the player's location in players.db. After changing the location the login works as expected.
So I can actually reproduce this:
Mar 1 2025
@Geez @dedmen it might make sense to merge https://feedback.bistudio.com/T182075 and https://feedback.bistudio.com/T93061 into this bug, or at least link them - they are definitely related.
I've also tried OPENSSL_ia32cap=~0x200000200000000 to really make sure its not a mix of hardware / too old openssl - but the issue stays the same.
Mar 01 17:30:59 game002 hashima-server[1326254]: Error decrypting message: error:0406506C:rsa routines:rsa_ossl_private_decrypt:data greater than mod len Mar 01 17:30:59 game002 hashima-server[1326254]: Error decrypting message: error:04099079:rsa routines:RSA_padding_check_PKCS1_OAEP_mgf1:oaep decoding error
Feb 28 2025
I tried Debian 11 in a podman container, that didn't make a difference.
After discussing this in the dayz discord, we are pretty sure that this bug and
https://feedback.bistudio.com/T182075
and
https://feedback.bistudio.com/T93061