the same 1.25 TB project:

I was able to brute force a build by ignoring all errors in mikero. It's ok for my local build but it's logs are pretty grim reading

hi, I'm experiencing a problem with packing my /world folder too.

In T165620#2544483, @KaMiKaZe6426 wrote:

In T165620#2533079, @DanielCeregatti wrote:

Tracing the openat() system call using strace during the execution of the server shows that the cfggameplay.json file isn't opened at all:

strace -o /tmp/dayz.log -e openat -f ./DayZServer -config=/profiles/serverDZ.cfg -port=2302 -freezecheck -BEpath=/profiles/battleye -profiles=/profiles -nologs

Let the server start up. Then:

grep json /tmp/dayz.log

The only json file that's opened is a different one:

1353 openat(AT_FDCWD, "/serverfiles/mpmissions/dayzOffline.chernarusplus/cfgundergroundtriggers.json", O_RDONLY) = 164

This was actually a very helpful tip, thank you very much, because of this I was able to get it to work again on my server.

If run the strace for the stat systemcall instead of the openat one, you will find that stat for the file cfgGameplay.json is being done during startup:

...
20457 stat("/dayz_server_root_directory/mpmissions/dayzOffline.chernarusplus/cfgGameplay.json", {st_mode=S_IFREG|0755, st_size=2594, ...}) = 0
...

(this line may look a bit different for you, i only took this trace after finding and fixing my issue)

So it seems the reason that the file is not being opened is the spelling of its name (note the capital G in the syscall that is neither in the documentation nor in the directory tree you download: cfggameplay.json vs cfgGameplay.json).
For me, renaming this file to include the capital G in its filename has actually solved the issue, so here's to hoping that this is the case for you as well.

I suspect that this stems from development on windows (given the apparent focus on windows releases, i suspect that DayZ is developed on windows), as windows does not care about capitalization of filenames at all while linux very much does (i.e on windows 'cfggameplay.json' and 'cfgGameplay.json' are actually the same file, while on linux they're two different files).

In any case, good luck to you all having this issue, and I hope that my comment here can help others as well.