In T190201#2778512, @bzed wrote:

@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 always empty before, so I think writes for simple files was broken since a longer time.

In T190201#2778410, @bzed wrote:

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.

In T190201#2778393, @SirAdef wrote:

Server running all night no problems... Next days will show if it really is stable enough.

For now, another point in yeold match Devs vs. Community...

In T190201#2778250, @bzed wrote:

In T190201#2778249, @SirAdef wrote:

In T190201#2778233, @bzed wrote:

https://github.com/bzed/dayz-append-fix/ - here is a workaround until its fixed properly.

Some workaround has been added to CF too

• Added a workaround for player loading under Linux due to DayZ bug T190201 (FileMode.APPEND without function)

Yes, that is a crude hack though and doesn't fix the issue properly - its impossible to do that within a mod.
You'll realize that with my LD_PRELOAD you'll suddenly have logs from various mods that were empty before.

That bug must have been lingering longer, I guess it only affected "normal" file writes before and made a mess as soon as the Filestream used by CF was affected.

Getting this as well with the muzzle errors and the weird crashing, also running Linux (Centos 9)
Changed maps, fresh wiped, played with no mods, and eventually still ran into the error.

Since the update the server has mostly been stable but I am seeing a new behavior. Now instead of the server crashing, some players will log in and then crash to a 0xc0000005 error. When this happens, the server freezes on the number of players and will continue reporting that number, being unresponsive. No crash logs, it just hangs until it's restarted.

In T189290#2770134, @bzed wrote:

@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.

In T189290#2765687, @Geez wrote:

In T189290#2765670, @Firewalker wrote:

Has there been any communication with BI about this issue? I haven't checked back on Expansion Discord, but last I read they were also thinking these are BI issues.

I'm going to try to turn airdrops back on later today with loot disabled and see what happens.

Fire

This particular crash that has appeared after 1.27 is on our end and we are working on a fix

In T189290#2764572, @OGBDayz wrote:

In T189290#2761160, @oldmann1991 wrote:

Same issues for us. Before this senseless update we didnt have crashes or crab like that. Update 1.27 happend, almost crashes on a hourly bases.
WIN-DC5QK4GAL09, 01.03 2025 10:56:06
Unhandled exception

Program: D:\OmegaManager\servers\1\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff68675e1b4 at 0xffffffffffffffff

SymGetSymFromAddr:487, addr:0x7ff68675e1b4
SymGetSymFromAddr:487, addr:0x7ff686821c27
[CDPCreateServer]: ??? addr:0x7ff687106c5e
[CDPCreateServer]: ??? addr:0x7ff687107fef
SymGetSymFromAddr:487, addr:0x7ff686820bfe
[CDPCreateServer]: ??? addr:0x7ff686f4b83d
[CDPCreateServer]: ??? addr:0x7ff686e8fbdb
[CDPCreateServer]: ??? addr:0x7ff686e8f30e
[CDPCreateServer]: ??? addr:0x7ff686fee8c6
[CDPCreateServer]: ??? addr:0x7ff686fe5a74
[CDPCreateServer]: ??? addr:0x7ff686fe7f79
SymGetSymFromAddr:487, addr:0x7ff686a2a5fd
[CDPCreateServer]: ??? addr:0x7ff686fefb86
SymGetSymFromAddr:487, addr:0x7ff686b4e1d0
[CDPCreateServer]: ??? addr:0x7ff687149332
[BaseThreadInitThunk]: ??? addr:0x7ffce61c4cb0
[RtlUserThreadStart]: ??? addr:0x7ffce6a5edcb
[RtlUserThreadStart]: ??? addr:0x7ffce6a5edcb

DayZServer_x64_2025-03-01_10-21-39.RPT3 MBDownload

DayZServer_x64_2025-03-01_10-56-06.mdmp1 MBDownload

did you get any response or update to this? I posted in a different thread because my error code was slightly different the original posted here, got dragged into a whole different thread where there appear to be totally different crashes than mine. Yours appears the same and possibly even the same code, i'll have to verify by logs, but I can literally put a 60 minute timer on it from server start and send a message right before crash, or restart the server. it's pitiful and i have found NO useful info

Ok doing some troubleshooting on my servers I have been able to replicate the weird behavior.

I started having issues as well after the 1.27 update. My symptoms are the access violation. As well, when this happens, players report no longer being able to join without crashing to the access violation error. What is interesting is I removed all mods from my server one by one to see if any one specific mod caused the issue, down to the point that it was just the Deer Isle map. It did not restore my ability to log back in. However, if I wipe the playerdb file and let players rejoin, it seems to behave fine for a short period of time. Upon slowly reintroducing mods, it seems to inevitably happen again. I would have anticipated the playerdb file updating as mods are removed and items are no longer in inventory but it's almost acting as if the playerdb is becoming corrupt. Most players state it works for a while and inevitably freezes and happens again. This happens to me on linux or on windows servers, as I am able to take the known broken playerdb, move it to my other server, and reproduce the issue, even with different mods.