Hi everyone,
at the beginning I will point out that with proxmox I am just starting my adventure.
My question is about solving a problem when on a new CT - Ubuntu 22.04, I fire up the following command:
Of course, I invoke it on purpose.
I'm learning how to manage proxmox server, stressing CT systems.
Well, and I came across this case.
This command completely kills my access as root to any terminal on the server.
Whether directly in ssh or in the GUI - it doesn't matter.
While cpu and ram usage on the root instance is still available, I still can't invoke any command - whether to kill the aforementioned stress command or call htop in the terminal.
Why?
Can anyone advise me why this is happening - why by firing stress on CT it affects the whole server even though I still have resources in main memory and cpu?
This is a problem in the range of a hypothetical scenario when some user on the host fires such a command at me.
Lukas
at the beginning I will point out that with proxmox I am just starting my adventure.
My question is about solving a problem when on a new CT - Ubuntu 22.04, I fire up the following command:
Bash:
stress -m 512 -c 1 -t 60I'm learning how to manage proxmox server, stressing CT systems.
Well, and I came across this case.
This command completely kills my access as root to any terminal on the server.
Whether directly in ssh or in the GUI - it doesn't matter.
While cpu and ram usage on the root instance is still available, I still can't invoke any command - whether to kill the aforementioned stress command or call htop in the terminal.
Why?
Can anyone advise me why this is happening - why by firing stress on CT it affects the whole server even though I still have resources in main memory and cpu?
This is a problem in the range of a hypothetical scenario when some user on the host fires such a command at me.
Lukas