Hello,

Any idea about this problem? I don't know if the email got through to the list.

Should I join the #vdsm channel and discuss it there? Is there any other place specific to vdsm where I could report this?

Cheers,

-rodri

On 9/15/20 9:55 AM, Rodrigo G. López wrote:

Hi there,

We are trying to setup a node in the same machine where we are running the engine, and noticed that the vdsmd service fails because the supervdsmd daemon can't authenticate against libvirtd afaict.

The error is the following on supervdsmd:

    daemonAdapter[17803]: libvirt: XML-RPC error : authentication failed: authentication failed
    ...

and in libvirtd:

    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.410+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error
    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.612+0000: 17776: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757)
    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.612+0000: 17776: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed
    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.612+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error
    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.814+0000: 17778: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757)
    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.814+0000: 17778: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed
    Sep 15 03:34:18 ovirt-test libvirtd[17775]: 2020-09-15 07:34:18.815+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error
    Sep 15 03:34:19 ovirt-test libvirtd[17775]: 2020-09-15 07:34:19.017+0000: 17780: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757)
    Sep 15 03:34:19 ovirt-test libvirtd[17775]: 2020-09-15 07:34:19.017+0000: 17780: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed
    Sep 15 03:34:19 ovirt-test libvirtd[17775]: 2020-09-15 07:34:19.020+0000: 17775: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error


Is there any way to work around that?

We have working infra on top of 4.0 in CentOS 7 systems, and we would like to replicate the exact same environment for availability purposes, in case anything bad happened.



Best regards,

-rodri

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OO377TE4EZUMYXFGGPPPKNTVJRCGCFS4/