lwbuk

There are several different sections like it, where you see spawn player_death, change it to call player_death
if you use notepad++ just do a find and replace 
you can also remove the player sethit parts. 

You've done something wrong then. 
Doing something wrong in infistar will only stop infistar from working, rarely it breaks the whole server. 

It's really quite simple. 
Any place it says SPAWN PLAYER_DEATH
change the spawn to CALL. 
You don't need to touch or do anything else. This won't break anything.
 
also as I said make sure if you are using ESS spawn select to make sure the call to the ess spawn_config.sqf in server_functions.sqf is BEFORE the call to infistar  
#include "spawn_config.sqf"; [] execVM "\a2_infiSTAR\AH.sqf"; DO NOT COPY THIS DIRECTLY AS YOUR FILE PATHS MAY BE  DIFFERENT. IT IS JUST AN EXAMPLE. 

Have you enabled body check in the config and amended the body check distance to suit? 
 
In server_playerdied the block should look like 
_newObject setVariable ["bodyName",_playerName,true]; _newObject setVariable ["bodyUID",_playerID,true]; _pos = getPosATL _newObject;

In dayz_server.pbo, go to system>scheduler  then edit sched_sync.sqf to have just this
sched_sync = { objNull };
save it, repack the pbo and enjoy nighttime. 

It's really quite simple. 
Any place it says SPAWN PLAYER_DEATH
change the spawn to CALL. 
You don't need to touch or do anything else. This won't break anything.
 
also as I said make sure if you are using ESS spawn select to make sure the call to the ess spawn_config.sqf in server_functions.sqf is BEFORE the call to infistar  
#include "spawn_config.sqf"; [] execVM "\a2_infiSTAR\AH.sqf"; DO NOT COPY THIS DIRECTLY AS YOUR FILE PATHS MAY BE  DIFFERENT. IT IS JUST AN EXAMPLE. 

Search your ah.sqf and at.sqf for spawn player death.  Change any instance of this to call player death. 
Was supposedly fixed in the latest infistar, but some were missed. 
 
Also so if you are using ess, make sure the call for it is above the call for infistar in server_functions.sqf

Edit these, you will need a custom config_variables in your mission folder. Search is you don't know how to do that. // Death Messages DZE_DeathMsgChat = "system"; //"none","global","side","system" Display death messages in selected chat channel. DZE_DeathMsgDynamicText = true; // Display death messages as dynamicText in the top left with weapon icons. DZE_DeathMsgRolling = false; // Display death messages as rolling messages in bottom center of screen. DZE_DeathScreen = false; // True=Use Epoch death screen (Trade city obituaries have been amended) False=Use DayZ death screen (You are dead) DZE_ServerLogHits = true; // Log damage source, weapon, distance and ammo to server RPT for player hits. Useful for detecting damage and ammo cheats.

Update infistar. 
Once done that, search the code and change any "spawn player death" to call player death. 
Problem fixed. 

This is for Infistar, you aren't running Infistar judging by your other posts. 

I tried a vm set up on an ovh mc-32.  
My orignal plan was to have my servers on a vm and then my father in law wanted a fm on the same box to host his websites with plesk, and we'd share the cost.
Well after a week of trials, I told him I couldn't run on a vm and needed to run on the base machine. 
Performance just wasn't good enough, even with the vm using 90% or so of the resources. 
We scrapped that idea and I just used the whole box to myself. 

@Draundenth i remember when i start installings mods and all about thiss... pass 15 days before know what a F... is a custom compiles.ssqf/fn_selfactions.. and blabla.. glad to see you find someone like iwbuk who try to explain you.
ServerRoot means the root folder of your server.. for example if u server is located in C:\user\epoch1.6.1\
then your serverroot is the content inside of epoch1.6.1\
Your server have 3 importants locations.
Mpmissions folder
Dayz_server.pbo
Dayz_code.pbo
the dayz_server.pbo and Dayz_code.pbo needs an external program like pbo manager to be opened.
When you work in files into dayz_server.pbo.. after you finish. you beed save(pack) the folder again in pbo. format
When you work in files into dayz_code.pbo the effects do not take effects.. so you need drop out of dayz_code this files and put into mpmissions folder or dayz_Server.pbo folder.
 
First thing.. your custom compiles.sqf /variables.sqf and fn_Selfactions  almost 90% of mods needs or use this files.. but this three are located in dayz_code.pbo... so you wiill need drop out from here.. and put in mpmissions folder.
How you do that=?
MAKE YOUR CUSTOM VARIABLES//COMPILES//FN_SELFACTIONS.sqf
 

i dont wanna know what kind of disaster you did in descripition.ext step haha

What do you mean ppm?  Are you saying you have no option to deploy when you right click? 

In dayz_code.pbo. You need to make custom ones in your mission folder and change the calls for them.
Juan posted a good tutorial here
Relevemt steps
 

I didn't do it that way, I changed the call in my new compiles to the new fn_selfactions and removed the call for the original file. 
I'm on my iPad so cant paste any code in the spoiler tags to show you. 
I'll post it tomorrow if no one else answers. 

If I'm around yeah. Still need your server rpt to see why it's not working. 

24 hours? 
I had backups every 15 minutes and players still moaned like little girls when someone hacked and I had to roll back. 

This is for my 1.0.6 server, and is how I do it. You can use the default sql events that come in the server files.
In the Mysql event to set damage to allow maintain, this adds 11% damage every 3 days, it isnt culmative, so damage will never be more than 11%.
UPDATE `Object_DATA` SET `Damage`=0.11 WHERE `ObjectUID` <> 0 AND `CharacterID` <> 0 AND `Datestamp` < DATE_SUB(CURRENT_TIMESTAMP, INTERVAL 3 DAY) AND ( (`Inventory` IS NULL) OR (`Inventory` = '[]') OR (`Classname` IN ('Land_DZE_GarageWoodDoorLocked','Land_DZE_LargeWoodDoorLocked','Land_DZE_WoodDoorLocked','CinderWallDoorLocked_DZ','CinderWallDoorSmallLocked_DZ','Plastic_Pole_EP1_DZ')) ) Then in init.sqf
DZE_DamageBeforeMaint = 0.09; // Min damage built items must have before they can be maintained then another MySQL event to remove old objects
DELETE FROM `Object_DATA` WHERE `LastUpdated` < DATE_SUB(CURRENT_TIMESTAMP, INTERVAL 7 DAY) AND `Datestamp` < DATE_SUB(CURRENT_TIMESTAMP, INTERVAL 14 DAY) This deletes objects that have been built for more than 14 days but havent been updated in 7 days.
When you maintain, it updates, so anything maintained within the last 7 days wont be deleted.
If running 1.0.5.1, you can also change cleanup placed after days to -1 in the hiveext.ini to stop the database removing objects of a certain age.

Doesn't matter, it's the same on 1061. Can't help you with MySQL much, that's something you need to learn yourself.  Kinda important to know when running a server as that's what runs the bulk of it.  If on a game host you'll likely connect to it through phpadmin, or you can download something like navicat on your pc and connect that way. 
You might find the data base doesn't have event scheduling enabled, so you'll also need to run a query to enable it before any of the cleanup events will work.  If you have access to my.ini you can also enable it there. 

Just add plot pole class name to dze_restrictremoval. Then only people on plot list can remove it. 

I never had that issue. Lockboxes and safes held money fine. Never tried vehicles so can't  comment on that one. 
Sounds like a database/hive issue to me

Thats why in my old overpoch server, ATM's were no where near traders. Completely pointless having bank/atm at trader as money is never at risk.
Some players moaned like crap about it. the same players that wanted a start box, and 10mil bank start... The players who are too damn lazy to play the game and want everything handed to them so they can sit in thier penis tower and snipe anything that moves.

Yes, copy into overwatch folder and replace its own dayz_code.pbo and bisign. 
Keep a backup up of the overwatch ones just in case. 

This is the thread where I first found the error.  Read through that to see what was changed in the loot sections of the events and  make sure you have the very latest version of the events you are using. 
The thread below is the all in one events menu activation, but the individual events should be the same.