May 6, 20179 yr I'm having some issues with Unraid, the GUI stops being responsive after a while and the hosted VM's also become unresponsive as I can't ping their IP's. I can still SSH to the host. The server is remote to me so I can't manually power it off to restart it. Is there a way I can retrieve logs to see what is causing this? How do I restart the machine remotely via command line? I assume there must be a procedure to stop Docker, stop KVM, turn off the array then issue a reboot command. Could someone please help me with these commands?
May 6, 20179 yr To stop docker and VM /etc/rc.d/rc.docker stop /etc/rd.d/rc.libvirt stop To restart unRAID /sbin/reboot
May 6, 20179 yr Author Is there another way I can force docker and libvert to stop? Libvirt is unable to connect to hypervisor and docker is stuck at 'stopping docker...' root@shr-unraid1:~# /etc/rc.d/rc.libvirt stop error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Waiting on VMs to shutdownerror: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Stopping libvirtd... error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory virtlogd is not running... root@shr-unraid1:~# /etc/rc.d/rc.docker stop stopping docker ... 'Docker stop' also does not stop the containers, I have to break out to retrieve the command line again. root@shr-unraid1:~# docker stop Zoneminder aptalca/zoneminder-1.29^C
May 7, 20179 yr Author I was able to have someone physically restart the box for me. Turned it back on and was running fine for a few hours running three containers and two VM's. When I started a particular VM I lost the GUI again and could no longer access the original two VM's. I forced the third VM to stop using 'virsh destroy [vm]' but could not access the original two VM's. I tried to shutdown the original two VM's using 'virsh shutdown' and 'virsh destroy', but neither of them worked. Is there a way to retrieve logs to see what might be the cause of the problem? I'm sure it has to do with libvert, QEMU, network bridges or hardware pass through. Whats the best way to dig further to find the cause? These links describe a similar problem not able to use Virsh to control the VM's. https://www.redhat.com/archives/libvirt-users/2014-February/msg00032.html https://www.redhat.com/archives/libvirt-users/2016-April/msg00092.html Edit: Additional info, links Edited May 7, 20179 yr by rcampbell
Archived
This topic is now archived and is closed to further replies.