TS6 Server BETA - v6.0.0-beta12.1

Announcements
, ,
1

Hey everyone! :waving_hand:

This hotfix resolves a startup crash affecting Windows Server 2019 and Windows 10 versions older than 1903, caused by the local time zone log timestamps introduced in beta12. Server log timestamps now use UTC by default again, while local time can be enabled using the new --log-timezone parameter or TSSERVER_LOG_TIMEZONE environment variable.

You can get the latest server release here:
– GitHub: Release v6.0.0-beta12.1 · teamspeak/teamspeak6-server
– Docker Hub: Release v6.0.0-beta12.1 · teamspeaksystems/teamspeak6-server

Forum Splitter
Forum Splitter1500Ă—150 11 KB

:memo: 6.0.0-beta12.1 Changelog :memo:

:sparkles: What’s New

  • Fixed a startup crash on Windows Server 2019 and Windows 10 releases older than 1903, caused by the local time zone log timestamps introduced in beta12
  • Server log timestamps use UTC again by default, local time can be enabled with the new --log-timezone parameter or TSSERVER_LOG_TIMEZONE environment variable

Please Note:

  • As always, feedback is welcome here. Please note that issues unrelated to this update should be discussed in their own dedicated threads.
  • We encourage you to share your suggestions for future releases in the appropriate threads within the suggestions and feedback area, rather than in the release thread. This is because update posts are typically closed after some time, and suggestions or feature requests may get overlooked.
  • We reserve the right to remove any off-topic posts from this thread.
Don't miss any future Announcements
8 Likes
4

What value should be passed to TSSERVER_LOG_TIMEZONE ?

Btw. for everyone else it’s a value “utc” or “local”, but took me some time to find it. I don’t know why this was pushed with absolute no info at all and just broke the timing… :enraged_face:

5

Very likely tz database time zone notation (List of tz database time zones - Wikipedia).

e.g. Europe/Dublin