FATAL UNHANDELED EXCEPTION when detach and attach with tmux in ubuntu 20.04

[XTARZ]

Operation:

• SSH to my server
• Open a new tmux session
• Inside the session, run mono Terra...exe
• Do some config changes and /reload several times
• Detach from session, exit SSH
• Overnight, SSH to server, attach to session
• Try to input some command
• Error

System Info：

 OS: Ubuntu 20.04 focal                
 Kernel: x86_64 Linux 5.4.0-91-generic 
 Uptime: 6d 10h 58m                    
 Packages: 956                         
 Shell: zsh 5.8                        
 Disk: 7.4G / 51G (16%)                
 CPU: Intel Xeon Gold 6148 @ 2.394GHz  
 GPU: Cirrus Logic GD 5446             
 RAM: 345MiB / 1987MiB                 

Software info:

Tshock: 4.5.12
tmux:  3.0a
mono: 6.8.0.105 (Debian 6.8.0.105+dfsg-2 Wed Feb 26 23:23:50 UTC 2020)

Error Message:

[ERROR] FATAL UNHANDLED EXCEPTION: System.ArgumentOutOfRangeException: Value must be positive and below the buffer height.
Parameter name: top
  at System.TermInfoDriver.SetCursorPosition (System.Int32 left, System.Int32 top) [0x0004d] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.TermInfoDriver.WriteSpecialKey (System.ConsoleKeyInfo key) [0x0006e] in <12b418a7818c4ca0893feeaaf67f1e7f>:0

  at System.TermInfoDriver.Echo (System.ConsoleKeyInfo key) [0x00020] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.TermInfoDriver.ReadUntilConditionInternal (System.Boolean haltOnNewLine) [0x000de] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.TermInfoDriver.ReadLine () [0x00000] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.ConsoleDriver.ReadLine () [0x00000] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Console.ReadLine () [0x00019] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at Terraria.Main.startDedInputCallBack () [0x0000f] in <98a6b92c2e0d4f11bb0711a26c060a83>:0
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <12b418a7818c4ca0893feeaaf67f1e7f>:0

[Arthri]

This has been reported in the TShock Discord before:

You ran the server in a screen instance, correct?
the screen pseudo terminal doesn't support scrolling or something like that, this doesn't happen on linux on a normal session or on windows
- @bartico6

if screen is the cause of your problems, you can run it using tmux. I honestly like it better than screen.

• by Gingersarentsoulless

More info here: https://discord.com/channels/479657350043664384/482065271297671168/780762088313847828

[hakusaro]

the screen pseudo terminal doesn't support scrolling or something like that, this doesn't happen on linux on a normal session or on windows

This is just patently incorrect. See how to scroll in screen.

[XTARZ]

Hmmm... Actually I'm using tmux.

[hakusaro]

@FallenXtar are you using any other plugins? Any tmux plugins, too?

[hakusaro]

@FallenXtar I think it's a tmux exclusive issue. You could try running screen instead. Screen is like tmux, but different. It's less powerful, more simple, etc. If you're not using tmux in a complicated way, I would suggest trying out screen.

screen to start a screen, ctrl + a d to detach, screen -r to reconnect.

If you want to give up the server console, you can try running the server with -disable-commands and see if that doesn't crash the server in tmux overnight. I don't exactly know why it's crashing in the first place. See: #2524 (reply in thread).

TShock works by patching the main dedicated server. So, if we find the fix, we can either pass it to Re-Logic or patch it/fix it in OTAPI most likely. It might even just be fixed by using .NET 6, but I won't say that with certainty.

[XTARZ]

I'll try it out, thank you!

[hakusaro]

@FallenXtar I'm sorry it's more of a bodge than a proper fix. But the fundamental issue is something inside the C# / mono / .NET stack and whatever tmux is doing when you resume. I'm not sure on the actual details of what's causing it though. The stack trace goes back to System and we're on .NET framework 4.5, which is eons old now, so if it was widespread, it's probably been fixed.

[XTARZ]

@hakusaro I'm still using tmux few days,tried to restart process several times to trace the problem but no same errors comes out. Maybe it's just a coinsidence. And thank you for the tips! I will keep notice the server.
By the way, is there a better way to run something like tshock background in Linux if I'm using cloud services?

[hakusaro]

There are other ways to run background processes and they all suck.