Page MenuHomeFeedback Tracker

Server not creating new DayZServer_x64.ADM after restart
Need More Info, NormalPublic

Description

Normally, when the server starts it creates DayZServer_x64.ADM. When the server is restarted, the file is replaced by a new file with the same name with only "AdminLog started on yyy-mm-dd at hh:mm:ss" in it. For the past 2 days, my server has not been creating the new file. Instead it re-uses the same DayZServer_x64.ADM file and appends a new "AdminLog started on yyy-mm-dd at hh:mm:ss" to it. This is happening after both restarts and stop/start. The result is one large ADM file with numerous AdminLog headings in it. What can be causing this? I am experiencing this one two servers.

Details

Severity
Minor
Resolution
Open
Reproducibility
Random
Operating System
Windows 7
Category
Server
Steps To Reproduce

Delete all ADM files.
Start server.
View contents of DayZServer_x64.ADM file and observe there is one heading inside.
Restart server.
There is still only one ADM file DayZServer_x64.ADM and it contains two "AdminLog started on yyy-mm-dd at hh:mm:ss" headings inside it.

Additional Information

This has happened randomly on numerous occasions. However in the past 48 hours it has happened repeatedly.

Event Timeline

ZRaider created this task.Jun 27 2022, 3:49 PM
Geez changed the task status from New to Need More Info.Jun 28 2022, 10:39 AM
Geez added a subscriber: Geez.

Hello ZRaider.
Please double check the time/date settings on the pc where the server is hosted. This problem sounds like if the .adm file was created with future date or that the date was not changed on the machine.
You can also try to manually delete the file which may force it to behave the normal way again.
Regards,
Geez

Hi Geez,

Thanks for the prompt response. I don't have access to the system time, however the current file has the following headings in it:
AdminLog started on 2022-06-27 at 09:34:22
AdminLog started on 2022-06-27 at 13:54:55
AdminLog started on 2022-06-27 at 20:33:16

In that order. Those time stamps coincide with the server restart events (which were all done manually). Deleting the file does force a new one to be created. But the next restart its still using the same file.'

Also, it is not creating the rolled over copy of the ADM file (for example DayZServer_x64_2022_06_27_210044858.ADM) as it normally would after a restart.

Thank you.

Geez added a comment.Jun 28 2022, 4:38 PM

Hello ZRaider.
All of these AdminLogs were created on the same day, which will not make it create a new file. Only when new day is detected a new .ADM file is going to be created.
Regards,
Geez

When it's working "normally", it creates a new DayZServer_x64.ADM each time the server is restarted. I just now restarted the server manually and it created a new file. The previous file is named: DayZServer_x64_2022_06_28_224130454.ADM and contains the heading: AdminLog started on 2022-06-28 at 10:19:28

After restart (on the same day) I have a new file named DayZServer_x64.ADM which contains the heading AdminLog started on 2022-06-28 at 22:41:30

As you can see they both were created on the same day. This is how it behaves 95% of the time. As for which behavior is correct, that I don't know. The reason I'm trying to find out why it behaves differently is that I'm working on a script to parse the events. This is a minor inconvenience but I would like to know how it is "supposed" to work so that I can design accordingly.

Thanks again!

Geez added a comment.Jun 29 2022, 11:27 AM

Hello ZRaider.
Can you please send us your server setup and modlist (if you are using any mods)?
Regards,
Geez

ZRaider added a subscriber: basic.Jun 29 2022, 3:51 PM

Command line:
-ip=x.x.x.x -port=2302 -profiles=c:\...\Admin -bepath=c:\...\Battleye -config=serverDZ.cfg -adminlog -dologs -freezecheck "-mod=@CF;@VanillaPlusPlusMap;@Code Lock;@Free Helicopters;@Hummer_Armored;@IRP-Land-Rover-Defender-110;@basic Ear Plugs;@BuildEverywhere;@Airdrop-Upgraded;@Gas-Pump-Refueling;@Radioactive Animals;@CabinZ;@DeerIsle;@SchanaModGlobalChat;@Raft;@MuchStuffPack" "-servermod=@SkyFall"

serverDZ.cfg:

hostname = "..edited.."; Server name
password = "";
Password to connect to the server
passwordAdmin = ""; Password to become a server admin
maxPlayers = 30;
Maximum amount of players

verifySignatures = 2; Verifies .pbos against .bisign files. (only 2 is supported)
forceSameBuild = 1;
When enabled, the server will allow the connection only to clients with same the .exe revision as the server (value 0-1)
disableRespawnDialog = 0;
enableWhitelist = 0; // Disable/Enable whitelist (value 0-1)

disableVoN = 0; Enable/disable voice over network (value 0-1)
vonCodecQuality = 7;
Voice over network codec quality, the higher the better (values 0-30)

disable3rdPerson=0; Toggles the 3rd person view for players (value 0-1)
disableCrosshair=0;
Toggles the cross-hair (value 0-1)

serverTime="SystemTime"; Initial in-game time of the server. "SystemTime" means the local time of the machine. Another possibility is to set the time to some value in "YYYY/MM/DD/HH/MM" format, f.e. "2015/4/8/17/23" .
serverTimeAcceleration=8;
Accelerated Time (value 0-24) This is a time multiplier for in-game time. In this case, the time would move 24 times faster than normal, so an entire day would pass in one hour.
serverNightTimeAcceleration=5;
Accelerated Nigh Time - The numerical value being a multiplier (0.1-64) and also multiplied by serverTimeAcceleration value. Thus, in case it is set to 4 and serverTimeAcceleration is set to 2, night time would move 8 times faster than normal. An entire night would pass in 3 hours.
serverTimePersistent=1; Persistent Time (value 0-1) The actual server time is saved to storage, so when active, the next server start will use the saved time value.

guaranteedUpdates=1; // Communication protocol used with game server (use only number 1)

loginQueueConcurrentPlayers=5; The number of players concurrently processed during the login process. Should prevent massive performance drop during connection when a lot of people are connecting at the same time.
loginQueueMaxPlayers=500;
The maximum number of players that can wait in login queue
instanceId = 2; // DayZ server instance id, to identify the number of instances per box and their storage folders with persistence files

storeHouseStateDisabled = false; Disable houses/doors persistence (value true/false), usable in case of problems with persistence
storageAutoFix = 1;
Checks if the persistence files are corrupted and replaces corrupted ones with empty ones (value 0-1)

adminLogPlayerHitsOnly = 0; 1 - log player hits only / 0 - log all hits ( animals/infected )
adminLogPlacement = 1;
1 - log placement action ( traps, tents )
adminLogBuildActions = 1; 1 - log basebuilding actions ( build, dismantle, destroy )
adminLogPlayerList = 1;
1 - log periodic player list with position every 5 minutes
disablePersonalLight = 1; disables personal light for all clients connected to server
logFile = "server_console.log";
Saves the server console log to a file in the folder with the other server logs

steamport = 2303;
steamqueryport = 2305;

class Missions
{

class DayZ
{
    template="empty.deerisle"; // Mission to load on server startup. <MissionName>.<TerrainName>
};

};