[BDS-9943] Console output not showing date and time

Summary

After upgrading BDS to 1.16.100, a timestamp no longer preceeds each line in the console output. It appears for the first few lines and is then gone after the difficulty is output.

Steps to reproduce...

Download and start a 1.16.40 based BDS instance
Note the console output displays timestamps on each line
Download and start a 1.16.100 BDS instance
Note that the console output displays no timestamps after initial startup

What I expected to happen...

Timestamps continue on each line in the console output

What actually happened...

No timestamp on each line

How does this impact admins

At the moment, with no meaningful log output option admins rely on the server generated log file that is cleared on each server start, or by copying the console output to a file. This information can be used to check for hangs, determine when players logged on and off etc.

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

Linked issues

is duplicated by 1

BDS-10318 Time stamps don't appear in the server console after 1.16.100 Resolved

Comments 30

John 2020-11-23T16:28:23Z

Same issue here, rather annoying. Upvoted.

migrated 2020-11-23T16:28:23Z

Same issue here, rather annoying. Upvoted.

Valiante 2020-11-24T16:55:42Z

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

migrated 2020-11-24T16:55:42Z

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

J 2020-11-24T19:26:29Z

I really hope the times haven't been removed on purpose... I depend on timestamps so I can roll back the server if someone griefs it. Among other things - like seeing how long a new player has been on, and such... Gotta keep an eye on these kids.

HOW DO I REECH THESE KEEEEEDS?

20 more comments

migrated 2020-11-24T19:26:29Z

HOW DO I REECH THESE KEEEEEDS?

John 2020-11-24T23:03:19Z

Issue still the same with 1.16.101.1 (Thought was unlikely, but tested anyway)

migrated 2020-11-24T23:03:19Z

Issue still the same with 1.16.101.1 (Thought was unlikely, but tested anyway)

Gergely Gy 2020-12-06T12:10:05Z

Same issue here after upgrading to 1.16.100 on Ubuntu Linux 20.04. On version 1.16.40 it was okay.

I run a MCB server at home on a Linux PC and I wrote a bash script if someone connects in the last 10 minutes, my kids and their friends get a notification about a new connection. Now this does not work, actually cannot work without time/date. Hope it will be fixed soon.

migrated 2020-12-06T12:10:05Z

Same issue here after upgrading to 1.16.100 on Ubuntu Linux 20.04. On version 1.16.40 it was okay.

Valiante 2020-12-10T12:47:06Z

Issue persists on 1.16.200.2

migrated 2020-12-10T12:47:06Z

Issue persists on 1.16.200.2

Gergely Gy 2020-12-19T14:08:42Z

Issue persists on 1.16.201.2

migrated 2020-12-19T14:08:42Z

Issue persists on 1.16.201.2

Valiante 2021-01-19T13:20:56Z

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.

migrated 2021-01-19T13:20:56Z

Kris Birchmore 2021-03-22T11:11:27Z

still waiting for this issue to be fixed. Last patch did not correct it. How does this get assigned to a developer to be corrected? It says it is a confirmed bug but nothing has been done about this issue as of yet.

migrated 2021-03-22T11:11:27Z

Bartosz Młot 2021-04-09T06:19:30Z

Issue persists on 1.16.220.2

migrated 2021-04-09T06:19:30Z

Issue persists on 1.16.220.2

Kris Birchmore 2021-04-23T14:23:22Z

Has anyone found a work around for this?

migrated 2021-04-23T14:23:22Z

Has anyone found a work around for this?

jpg 2021-04-23T15:17:41Z

One workaround is to run it in a docker container. The docker logs can be viewed with timestamps.

migrated 2021-04-23T15:17:41Z

One workaround is to run it in a docker container. The docker logs can be viewed with timestamps.

Jesse Foster 2021-06-23T20:12:51Z

Issue still persists on 1.17.2.01

migrated 2021-06-23T20:12:51Z

Issue still persists on 1.17.2.01

Todd B 2021-07-09T19:29:23Z

Same issue for me as well. I have no idea how long users are active on my server without the timestamps in the console window. This doesn't seem like a complex issue that should be persisting this long.

migrated 2021-07-09T19:29:23Z

[Mojang] Mega_Spud (Jay) 2022-04-11T15:28:04Z

We believe this is fixed in the latest version.

[Mojang] Mega_Spud (Jay) 2022-04-11T15:28:04Z

We believe this is fixed in the latest version.