Same problem on my server. I am attaching the files. I'm desperate.

Unknown, 10.03 2025 07:53:16

Weapon.OnStoreLoad M16A2_Base<8bc90900> trying to set muzzle index 5 while it only has 1 muzzles!
Class: 'M16A2_Base'
Entity id:3002562

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weapon_base.c:503

Runtime mode
CLI params: ip 192.168.0.200 port 2305 config /home/dayz/serverfiles/cfg/dayzserver.server.cfg mod @CF;@Dabs Framework;@DayZ-Expansion-Bundle;@DayZ-Expansion-Licensed;@VPPAdminTools;@AmmunitionExpansion;@Early Winter or late Fall in Chernarus;@DBN_FordRaptor_Scorpio;@TerjeCore;@TerjeMedicine;@TerjeSkills;@TerjeCompatibilityVPP;@InediaInfectedAI;@RaG_BaseBuilding;@Namalsk Survival;@SkyZ - Skybox Overhaul;@Jiggles Signs;@Forward Operator Gear;@Snafu Weapons servermod @GoreZ bepath /home/dayz/serverfiles/battleye limitFPS 60 doLogs adminLog cpuCount 4 netLog freezeCheck

Weapon.OnStoreLoad AKS74U<684ceb00> trying to set muzzle index 5 while it only has 1 muzzles!
Class: 'AKS74U'
Entity id:3002576

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weapon_base.c:503

Runtime mode
CLI params: ip 192.168.0.200 port 2305 config /home/dayz/serverfiles/cfg/dayzserver.server.cfg mod @CF;@Dabs Framework;@DayZ-Expansion-Bundle;@DayZ-Expansion-Licensed;@VPPAdminTools;@AmmunitionExpansion;@Early Winter or late Fall in Chernarus;@DBN_FordRaptor_Scorpio;@TerjeCore;@TerjeMedicine;@TerjeSkills;@TerjeCompatibilityVPP;@InediaInfectedAI;@RaG_BaseBuilding;@Namalsk Survival;@SkyZ - Skybox Overhaul;@Jiggles Signs;@Forward Operator Gear;@Snafu Weapons servermod @GoreZ bepath /home/dayz/serverfiles/battleye limitFPS 60 doLogs adminLog cpuCount 4 netLog freezeCheck

I looked at other logs and there's more. Both for vanilla weapons and modded weapons.

crash_2025-03-06_18-00-30.log:Weapon.OnStoreLoad CZ75_Base<5e7add40> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-06_18-45-20.log:Weapon.OnStoreLoad BO_TAR21<723e5350> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-06_18-45-20.log:Weapon.OnStoreLoad BO_M82A1_Base<60a2b8c0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_06-00-30.log:Weapon.OnStoreLoad BO_Delta5_Camo8<89243f50> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_06-00-30.log:Weapon.OnStoreLoad MakarovIJ70_Base<72e64500> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_06-00-30.log:Weapon.OnStoreLoad BO_AA12<6986f530> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_19-04-26.log:Weapon.OnStoreLoad Repeater<81490510> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_19-10-20.log:Weapon.OnStoreLoad Repeater<76f5be20> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_19-40-20.log:Weapon.OnStoreLoad MakarovIJ70_Base<69a01120> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_19-40-20.log:Weapon.OnStoreLoad Izh18_Base<7dd98cb0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_19-40-20.log:Weapon.OnStoreLoad AKS74U<9342e960> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_21-03-36.log:Weapon.OnStoreLoad MakarovIJ70_Base<87771df0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_21-03-36.log:Weapon.OnStoreLoad Izh18_Base<870121d0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-07_21-03-36.log:Weapon.OnStoreLoad AKS74U<616b79e0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_15-00-30.log:Weapon.OnStoreLoad Vikhr<66cc7be0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_15-00-30.log:Weapon.OnStoreLoad TF_AEK999<79536d00> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_15-00-30.log:Weapon.OnStoreLoad SKS_Base<5dbcd4c0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_18-00-24.log:Weapon.OnStoreLoad CZ527_Base<676245f0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_18-00-24.log:Weapon.OnStoreLoad SKS_Base<a7f940c0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_18-00-24.log:Weapon.OnStoreLoad Vikhr<74835200> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_18-00-24.log:Weapon.OnStoreLoad TF_AEK999<72aa5010> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_21-01-06.log:Weapon.OnStoreLoad CZ527_Base<381086a0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_21-01-06.log:Weapon.OnStoreLoad SKS_Base<7eab0b50> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_21-01-06.log:Weapon.OnStoreLoad Vikhr<88985b30> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-08_21-01-06.log:Weapon.OnStoreLoad TF_AEK999<73988710> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_15-00-30.log:Weapon.OnStoreLoad CZ527_Base<5f5df260> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_15-00-30.log:Weapon.OnStoreLoad TF_MakarovPB<884f7390> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_15-00-30.log:Weapon.OnStoreLoad CZ61_Base<62aa3380> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_15-00-30.log:Weapon.OnStoreLoad MKII_Base<66861050> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_15-00-30.log:Weapon.OnStoreLoad Mp133Shotgun_Base<665973b0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_22-11-59.log:Weapon.OnStoreLoad AK74<652ddc60> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_22-11-59.log:Weapon.OnStoreLoad M16A2_Base<8c75dec0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-09_22-11-59.log:Weapon.OnStoreLoad AKS74U<681257f0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-10_06-00-30.log:Weapon.OnStoreLoad AK74<7a2f2ba0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-10_06-00-30.log:Weapon.OnStoreLoad M16A2_Base<a6cc9fb0> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-10_06-00-30.log:Weapon.OnStoreLoad AKS74U<765b3e80> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-10_07-47-00.log:Weapon.OnStoreLoad AK74<60492550> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-10_07-47-00.log:Weapon.OnStoreLoad M16A2_Base<8bc90900> trying to set muzzle index 5 while it only has 1 muzzles!
crash_2025-03-10_07-47-00.log:Weapon.OnStoreLoad AKS74U<684ceb00> trying to set muzzle index 5 while it only has 1 muzzles!

Without a .mdmp file we cannot analyse the cause of the crash

I added it above in the comment, but I'll add another one.

I'm adding mdmp files from server. I hope they help.

Last mdmp and crashlogs from server

Thank you, was the server wiped with the 1.27 release? And are you running any mods?

We are still testing, i.e. wipes every now and then. The server was installed after update 1.27. We currently have several mods, we tried EDO weapons, Tactical FLAVA, currently SNAFU, but the problem was with every mod. After changing mods, there was always a wipe. The problem is most noticeable when the player logs out with a weapon in hand. After logging in, the server crashes with the error mentioned.

mod:
@CF;
@Dabs Framework;
@DayZ-Expansion-Bundle;
@DayZ-Expansion-Licensed;
@VPPAdminTools;
@Early Winter or late Fall in hernarus;
@DBN_FordRaptor_Scorpio;
@TerjeCore;
@TerjeMedicine;
@TerjeSkills;
@TerjeCompatibilityVPP;
@InediaInfectedAI;
@RaG_BaseBuilding;
@Namalsk Survival;
@SkyZ - Skybox Overhaul;
@Jiggles Signs;
@Forward Operator Gear;
@Snafu Weapons

servermod @GoreZ

In T189830#2768587, @Geez wrote:

Thank you, was the server wiped with the 1.27 release? And are you running any mods?

First wiped, then even fresh install from zero.

Modlist first instance:

#CF = 1559212036
#COT = 1564026768
#Dabs = 2545327648
#Expansion:
#Bundle = 2572331007
#Licensed = 2116157322

#Earplugs = 1819514788
#SearchForLoot = 3200745813
#BetterTrac = 3191155841
#InventoryInCar = 2361330944
#Immersive_Veh = 3105330157
#BuildEverywhere = 3257424504
#BaseBuildingPlus = 1710977250
#Fortifications = 2670506982
#SolarPanel = 2534155979
#FOGear = 2931560672
#FoGearPatches = 3428742051
#Money = 2018887948
#MoneyRuble = 2859892611
#Refuel = 2470924704

After another clean install:
#CF = 1559212036 +
#COT = 1564026768 +
#Dabs = 2545327648 +
#Expansion:
#Core = 2291785308 +
#Licensed = 2116157322 +
#Spawn = 2804241648 +
#Navi = 2792984722 +
#Groups = 2792983364 +
#Tags = 2576460232 +
#Chat = 2792982897 +
#Book = 2572324799 +
#Build = 2792982513 +
#Hardline = 2828487396 +
#Market = 2572328470 +

Then added and wiped:

#Earplugs = 1819514788 +
#Radio = 3111941154 +
#SearchForLoot = 3200745813 +
#BetterTrac = 3191155841 +
#InventoryInCar = 2361330944 +
#Immersive_Veh = 3105330157 +
#BuildEverywhere = 3257424504 +
#BaseBuildingPlus = 1710977250 +
#Fortifications = 2670506982 +
#SolarPanel = 2534155979 +
#FOGear = 2931560672 +
#FoGearPatches = 3428742051 +
#Money = 2018887948 +
#MoneyRuble = 2859892611 +
#Rag Vehi = 2880254695 +
#Better Inspect = 1940434090 +
#more melee = 2445422689 +
#Refuel = 2470924704 +

I made a clean new server with only @CF and @VPP and everything works as it should. I assume that the problem mentioned is from the Expansion mod. The expansion guys will have to update it.

I tested it today without the Expansion-bundle, but the same error. Things like ammo and magazines in the inventory are duplicated after a server restart. The problem is also with water and energy, they always reset to the value 599.709 I don't understand.

49940 13:19:15 SCRIPT (E):
49941 Weapon.OnStoreLoad SNAFU_M70_Base<82ec4aa0> trying to set muzzle index 5 while it only has 1 muzzles!
49942 Class: 'SNAFU_M70_Base'
49943 Entity id:3011046
49944
49945 Function: 'Error'
49946 Stack trace:
49947 scripts/1_Core/proto\endebug.c:92
49948 scripts/4_World/entities\firearms\weapon_base.c:503
49949
49950 13:19:15 [ERROR][SNAFU_M70] :: state load does not correspond to state save
49951 13:19:15 [ERROR][Mag_AKM_Drum75Rnd_Black] :: state load does not correspond to state save
49956 13:19:15 [ERROR][FOG_Big_Patch_KillCell] :: state load does not correspond to state save
49957 13:19:15 [ERROR][BandageDressing] :: state load does not correspond to state save
49958 13:19:15 [ERROR][Ammo_762x39] :: state load does not correspond to state save
49959 13:19:15 [ERROR][Mag_AKM_Drum75Rnd_Black] :: state load does not correspond to state save
49960 13:19:15 [ERROR][Ammo_762x39] :: state load does not correspond to state save
49961 13:19:15 [ERROR][Ammo_762x39] :: state load does not correspond to state save
49962 13:19:15 [ERROR][Ammo_762x39] :: state load does not correspond to state save
49963 13:19:15 [ERROR][Mag_AKM_Drum75Rnd_Black] :: state load does not correspond to state save

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weapon_base.c:503
SCRIPT (E):
[wpnfsm] ValidateAndRepair Attempting to repair: SNAFU_M70:33012 - MagazineRepair - RBF_CLO_BU0_MA0<a3b3ebb0> - state: 0 != weapon: 1
Class: 'WeaponFSM'
Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weaponfsm.c:545
scripts/4_World/entities\firearms\weaponfsm.c:477
scripts/4_World/entities\firearms\weaponfsm.c:455
scripts/4_World/entities\firearms\weapon_base.c:1064
scripts/4_World/entities\manbase\playerbase.c:2320
scripts/3_Game/dayzgame.c:2919
JM/CF/Scripts/3_Game/communityframework\game\dayzgame.c:23
VPPAdminTools/3_Game/vppadmintools\vanillaplusplus.c:211

There's something messed up with:

override bool OnStoreLoad(ParamsReadContext ctx, int version)

in weapon_base.c

Any BI Dev care to take a look or are we just suppose to shut up and buy the dlc?

In T189830#2769203, @fraky wrote:

I made a clean new server with only @CF and @VPP and everything works as it should. I assume that the problem mentioned is from the Expansion mod. The expansion guys will have to update it.

no I've seen that on servers without expansion mods.

Can confirm, do not have expansion and this shows in crash log. Though im not sure its a crash producing error

In T189830#2771525, @Toggy wrote:

Can confirm, do not have expansion and this shows in crash log. Though im not sure its a crash producing error

Thank you, we are currently investigating the issue.
Regards,
Geez

Hi,
any idea how to solve it? I made a new server without Expansion mod, because I assumed that the problem was there. But apparently it wasn't, only when using Expansion mod the server crashed when an error occurred with muzzle index. I tested the server myself for three days with about KA-101 weapons, ACC Honey badger from SNAFU mod. The problem didn't appear for me. Yesterday other players joined and the problem is back. The server doesn't crash, but the error message is displayed:

23:13:36 [StateMachine]: Player TarXp (dpnid .... uid ...... Entering GetLoadedCharLoginState
23:13:36 [ERROR][SurvivorM_Quinn] :: state load does not correspond to state save
23:13:36 Warning: No components in dz\characters\heads\m_quinn.p3d:geometry
Ref to nonnetwork object SurvivorM_Quinn:0
23:13:36 [ERROR][JumpsuitJacket_Red] :: state load does not correspond to state save
23:13:36 [ERROR][LeatherSewingKit] :: state load does not correspond to state save
23:13:36 [ERROR][IodineTincture] :: state load does not correspond to state save
23:13:36 [ERROR][AmmoBox_9x19_25rnd] :: state load does not correspond to state save
23:13:36 [ERROR][WoodenStick] :: state load does not correspond to state save
23:13:36 [ERROR][FlashGrenade] :: state load does not correspond to state save
23:13:36 [ERROR][AmmoBox_9x19_25rnd] :: state load does not correspond to state save
23:13:36 [ERROR][AmmoBox_9x19_25rnd] :: state load does not correspond to state save
23:13:36 [ERROR][Pitchfork] :: state load does not correspond to state save
23:13:36 [ERROR][WoolGlovesFingerless_Green] :: state load does not correspond to state save
23:13:36 [ERROR][Broom] :: state load does not correspond to state save
23:13:36 [ERROR][ArmyPouch_Black] :: state load does not correspond to state save
23:13:36 [ERROR][TunaCan] :: state load does not correspond to state save
23:13:36 SCRIPT (E):
Weapon.OnStoreLoad Colt1911<133da4b0> trying to set muzzle index 5 while it only has 1 muzzles!
Class: 'Colt1911'
Entity id:3011696

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weapon_base.c:503

23:13:36 [ERROR][Colt1911] :: state load does not correspond to state save
23:13:36 [ERROR][Mag_1911_7Rnd] :: state load does not correspond to state save
23:13:36 [ERROR][Pliers] :: state load does not correspond to state save
23:13:36 [ERROR][ReflexOptic] :: state load does not correspond to state save
23:13:36 [ERROR][TacticalGloves_Beige] :: state load does not correspond to state save
23:13:36 [ERROR][Mag_1911_7Rnd] :: state load does not correspond to state save
23:13:36 [ERROR][M68Optic] :: state load does not correspond to state save
23:13:36 [ERROR][Rag] :: state load does not correspond to state save
23:13:36 [ERROR][NailBox] :: state load does not correspond to state save
23:13:36 [ERROR][FieldShovel] :: state load does not correspond to state save
23:13:36 [ERROR][FaceCover_Improvised] :: state load does not correspond to state save
23:13:36 [ERROR][WorkingBoots_Beige] :: state load does not correspond to state save
23:13:36 [ERROR][RopeBelt] :: state load does not correspond to state save
23:13:36 [ERROR][SteakKnife] :: state load does not correspond to state save
23:13:36 [ERROR][DarkMotoHelmet_Red] :: state load does not correspond to state save
23:13:36 [ERROR][JumpsuitPants_Grey] :: state load does not correspond to state save
23:13:36 [ERROR][Hatchet] :: state load does not correspond to state save
23:13:36 [ERROR][Pajka] :: state load does not correspond to state save
23:13:36 [ERROR][Ammo_762x39] :: state load does not correspond to state save
23:13:36 [ERROR][Rag] :: state load does not correspond to state save
23:13:36 [ERROR][Hook] :: state load does not correspond to state save
23:13:36 [ERROR][BandageDressing] :: state load does not correspond to state save
23:13:36 [ERROR][Hook] :: state load does not correspond to state save
23:13:36 [ERROR][SewingKit] :: state load does not correspond to state save
23:13:36 <LOAD EXISTING CHAR>:

charID 3
playerID 3
dpnid ......
uid .........

23:13:36 <LOAD EXISTING CHAR>:

charID 3
playerID 3
dpnid .......
uid .....

mods="@Namalsk\ Survival\;@winter\ Chernarus\ V2\;@CF\;@VPPAdminTools\;@InediaInfectedAI\;@TerjeCore\;@TerjeMedicine\;@TerjeSkills\;@TerjeCompatibilityVPP\;@CJ187-MoreCrashsites\;@TraderPlus\;@CJ187-PokemonCards\;@CJ187-ToxicZoneAlarm\;@Advanced\ Crafting\;@Forever_Burning_Campfire\;@FridForsMods\ Wooden\ CrossBow\;@DBN_FordRaptor_Scorpio\;@MiniMap\ Relocated\;@RaG_BaseBuilding\;@RaG_Hunting_Cabin\;@Realistic\ Suppressors\;@Realistic\ Weapons\;@Code\ Lock\;@Zens\ Firewood\ Piles\;@Zens\ Chicken\ Coops\;@Zens\ Music\;@SchanaModGlobalChat\;@Forward\ Operator\ Gear\;@Snafu\ Weapons\;@A-Frame-House\;@MMG\ Base\ Storage\;@SkyZ\ -\ Skybox\ Overhaul\;@mod\ Options\;@KillFeedLanky"
servermods="@GoreZ"

I don't know if it has anything to do with the bug report, but this is what happens to players: If they have one piece of ammo in their inventory, after restarting the server and logging in they already have a full stack of 20 pieces ammo. If their magazine is empty, they will be refilled with rounds until it is full. They also don't have their life and water values, they always end up with about 599.

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

[ OK ] Updating dayzserver: Checking for update: SteamCMD

Update available

• Local build: 17405900
• Remote build: 17692189
• Branch: public

The update is out, we're looking forward to it like children :)

I had just a crash (after updating to the last release today), with the same origin. Not a vanilla server though:

Weapon.OnStoreLoad CZ527_Base<929f1390> trying to set muzzle index 5 while it only has 1 muzzles!
Class:      'CZ527_Base'
Entity id:2958827

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weapon_base.c:503
SCRIPT       : Lifespan state missing
SCRIPT       : string output = '16:25:52.550 [AI Object Patrol 00001] Spawning 2 East bots at <1462.594727, 183.630005, 7381.012695>'
SCRIPT       : string output = '16:25:52.835 [AI Object Patrol 00001] Global patrol count: 1'
SCRIPT       : string output = '16:25:52.835 [AI Object Patrol 00010] Spawning 3 East bots at <1470.504395, 183.674210, 7396.302246>'
SCRIPT       : string output = '16:25:52.867 [AI Object Patrol 00010] Global patrol count: 2'
SCRIPT       : [wpnfsm] ValidateAndRepair Attempting to repair: Glock19:21779 (owner eAI_SurvivorM_Denis<8113e730>) - ChamberRepair - Pistol_OPE_DIS_BU0_MA1<84c48ce0> - state: 0 != weapon: 1
Class:      'WeaponFSM'

Function: 'ValidateAndRepairHelper'
Stack trace:
SCRIPT       : DayZExpansion/Core/Scripts/4_World/dayzexpansion_core\entities\firearms\weaponfsm.c:30
SCRIPT       : [wpnfsm] ValidateAndRepair Attempting to repair: Glock19:21741 (owner eAI_SurvivorF_Irena<9800ecf0>) - ChamberRepair - Pistol_OPE_DIS_BU0_MA1<7cc065b0> - state: 0 != weapon: 1
Class:      'WeaponFSM'

Function: 'ValidateAndRepairHelper'
Stack trace:
SCRIPT       : DayZExpansion/Core/Scripts/4_World/dayzexpansion_core\entities\firearms\weaponfsm.c:30

The new line is this one: SCRIPT : Lifespan state missing

@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

It's the same for me, after restarting the server, health and water are reset to the default 599. and the player's ammo is replenished to a full 20 pieces, if he had less. I'm going to cry in the corner.

Weapon.OnStoreLoad Colt1911<8fa77150> trying to set muzzle index 5 while it only has 1 muzzles!
Class: 'Colt1911'
Entity id:3009688

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
scripts/4_World/entities\firearms\weapon_base.c:503

17:22:25 [ERROR][Colt1911] :: state load does not correspond to state save
17:22:25 [ERROR][Mag_1911_7Rnd] :: state load does not correspond to state save
17:22:25 [ERROR][FieldShovel] :: state load does not correspond to state save
17:22:25 [ERROR][FaceCover_Improvised] :: state load does not correspond to state save
17:22:25 [ERROR][WorkingBoots_Beige] :: state load does not correspond to state save
17:22:25 [ERROR][RopeBelt] :: state load does not correspond to state save
17:22:25 [ERROR][SteakKnife] :: state load does not correspond to state save
17:22:25 [ERROR][DarkMotoHelmet_Red] :: state load does not correspond to state save
17:22:25 [ERROR][JumpsuitPants_Grey] :: state load does not correspond to state save
17:22:25 [ERROR][Hatchet] :: state load does not correspond to state save
17:22:25 [ERROR][Pajka] :: state load does not correspond to state save
17:22:25 [ERROR][Ammo_762x39] :: state load does not correspond to state save
17:22:25 [ERROR][Rag] :: state load does not correspond to state save
17:22:25 [ERROR][Hook] :: state load does not correspond to state save
17:22:25 [ERROR][BandageDressing] :: state load does not correspond to state save
17:22:25 [ERROR][Hook] :: state load does not correspond to state save
17:22:25 [ERROR][SewingKit] :: state load does not correspond to state save
17:22:25 [ERROR][Ammo_762x39] :: state load does not correspond to state save
17:22:25 <LOAD EXISTING CHAR>:

charID 3
playerID 3

In T189830#2774524, @fraky wrote:

It's the same for me, after restarting the server, health and water are reset to the default 599. and the player's ammo is replenished to a full 20 pieces, if he had less. I'm going to cry in the corner.

again, thats a different issue. That happens when the player is missing in the storage of the CF mod. Which is either a bug in the mod or the result of the server crashing. I've linked the CF bug above.

Hey, we're facing the same issue regarding the error "Weapon.OnStoreLoad <WEAPON> trying to set muzzle index 5 while it only has 1 muzzles!".
Unfortunately we have not found any clear evidence when it occurs, sometimes 2 hours after serverwipe, sometimes 2 days.

Now let's get an overview of how many of these servers that are having problems are running under Linux like the OP.

It also occurred to me how much Linux and how much Windows. My server runs on Linux. I'm going to try it on Windows, because I'm starting to get nervous.

To share the information I have up to this point, the issue seems to be related to FileSerializers. It looks like they cannot reliably be written, and maybe also not reliably be read, under Linux. The failures seem to be silent during the actual write/read, i.e. the game doesn't print or otherwise hint at anything being wrong, which is why the effects of these failures crop up later when the read data is attempted to be used.

It looks like FileMode.APPEND does not work under Linux, the file is seemingly overwritten if opened in that mode. Note that I'm basing this off logs and files that people have sent me, as I currently don't have a Linux testing setup. If you want to test this theory, put this code into your init.c (e.g. at the bottom of the main function):

FileSerializer s = new FileSerializer();
for (int i = 0; i < 2; i++)
{
    if (s.Open("$profile:test.bin", FileMode.APPEND))
    {
        s.Write("TEST");
        s.Close();
    }
}

After running that, the file test.bin in your server profile directory should contain (hex) 04 00 00 00 54 45 53 54 04 00 00 00 54 45 53 54 (same string twice). If it only contains 04 00 00 00 54 45 53 54 (once), then that's indeed the mode of failure.

In T189830#2775121, @lava76 wrote:

It looks like FileMode.APPEND does not work under Linux, the file is seemingly overwritten if opened in that mode. Note that I'm basing this off logs and files that people have sent me, as I currently don't have a Linux testing setup. If you want to test this theory, put this code into your init.c (e.g. at the bottom of the main function):

FileSerializer s = new FileSerializer();
for (int i = 0; i < 2; i++)
{
    if (s.Open("$profile:test.bin", FileMode.APPEND))
    {
        s.Write("TEST");
        s.Close();
    }
}

After running that, the file test.bin in your server profile directory should contain (hex) 04 00 00 00 54 45 53 54 04 00 00 00 54 45 53 54 (same string twice). If it only contains 04 00 00 00 54 45 53 54 (once), then that's indeed the mode of failure.

Added... Testing.. Will post results

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

But: either a segfault on restart, or its getting stuck on munmap_chunk(): invalid pointer
I've attached a mdmp from a segfault.

Unfortunaly I could not get a memory dump from the stuck process, sending a sigsegv didn't create an mdmp file.

So indeed that looks like the FileSerializer is broken.

@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();
+     }

FileMode.WRITE worked as expected, FileMode.APPEND did just to nothing at all.
With FileMode.WRITE the content was also write on Close().
(yes, I didn't check if open was successful....)

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.

Same here...
Server start -> file gets created at 0KB
player enters -> no change...
player leaves afer a while -> no change...
Server resatrt -> no change...

Effect -> Empty test.bin

Effect for player -> bad spawn (Dark screen location given as Vibor Airfield, 0 in parameters, zombie sounds everywhere - database error?)

No, it's very much related. The muzzle index being wrong on load is just an effect of the bug.

I've moved that into https://feedback.bistudio.com/T190201 - the muzzle error is a bug on its own.

In T189830#2775168, @lava76 wrote:

No, it's very much related. The muzzle index being wrong on load is just an effect of the bug.

True. Anyway, I guess a new easy to read bug report is not bad and @Geez can merge them always.

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.

As a weird workaround, I myself as an admin experienced it and couldn't even log into my own server. I copied the player database blob from one player to mine, logged in and blammo, worked fine. It's like database entries for a player just get corrupt and it crashes on loading in?

Super weird, and I see the same strange muzzle errors when loading in, but like you said that may be a symptom of the issue. Same thing though, for the first hour of me playing i was just floating around the map doing my thing, working on coordinates to setup a trader and what not. Then I equipped a weapon. A few minutes later, crash. Muzzle error in log. Doesn't seem to be a specific mod, but I've had this on two different maps. I also see it often when players log out and log back in, or after a restart.

Hi,

I moved the server from Linux to Windows 10 with the same configuration and it works there. It's a problem in Linux, as you wrote.

Any news on issue beeing fixed?

In T189830#2777643, @fraky wrote:

Hi,

I moved the server from Linux to Windows 10 with the same configuration and it works there. It's a problem in Linux, as you wrote.

https://feedback.bistudio.com/T190201 - that is the reason. If I remember right, O_APPEND is enough in windows to append to a file, but linux needs O_APPEND | O_WRONLY or O_APPEND | O_RDWR, and that is completely broken.

Right now the linux dayz server even seems to have issues with its own persistance due to that. Not 100% sure though, feels weird on vanilla though.

The workaround I've posted in https://feedback.bistudio.com/T190201 also fixes that error for me.