Howdy all.
I have two proxmox nodes in a cluster. On one of them a user cloned out a few machine and afterward node the clone was on went down... and didn't come back up. The web gui was unresponsive, ssh was down, on the bright side: icmp was up. I was able to access the web gui of the second node... and it said that the first node was just down. Red "X". =(
After bugging our physical guy, we saw this after plugging in a vga. When we plugged in a keyboard and mouse it added the new usb devices found. It is important to note that ctrl + c, ctrl + z, escape. Nothing got out of this. We had to hard reboot.
The top reads
"echo 0 > proc/sys/kernel/hung_task_timeout_secs" disables this message.
So I started to look at the syslog. I did see the user log in and clone. The relevant section of the logs are attached if anyone wants to look at them. The .log is actually a .xlsx
Has anyone experienced this before?
I have two proxmox nodes in a cluster. On one of them a user cloned out a few machine and afterward node the clone was on went down... and didn't come back up. The web gui was unresponsive, ssh was down, on the bright side: icmp was up. I was able to access the web gui of the second node... and it said that the first node was just down. Red "X". =(
After bugging our physical guy, we saw this after plugging in a vga. When we plugged in a keyboard and mouse it added the new usb devices found. It is important to note that ctrl + c, ctrl + z, escape. Nothing got out of this. We had to hard reboot.
The top reads
"echo 0 > proc/sys/kernel/hung_task_timeout_secs" disables this message.
So I started to look at the syslog. I did see the user log in and clone. The relevant section of the logs are attached if anyone wants to look at them. The .log is actually a .xlsx
Has anyone experienced this before?
Please try to use a plain text format for the next time while I have too look how to improve the upload enforcement. 