
This is a multi-part message in MIME format. --------------D1D0407AE4CFA3C37FF62CF4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello community, yesterday evening one of our nodes was rebooted, but I have not found out why. The engine only reports this: 24.11.2017 22:01:43 Storage Pool Manager runs on Host onode-1 (Address: onode-1.worknet.lan). 24.11.2017 21:58:50 Failed to verify Host onode-1 power management. 24.11.2017 21:58:50 Status of host onode-1 was set to Up. 24.11.2017 21:58:41 Successfully refreshed the capabilities of host onode-1. 24.11.2017 21:58:37 VDSM onode-1 command GetCapabilitiesVDS failed: Client close 24.11.2017 21:58:37 VDSM onode-1 command HSMGetAllTasksStatusesVDS failed: Not SPM: () 24.11.2017 21:58:22 Host onode-1 is rebooting. 24.11.2017 21:58:22 Kdump flow is not in progress on host onode-1. 24.11.2017 21:57:51 Host onode-1 is non responsive. 24.11.2017 21:57:51 VM playout was set to the Unknown status. 24.11.2017 21:57:51 VM gogs was set to the Unknown status. 24.11.2017 21:57:51 VM Windows2008 was set to the Unknown status. [...] There is no crash report, and no relevant errors in dmesg. Does the engine send a reboot command to the node, when it gets no responds? Is there any other way to found out why the node was rebooting? The node hangs on a usv and all other servers was running well... In the time, when the reboot was happen, I had a bigger video compression job in one of the VMs, so maybe the CPUs got a bit stressed, but they are not over committed. Regards Jonathan --------------D1D0407AE4CFA3C37FF62CF4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hello community, <br> </p> <p>yesterday evening one of our nodes was rebooted, but I have not found out why. The engine only reports this:</p> <blockquote> <blockquote> <p>24.11.2017 22:01:43 Storage Pool Manager runs on Host onode-1 (Address: onode-1.worknet.lan).<br> 24.11.2017 21:58:50 Failed to verify Host onode-1 power management.<br> 24.11.2017 21:58:50 Status of host onode-1 was set to Up.<br> 24.11.2017 21:58:41 Successfully refreshed the capabilities of host onode-1.<br> 24.11.2017 21:58:37 VDSM onode-1 command GetCapabilitiesVDS failed: Client close<br> 24.11.2017 21:58:37 VDSM onode-1 command HSMGetAllTasksStatusesVDS failed: Not SPM: ()<br> 24.11.2017 21:58:22 Host onode-1 is rebooting.<br> 24.11.2017 21:58:22 Kdump flow is not in progress on host onode-1.<br> 24.11.2017 21:57:51 Host onode-1 is non responsive.<br> 24.11.2017 21:57:51 VM playout was set to the Unknown status.<br> 24.11.2017 21:57:51 VM gogs was set to the Unknown status.<br> 24.11.2017 21:57:51 VM Windows2008 was set to the Unknown status.<br> [...]</p> </blockquote> </blockquote> <p>There is no crash report, and no relevant errors in dmesg. <br> </p> <p>Does the engine send a reboot command to the node, when it gets no responds? Is there any other way to found out why the node was rebooting? The node hangs on a usv and all other servers was running well...</p> <p>In the time, when the reboot was happen, I had a bigger video compression job in one of the VMs, so maybe the CPUs got a bit stressed, but they are not over committed. <br> </p> <p><br> </p> <p>Regards</p> <p>Jonathan<br> </p> </body> </html> --------------D1D0407AE4CFA3C37FF62CF4--