Is it node setup? Today i tried to upgrade my one node cluster, after that VM's fail to start, it turns out that selinux prevents virtlogd to start.

ausearch -c 'virtlogd' --raw | audit2allow -M my-virtlogd
semodule -i my-virtlogd.pp
/sbin/restorecon -v /etc/libvirt/virtlogd.conf

fixed things for me, YMMV.

Best regards,
Misak Khachatryan

On Mon, Apr 10, 2017 at 2:03 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Can you please provide a full sos report from that host?

On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Adding node team.

Il 09/Apr/2017 15:43, "eric stam" <estam@indm.nl> ha scritto:

Yesterday I executed an upgrade on my hypervisor to version 4.1.1.1

After the upgrade, it is impossible to start a virtual machine on it. 

The messages I found: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': Connection refused

[root@vm-1 log]# hosted-engine --vm-status | grep -i engine

Engine status                      : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "down"}

state=EngineUnexpectedlyDown

The redhead version: CentOS Linux release 7.3.1611 (Core) 

Is this a known problem?

Regards, Eric

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users