Jump to content

Backup logs cut off at Unicode characters on Linux

Crestwave

By Crestwave

    • Pending

I've been experiencing several long-standing issues with backup logs on Linux, and figured one of them out. 

$ wc -l *
   532 client_log_2022-04-14-13-34-10.txt
   532 client_log_2022-04-14-13-34-30.txt
   532 client_log_2022-04-14-13-34-57.txt
   402 client_log_2022-04-14-13-35-45.txt
   402 client_log_2022-04-14-13-39-27.txt
   402 client_log_2022-04-14-13-39-42.txt
   402 client_log_2022-04-14-13-46-46.txt
   402 client_log_2022-04-14-14-40-32.txt
   402 client_log_2022-04-14-22-40-50.txt
   402 client_log_2022-04-15-09-34-34.txt
   532 client_log_2022-04-16-16-21-02.txt
   402 client_log_2022-04-16-16-39-22.txt
   532 client_log_2022-04-16-17-00-56.txt
   532 client_log_2022-04-16-18-10-31.txt
   532 client_log_2022-04-17-10-15-25.txt
   402 client_log_2022-04-17-12-01-36.txt
   402 client_log_2022-04-17-17-42-13.txt
   402 client_log_2022-04-17-18-48-33.txt
   402 client_log_2022-04-17-22-13-42.txt
   402 client_log_2022-04-17-22-44-01.txt
   402 client_log_2022-04-17-22-54-23.txt
   402 client_log_2022-04-18-09-37-31.txt
   402 client_log_2022-04-18-19-28-41.txt
   402 client_log_2022-04-18-22-21-44.txt
   402 client_log_2022-04-19-09-41-32.txt
 10960 total

Note: no mods are enabled, but several are downloaded.
All of these cut off at the Chinese character in this line: 

[00:00:01]: WARNING: icon paths for mod workshop-1952541249 (包裹记录) are not valid. Got icon_atlas="modicon.xml" and icon="modicon.tex".


Note that the logs themselves are perfectly fine; it only gets truncated when they are copied over to the backup directory.

This does not quite explain my other issues, such as most of my backup chat logs being blank and the remaining ones cut extremely short with no ending newline after a ': '. ($ is from my prompt) 

$ wc -l *
   0 client_chat_log_2022-04-14-13-34-30.txt
   0 client_chat_log_2022-04-14-13-34-57.txt
   0 client_chat_log_2022-04-14-13-35-45.txt
   0 client_chat_log_2022-04-14-13-39-27.txt
   0 client_chat_log_2022-04-14-13-39-43.txt
   0 client_chat_log_2022-04-14-13-46-46.txt
   0 client_chat_log_2022-04-14-14-40-32.txt
   0 client_chat_log_2022-04-14-22-40-50.txt
   0 client_chat_log_2022-04-15-09-34-34.txt
   0 client_chat_log_2022-04-16-16-21-02.txt
   0 client_chat_log_2022-04-16-16-39-22.txt
   0 client_chat_log_2022-04-16-17-00-56.txt
   0 client_chat_log_2022-04-16-18-10-32.txt
  15 client_chat_log_2022-04-17-10-15-25.txt
   0 client_chat_log_2022-04-17-12-01-36.txt
   1 client_chat_log_2022-04-17-17-42-13.txt
   0 client_chat_log_2022-04-17-18-48-33.txt
   1 client_chat_log_2022-04-17-22-13-42.txt
   6 client_chat_log_2022-04-17-22-44-01.txt
   1 client_chat_log_2022-04-17-22-54-24.txt
   1 client_chat_log_2022-04-18-09-37-32.txt
   0 client_chat_log_2022-04-18-19-28-41.txt
   0 client_chat_log_2022-04-18-22-21-44.txt
   0 client_chat_log_2022-04-19-09-41-32.txt
   0 client_chat_log_2022-04-19-10-00-15.txt
  25 total
$ cat client_chat_log_2022-04-14-14-40-32.txt 
[00:02:54]: [Say] (KU_KSZYEhBU) Crestwave: $ 
$

Backup issues have also been experienced with server logs.

Steps to Reproduce

Play in-game and test out printing Chinese/Unicode characters, then check the backup logs.

Not sure how to specifically reproduce the other issues, it just happens after playing the game normally.

  • Thanks 1
Go to bugs

User Feedback


myxal

Just adding my "+1" to having no useful server logs saved, as of this winter's feast (535066, possibly a few hotfixes after that). Thanks for investigating and posting the cause! :steamthumbsup:

Share this comment

Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...