Tracking Down Ubuntu BASH Session Closing

scottalanmiller

@kamidon said in Tracking Down Ubuntu BASH Session Closing:

@dbeato said in Tracking Down Ubuntu BASH Session Closing:

I see this issue with Graphics card drivers. I would start by upgrading the video card drivers even if it means removing and installing again the package.

Oh wow, great point, the graphic driver could be crashing, causing a remote disconnect. Nice

Maybe, there is definitely lots of extra code in there, but the connection is via SSH only, so in theory the GUI could crash and never impact us.

scottalanmiller

@kamidon said in Tracking Down Ubuntu BASH Session Closing:

@IRJ said in Tracking Down Ubuntu BASH Session Closing:

@dbeato said in Tracking Down Ubuntu BASH Session Closing:

I see this issue with Graphics card drivers. I would start by upgrading the video card drivers even if it means removing and installing again the package.

Removing GUI could quickly verify this

How do Runtime levels work? Could he remote in at that GUIless runtime level 3 or w/e?

That's what we are doing.

scottalanmiller

@dbeato said in Tracking Down Ubuntu BASH Session Closing:

I see this issue with Graphics card drivers. I would start by upgrading the video card drivers even if it means removing and installing again the package.

The problem with removing them is that it is a CUDA processing server.

kamidon

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

That's what we are doing.

Are the lower runtimes essentially the equivalent to Windows Safemode?
Edit: Except I'm sure the Linux end is significantly more robust since Safemode is so damned restricted.
"OH NOPE, can't do that, sorry." lol.

dafyre

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

@JaredBusch said in Tracking Down Ubuntu BASH Session Closing:

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

@IRJ brand new users have the issue, too.

Doesn't bash have a global default config that applies to all users?

It has one, yes. But it's vanilla. And even removing it, no change.

What happens if you connect to the VM's console and log in via the terminal (not the gui) ?

What about running the shell from within MeshCentral -- do you still get disconnected that way?

scottalanmiller

@kamidon said in Tracking Down Ubuntu BASH Session Closing:

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

That's what we are doing.

Are the lower runtimes essentially the equivalent to Windows Safemode?
Edit: Except I'm sure the Linux end is significantly more robust since Safemode is so damned restricted.
"OH NOPE, can't do that, sorry." lol.

Kind of, yes. Mode 3 is just the "normal" non-GUI mode. Some modes are for custom stuff. You can customize any mode, though, if you want.

scottalanmiller

@dafyre said in Tracking Down Ubuntu BASH Session Closing:

What happens if you connect to the VM's console and log in via the terminal (not the gui) ?

We didn't build the server, it's not virtualized - likely because it is used as a CUDA system and is older.

scottalanmiller

@dafyre said in Tracking Down Ubuntu BASH Session Closing:

What about running the shell from within MeshCentral -- do you still get disconnected that way?

Does that stay connected normally?

dafyre

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

@dafyre said in Tracking Down Ubuntu BASH Session Closing:

What about running the shell from within MeshCentral -- do you still get disconnected that way?

Does that stay connected normally?

Once you hit "CONNECT" it will stay connected until you type exit or logoff enough times.

matteo nunziati

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

@matteo-nunziati said in Tracking Down Ubuntu BASH Session Closing:

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

If I use zsh, I'm good. If I enter BASH from zsh, I get kicked out after several seconds. Definitely is something to do with BASH.

Stupid tryout: use bash and then enter zsh before being kicked out. Still out?
To understand if it is the firing of bash itself or the stay in bash...

No, the underlying bash remains until the ZSH closes. Same as if you were running top from it, for example.

So basically bash is able to run long running jobs with your user...
It's the interactivity with the shell to be broken... Meh.

Sorry the thread is long, did you mention any test from zsh with:

Bash <-- ok this kills the session
Bash -i any difference???
Bash -l ???
bash --norc
bash --noprofile

From bashman page