All,
Problem solved.
I executed the “ restorecon -Rv /etc/ “ command. and the problem is solved.
The other question, execute "semodule -DB “ will give no return of any massage.
Everything is up an running again.
Regards,
Eric
On 10 Apr 2017, 16:10 +0200, Ryan Barry , wrote:
> Hey Eric -
>
> I
We are on the good way.
I first put SELinux in permissive mode, and now it is possible to start
virtual machine's.
I will test the "restorecon" next.
Regards,
Eric
2017-04-10 14:00 GMT+02:00 Yuval Turgeman :
> restorecon on virtlogd.conf would be enough
>
> On Apr 10, 2017 2:51 PM, "Misak Khac
Hey Eric -
It's possible that there are some silent denials in some policy. Can you
please try "semodule -DB" to see if anything pops up?
I'll also try to reproduce this...
On Mon, Apr 10, 2017 at 5:11 AM, eric stam wrote:
> We are on the good way.
> I first put SELinux in permissive mode, and
On Mon, Apr 10, 2017 at 2:11 PM, eric stam wrote:
> We are on the good way.
> I first put SELinux in permissive mode, and now it is possible to start
> virtual machine's.
>
>
> I will test the "restorecon" next.
>
the strange thing here is that the sosreport Eric provided showed no
selinux deni
restorecon on virtlogd.conf would be enough
On Apr 10, 2017 2:51 PM, "Misak Khachatryan" wrote:
> 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
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
Can you please provide a full sos report from that host?
On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
wrote:
> Adding node team.
>
> Il 09/Apr/2017 15:43, "eric stam" ha scritto:
>
> Yesterday I executed an upgrade on my hypervisor to version 4.1.1.1
> After the upgrade, it is impossible to
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" 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
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 eng
9 matches
Mail list logo