Still present in 53.126384.

This is still a problem. Occurs multiple times a day and is 100% reproducable. Added to that, whatever was done during yesterdays maintenance period, made it so that when the last person leaves the server, the mission/ingame simulation seem to stop. When joining again the ingame time is showing 09:00, indicating that the simulation has been reset.

@JStewart I've sent the support ticket conversation.

It happened this morning. I saw on our Gametracker that the server was offline about 30 minutes after it's scheduled restart. When I started the game and went to the ingame browser, the ingame time was 9:20. As far as I understand, this is usually a number that the server goes through before the actual game simulation has started. When I logged in to the server I first got "wait for host", and then I had a new character instead of my old one. When I logged out and checked the ingame browser again, the ingame time was 9:01, indicating that the simulation didn't start until I logged in. As per the BEC logs below (GUIDs and IPs are removed, my ingame name is bushman), there was no other person logging in before me.

05:31:00 : RCon admin #0: (Global) SERVER RESTART IN 5 MINUTES!
05:36:00 : RCon admin #0: (Global) SERVER RESTART IN ONE MINUTE! LOG OFF NOW TO SAVE YOUR GEAR AND POSITION! To avoid the character reset bug, do to NOT log in again until server time is showing XX.01 (i.e. do not log in when it says 08:00, 09:00, 12:00, or 09:20).
05:36:16 : Player #0 DI.MSI disconnected
05:37:19 : Lost Connection!
05:37:19 : Closing socket & exiting!
05:38:04 : Rcon client logging in
05:38:04 : RCon admin #0 (XXX) logged in
05:58:58 : Player #0 bushman (XXX) connected
05:59:30 : Player #0 bushman - GUID: XXX (unverified)
05:59:33 : Verified GUID (XXX) of player #0 bushman
06:01:20 : Player #0 bushman disconnected

It happened this morning again. Server was set in the 9:20 limbo and didn't startup properly until I joined the server. So the issue should definitely be reproducable. However, my character didn't get wiped this time, although I had to reconnect a couple of times before I even got in.

I don't know if this is a known issue or not. Our hosting partner refers to Bohemia in this matter in their ticket system (ticket #1462708). They also asked me to use their reset world feature, which supposedly resets the "persistency files", but it had no effect on the limbo issue.

Confirmed to still be present in version 53.126384 on our private shard. Having persistency activated too many restarts will also crash the server. This is a game-breaking issue (server crashing), and a gameplay-breaking issue (because without persistency, DayZ is ungodly uninteresting and meaningless. with persistency, one can reach endgame in no time).