what can i do if a CLI session times out?

[whitewum]

the console's session times out, and a scary warning is raised.

I know the reason and restart the CLI. But the message is a bit confusing and hard to guess the solution for other users.

I suggest to write a more friendly suggestion or no reconnect again by the CLI itself.

[Shylock-Hg]

I don't think it's session expire.
If so, will print like:

(user@127.0.0.1:3699) [(none)]> show spaces
[ERROR (-5)]: Session `1' has expired
Mon Mar  2 15:27:23 2020

[whitewum]

That's wired. The connect was idle for someday and I came back to reuse the CLI. And then that warning was raised.

The server is OK. Quit CLI and reconnect will be connected successfully.

What else the problem can be. Any guess.

[Amber1990Zhang]

That's wired. The connect was idle for someday and I came back to reuse the CLI. And then that warning was raised.

The server is OK. Quit CLI and reconnect will be connected successfully.

What else the problem can be. Any guess.

Good quetstion. I encountered the same problem as you.

[Shylock-Hg]

I think maybe it caused by the thrift idle timeout (although we set infinity default, maybe it just drop connection when timeout but not keep alive the connection according the source code, so the infinity idle timeout is overlap by the tcp protocol connection timeout :).

[CPWstatic]

The clients will do retry in latest version.