Valiante
Assigned
Reported
Comments
I believe the following Microsoft UWP Develop articles relate to and address this issue, if this information could please be relayed to the developers:
Is there a process for getting an update or assigning an issue? This bug remains unresolved and unassigned, and is preventing backup scripts from functioning correctly as they rely on timestamps to detect whether a player has connected/disconnected since the last backup. Without that, taking hourly backups is causing capacity issues.
Issue persists on 1.16.200.2
The timestamp is there at server startup, but drops off after the Difficulty level INFO message is written to the console. They were time-stamped up to and including Version 1.16.40.2, but not from 1.16.100.4 onwards (see below examples);
Before
[2020-11-17 02:00:09 INFO] Starting Server
[2020-11-17 02:00:09 INFO] Version 1.16.40.2
[2020-11-17 02:00:09 INFO] Session ID 1ae7d74c-5f58-4bc6-a187-835d1a63b062
[2020-11-17 02:00:09 INFO] Level Name: Jungle Temple and Treehouse
[2020-11-17 02:00:09 INFO] Game mode: 0 Survival
[2020-11-17 02:00:09 INFO] Difficulty: 2 NORMAL
[2020-11-17 02:00:09 INFO] opening worlds/Jungle Temple and Treehouse/db
[2020-11-17 02:00:12 INFO] IPv4 supported, port: 19132
[2020-11-17 02:00:12 INFO] IPv6 supported, port: 19133
[2020-11-17 02:00:12 INFO] IPv4 supported, port: 33710
[2020-11-17 02:00:12 INFO] IPv6 supported, port: 49241
[2020-11-17 02:00:13 INFO] Server started.
[2020-11-17 02:06:18 INFO] Running AutoCompaction...
[2020-11-17 02:12:18 INFO] Running AutoCompaction...
After
[2020-11-18 02:00:10 INFO] Starting Server
[2020-11-18 02:00:10 INFO] Version 1.16.100.4
[2020-11-18 02:00:10 INFO] Session ID d22584e4-14e4-4af0-9bbd-aa01a12d3c1f
[2020-11-18 02:00:10 INFO] Level Name: Jungle Temple and Treehouse
[2020-11-18 02:00:10 INFO] Game mode: 0 Survival
[2020-11-18 02:00:10 INFO] Difficulty: 2 NORMAL
[INFO] opening worlds/Jungle Temple and Treehouse/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] IPv4 supported, port: 45348
[INFO] IPv6 supported, port: 60435
[INFO] Server started.
[INFO] Running AutoCompaction...
[INFO] Running AutoCompaction...This just happened to me also. Like MCPE-38374 I spawned at high altitude above the world spawn point, not my spawn point or bed.
Oh what horrible timing. I rebuilt my Hyper-V server and re-imported all my VMs, including a Bedrock Server I hadn't used for a couple of months. Fired it up to check it was working ok, but couldn't connect (the exact issue described in this ticket). Spent days on and off trying to figure out what I'd cocked up during the re-import, only to discover this bug completely unrelated to what I'd done - just poor timing.
Indeed, sudo ethtool -K eth0 tx off worked a treat for me too.
Edit: It looks like you need to do this after each fresh boot of the VM. Added the following line to root cron (sudo crontab -e) which seemed to do the trick: