Re: [ovirt-users] database restoration

2018-02-17 Thread Yedidyah Bar David
On Fri, Feb 16, 2018 at 1:04 PM, Fabrice Bacchella
 wrote:
> I'm running a restoration test and getting the following log generated by 
> engine-backup --mode=restore:

Which version?

Did you also get any error on stdout/stderr, or only in the log?

>
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 4274; 0 0 COMMENT EXTENSION 
> plpgsql
> pg_restore: [archiver (db)] could not execute query: ERROR:  must be owner of 
> extension plpgsql
> Command was: COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural 
> language';
>
>
>
> pg_restore: WARNING:  no privileges could be revoked for "public"
> pg_restore: WARNING:  no privileges could be revoked for "public"
> pg_restore: WARNING:  no privileges were granted for "public"
> pg_restore: WARNING:  no privileges were granted for "public"
> WARNING: errors ignored on restore: 1
>
> Do I need to worry, as this error is ignored ?

TL;DR no need to worry, can be ignored.

Details:

engine-backup has a specific set of errors it ignores.
You can search inside it for 'IGNORED_ERRORS' to see the list.

It _also_ logs the entire pg_restore output, just for reference.

(I also have a patch to log separately the list of errors not ignored:

https://gerrit.ovirt.org/86395

Need to find time to verify it, probably only in 4.3...)

This specific error happens due to the following:

PG by default creates new databases with the extension plpgsql.
This is good for us, as the engine needs it.
However, if you try to manually create this extension on some db,
you need admin permission for this - owning (e.g.) the db is not
enough.

When backing up the database, pg_dump dumps everything in it,
including commands to create this extension.

When engine-backup restores a database, it always uses only the
credentials of the engine db user, not postgres, thus (by default)
has no admin privs at this point. So this 'create' command fails,
and that's ok.

Best regards,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to connect to the graphic server

2018-02-17 Thread Yedidyah Bar David
On Fri, Feb 16, 2018 at 5:50 AM, Alex Bartonek  wrote:
>
>  Original Message 
>  On February 15, 2018 12:52 AM, Yedidyah Bar David  wrote:
>
>>On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek a...@unix1337.com wrote:
>>> Original Message 
>>> On February 14, 2018 2:23 AM, Yedidyah Bar David d...@redhat.com wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek a...@unix1337.com wrote:
>I've built and rebuilt about 4 oVirt servers.  Consider myself pretty good
> at this.  LOL.
> So I am setting up a oVirt server for a friend on his r710.  CentOS 7, 
> ovirt
> 4.2.   /etc/hosts has the correct IP and FQDN setup.
> When I build a VM and try to open a console session via  SPICE I am unable
> to connect to the graphic server.  I'm connecting from a Windows 10 box.
> Using virt-manager to connect.
>What happens when you try?
Unable to connect to the graphic console is what the error says.  Here is 
the .vv file other than the cert stuff in it:
>>>[virt-viewer]
>>> type=spice
>>> host=192.168.1.83
>>> port=-1
>>> password=
>>>Password is valid for 120 seconds.
>>>
>>>delete-this-file=1
>>> fullscreen=0
>>> title=Win_7_32bit:%d
>>> toggle-fullscreen=shift+f11
>>> release-cursor=shift+f12
>>> tls-port=5900
>>> enable-smartcard=0
>>> enable-usb-autoshare=1
>>> usb-filter=-1,-1,-1,-1,0
>>> tls-ciphers=DEFAULT
>>>host-subject=O=williams.com,CN=randb.williams.com
>>>Port 5900 is listening by IP on the server, so that looks correct.  I shut 
>>>the firewall off just in case it was the issue..no go.
>>>
>>
>> Did you verify that you can connect there manually (e.g. with telnet)?
>> Can you run a sniffer on both sides to make sure traffic passes correctly?
>> Can you check vdsm/libvirt logs on the host side?
>
>
> Ok.. I must have tanked it on install with the firewall.  The firewall is 
> blocking port 5900.  This is on CentOS 7.  If I flush the rules, it works.

Thanks for the report.

Did you choose to have firewall configured automatically, or did you
configure it yourself?

Best regards,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to add Hosts to Cluster

2018-02-17 Thread Mark Steele
Yaniv,

I have one of my developers assisting me and we are continuing to run into
issues. This is a note from him:

Hi, I'm trying to add a host to ovirt, but I'm running into package
dependency problems. I have existing hosts that are working and integrated
properly, and inspecting those, I am able to match the packages between the
new host and the existing, but when I then try to add the new host to
ovirt, it fails on reinstall because it's trying to install packages that
are later versions. does the installation run list from ovirt-release35
002-1 have unspecified versions? The working hosts use libvirt-1.1.1-29,
and vdsm-4.16.7, but it's trying to install vdsm-4.16.30, which requires a
higher version of libvirt, at which point, the installation fails. is there
some way I can specify which package versions the ovirt install procedure
uses? or better yet, skip the package management step entirely?


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue

On Sat, Feb 17, 2018 at 2:32 AM, Yaniv Kaul  wrote:

>
>
> On Fri, Feb 16, 2018 at 11:14 PM, Mark Steele  wrote:
>
>> We are using CentOS Linux release 7.0.1406 (Core) and  oVirt Engine
>> Version: 3.5.0.1-1.el6
>>
>
> You are seeing https://bugzilla.redhat.com/show_bug.cgi?id=126 ,
> which is a result of a default change of libvirt and was fixed in later
> versions of oVirt than the one you are using.
> See patch https://gerrit.ovirt.org/#/c/76934/ for how it was fixed, you
> can probably configure it manually.
> Y.
>
>
>>
>> We have four other hosts that are running this same configuration
>> already. I took one host out of the cluster (forcefully) that was working
>> and now it will not add back in either - throwing the same SASL error.
>>
>> We are looking at downgrading libvirt as I've seen that somewhere else -
>> is there another version of RH I should be trying? I have a host I can put
>> it on.
>>
>>
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> 
>> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
>> www.telvue.com
>> twitter: http://twitter.com/telvue | facebook: https://www.facebook
>> .com/telvue
>>
>> On Fri, Feb 16, 2018 at 3:31 PM, Yaniv Kaul  wrote:
>>
>>>
>>>
>>> On Feb 16, 2018 6:47 PM, "Mark Steele"  wrote:
>>>
>>> Hello all,
>>>
>>> We recently had a network event where we lost access to our storage for
>>> a period of time. The Cluster basically shut down all our VM's and in the
>>> process we had three HV's that went offline and would not communicate
>>> properly with the cluster.
>>>
>>> We have since completely reinstalled CentOS on the hosts and attempted
>>> to install them into the cluster with no joy. We've gotten to the point
>>> where we generally get an error message in the web gui:
>>>
>>>
>>> Which EL release and which oVirt release are you using? My guess would
>>> be latest EL, with an older oVirt?
>>> Y.
>>>
>>>
>>> Stage: Misc Configuration
>>> Host hv-ausa-02 installation failed. Command returned failure code 1
>>> during SSH session 'root@10.1.90.154'.
>>>
>>> the following is what we are seeing in the messages log:
>>>
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
>>> authentication failed: authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
>>> 15231: error : virNetSASLSessionListMechanisms:390 : internal error:
>>> cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
>>> Error -4 in server.c near line 1757)
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
>>> 15231: error : remoteDispatchAuthSaslInit:3411 : authentication failed:
>>> authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
>>> 15226: error : virNetSocketReadWire:1808 : End of file while reading data:
>>> Input/output error
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
>>> authentication failed: authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.962+:
>>> 15233: error : virNetSASLSessionListMechanisms:390 : internal error:
>>> cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
>>> Error -4 in server.c near line 1757)
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.963+:
>>> 15233: error : remoteDispatchAuthSaslInit:3411 : authentication failed:
>>> authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.963+:
>>> 15226: error : 

Re: [ovirt-users] VDSM SSL validity

2018-02-17 Thread Punaatua PAINT-KOUI
Any idea someone ?

Le 14 févr. 2018 23:19, "Punaatua PAINT-KOUI"  a
écrit :

> Hi,
>
> I setup an hyperconverged solution with 3 nodes, hosted engine on
> glusterfs.
> We run this setup in a PCI-DSS environment. According to PCI-DSS
> requirements, we are required to reduce the validity of any certificate
> under 39 months.
>
> I saw in this link https://www.ovirt.org/develop/release-management/
> features/infra/pki/ that i can use the option
> VdsCertificateValidityInYears at engine-config.
>
> I'm running ovirt engine 4.2.1 and i checked when i was on 4.2 how to edit
> the option with engine-config --all and engine-config --list but the option
> is not listed
>
> Am i missing something ?
>
> I thing i can regenerate a VDSM certificate with openssl and the CA conf
> in /etc/pki/ovirt-engine on the hosted-engine but i would rather modifiy
> the option for future host that I will add.
>
> --
> -
> PAINT-KOUI Punaatua
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to add Hosts to Cluster

2018-02-17 Thread Mark Steele
Thank you Alex.

I guess the first step is to get my existing hosts back into the cluster.
I'm going to try to manually apply the patch that Yaniv sent over to see if
I can get them back in.

Mark


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue

On Sat, Feb 17, 2018 at 7:20 AM, Alex K  wrote:

> For a proper upgrade there are specific steps that you follow for each
> host and the engine.
>
> I usually upgrade the hosts first then the engine. If you have spare
> resources so as to put hosts at maintenance then the upgrade should be
> seamless. Also i think you need to go strp by step: 3.5 -> 3.6 -> 4.0 ...
> etc
>
> In case you have a similar test setup you may try it first there.
>
>
>
> On Feb 17, 2018 14:10, "Mark Steele"  wrote:
>
>> Thank you very much!
>>
>> Question - is upgrading the ovirt installation a matter of just upgrading
>> the engine? Or are there changes that are pushed down to each host / vm?
>>
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> 
>> 800.885.8886 x128 <800%20885%208886> | mste...@telvue.com | http://
>> www.telvue.com
>> twitter: http://twitter.com/telvue | facebook: https://www.facebook
>> .com/telvue
>>
>> On Sat, Feb 17, 2018 at 2:32 AM, Yaniv Kaul  wrote:
>>
>>>
>>>
>>> On Fri, Feb 16, 2018 at 11:14 PM, Mark Steele 
>>> wrote:
>>>
 We are using CentOS Linux release 7.0.1406 (Core) and  oVirt Engine
 Version: 3.5.0.1-1.el6

>>>
>>> You are seeing https://bugzilla.redhat.com/show_bug.cgi?id=126 ,
>>> which is a result of a default change of libvirt and was fixed in later
>>> versions of oVirt than the one you are using.
>>> See patch https://gerrit.ovirt.org/#/c/76934/ for how it was fixed, you
>>> can probably configure it manually.
>>> Y.
>>>
>>>

 We have four other hosts that are running this same configuration
 already. I took one host out of the cluster (forcefully) that was working
 and now it will not add back in either - throwing the same SASL error.

 We are looking at downgrading libvirt as I've seen that somewhere else
 - is there another version of RH I should be trying? I have a host I can
 put it on.



 ***
 *Mark Steele*
 CIO / VP Technical Operations | TelVue Corporation
 TelVue - We Share Your Vision
 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
 
 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
 www.telvue.com
 twitter: http://twitter.com/telvue | facebook: https://www.facebook
 .com/telvue

 On Fri, Feb 16, 2018 at 3:31 PM, Yaniv Kaul  wrote:

>
>
> On Feb 16, 2018 6:47 PM, "Mark Steele"  wrote:
>
> Hello all,
>
> We recently had a network event where we lost access to our storage
> for a period of time. The Cluster basically shut down all our VM's and in
> the process we had three HV's that went offline and would not communicate
> properly with the cluster.
>
> We have since completely reinstalled CentOS on the hosts and attempted
> to install them into the cluster with no joy. We've gotten to the point
> where we generally get an error message in the web gui:
>
>
> Which EL release and which oVirt release are you using? My guess would
> be latest EL, with an older oVirt?
> Y.
>
>
> Stage: Misc Configuration
> Host hv-ausa-02 installation failed. Command returned failure code 1
> during SSH session 'root@10.1.90.154'.
>
> the following is what we are seeing in the messages log:
>
> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
> authentication failed: authentication failed
> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
> 15231: error : virNetSASLSessionListMechanisms:390 : internal error:
> cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
> Error -4 in server.c near line 1757)
> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
> 15231: error : remoteDispatchAuthSaslInit:3411 : authentication
> failed: authentication failed
> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
> 15226: error : virNetSocketReadWire:1808 : End of file while reading data:
> Input/output error
> Feb 16 11:39:53 hv-ausa-02 

Re: [ovirt-users] Unable to add Hosts to Cluster

2018-02-17 Thread Alex K
For a proper upgrade there are specific steps that you follow for each host
and the engine.

I usually upgrade the hosts first then the engine. If you have spare
resources so as to put hosts at maintenance then the upgrade should be
seamless. Also i think you need to go strp by step: 3.5 -> 3.6 -> 4.0 ...
etc

In case you have a similar test setup you may try it first there.



On Feb 17, 2018 14:10, "Mark Steele"  wrote:

> Thank you very much!
>
> Question - is upgrading the ovirt installation a matter of just upgrading
> the engine? Or are there changes that are pushed down to each host / vm?
>
>
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 800.885.8886 x128 <800%20885%208886> | mste...@telvue.com | http://
> www.telvue.com
> twitter: http://twitter.com/telvue | facebook: https://www.
> facebook.com/telvue
>
> On Sat, Feb 17, 2018 at 2:32 AM, Yaniv Kaul  wrote:
>
>>
>>
>> On Fri, Feb 16, 2018 at 11:14 PM, Mark Steele  wrote:
>>
>>> We are using CentOS Linux release 7.0.1406 (Core) and  oVirt Engine
>>> Version: 3.5.0.1-1.el6
>>>
>>
>> You are seeing https://bugzilla.redhat.com/show_bug.cgi?id=126 ,
>> which is a result of a default change of libvirt and was fixed in later
>> versions of oVirt than the one you are using.
>> See patch https://gerrit.ovirt.org/#/c/76934/ for how it was fixed, you
>> can probably configure it manually.
>> Y.
>>
>>
>>>
>>> We have four other hosts that are running this same configuration
>>> already. I took one host out of the cluster (forcefully) that was working
>>> and now it will not add back in either - throwing the same SASL error.
>>>
>>> We are looking at downgrading libvirt as I've seen that somewhere else -
>>> is there another version of RH I should be trying? I have a host I can put
>>> it on.
>>>
>>>
>>>
>>> ***
>>> *Mark Steele*
>>> CIO / VP Technical Operations | TelVue Corporation
>>> TelVue - We Share Your Vision
>>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>>> 
>>> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
>>> www.telvue.com
>>> twitter: http://twitter.com/telvue | facebook: https://www.facebook
>>> .com/telvue
>>>
>>> On Fri, Feb 16, 2018 at 3:31 PM, Yaniv Kaul  wrote:
>>>


 On Feb 16, 2018 6:47 PM, "Mark Steele"  wrote:

 Hello all,

 We recently had a network event where we lost access to our storage for
 a period of time. The Cluster basically shut down all our VM's and in the
 process we had three HV's that went offline and would not communicate
 properly with the cluster.

 We have since completely reinstalled CentOS on the hosts and attempted
 to install them into the cluster with no joy. We've gotten to the point
 where we generally get an error message in the web gui:


 Which EL release and which oVirt release are you using? My guess would
 be latest EL, with an older oVirt?
 Y.


 Stage: Misc Configuration
 Host hv-ausa-02 installation failed. Command returned failure code 1
 during SSH session 'root@10.1.90.154'.

 the following is what we are seeing in the messages log:

 Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
 authentication failed: authentication failed
 Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
 15231: error : virNetSASLSessionListMechanisms:390 : internal error:
 cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
 Error -4 in server.c near line 1757)
 Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
 15231: error : remoteDispatchAuthSaslInit:3411 : authentication
 failed: authentication failed
 Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
 15226: error : virNetSocketReadWire:1808 : End of file while reading data:
 Input/output error
 Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
 authentication failed: authentication failed
 Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.962+:
 15233: error : virNetSASLSessionListMechanisms:390 : internal error:
 cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
 Error -4 in server.c near line 1757)
 Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.963+:
 15233: error : remoteDispatchAuthSaslInit:3411 : authentication
 failed: authentication failed
 Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.963+:
 15226: error : virNetSocketReadWire:1808 : End of file while reading data:
 Input/output error
 Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
 

Re: [ovirt-users] Unable to add Hosts to Cluster

2018-02-17 Thread Mark Steele
Thank you very much!

Question - is upgrading the ovirt installation a matter of just upgrading
the engine? Or are there changes that are pushed down to each host / vm?


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue

On Sat, Feb 17, 2018 at 2:32 AM, Yaniv Kaul  wrote:

>
>
> On Fri, Feb 16, 2018 at 11:14 PM, Mark Steele  wrote:
>
>> We are using CentOS Linux release 7.0.1406 (Core) and  oVirt Engine
>> Version: 3.5.0.1-1.el6
>>
>
> You are seeing https://bugzilla.redhat.com/show_bug.cgi?id=126 ,
> which is a result of a default change of libvirt and was fixed in later
> versions of oVirt than the one you are using.
> See patch https://gerrit.ovirt.org/#/c/76934/ for how it was fixed, you
> can probably configure it manually.
> Y.
>
>
>>
>> We have four other hosts that are running this same configuration
>> already. I took one host out of the cluster (forcefully) that was working
>> and now it will not add back in either - throwing the same SASL error.
>>
>> We are looking at downgrading libvirt as I've seen that somewhere else -
>> is there another version of RH I should be trying? I have a host I can put
>> it on.
>>
>>
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> 
>> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
>> www.telvue.com
>> twitter: http://twitter.com/telvue | facebook: https://www.facebook
>> .com/telvue
>>
>> On Fri, Feb 16, 2018 at 3:31 PM, Yaniv Kaul  wrote:
>>
>>>
>>>
>>> On Feb 16, 2018 6:47 PM, "Mark Steele"  wrote:
>>>
>>> Hello all,
>>>
>>> We recently had a network event where we lost access to our storage for
>>> a period of time. The Cluster basically shut down all our VM's and in the
>>> process we had three HV's that went offline and would not communicate
>>> properly with the cluster.
>>>
>>> We have since completely reinstalled CentOS on the hosts and attempted
>>> to install them into the cluster with no joy. We've gotten to the point
>>> where we generally get an error message in the web gui:
>>>
>>>
>>> Which EL release and which oVirt release are you using? My guess would
>>> be latest EL, with an older oVirt?
>>> Y.
>>>
>>>
>>> Stage: Misc Configuration
>>> Host hv-ausa-02 installation failed. Command returned failure code 1
>>> during SSH session 'root@10.1.90.154'.
>>>
>>> the following is what we are seeing in the messages log:
>>>
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
>>> authentication failed: authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
>>> 15231: error : virNetSASLSessionListMechanisms:390 : internal error:
>>> cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
>>> Error -4 in server.c near line 1757)
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
>>> 15231: error : remoteDispatchAuthSaslInit:3411 : authentication failed:
>>> authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.761+:
>>> 15226: error : virNetSocketReadWire:1808 : End of file while reading data:
>>> Input/output error
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
>>> authentication failed: authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.962+:
>>> 15233: error : virNetSASLSessionListMechanisms:390 : internal error:
>>> cannot list SASL mechanisms -4 (SASL(-4): no mechanism available: Internal
>>> Error -4 in server.c near line 1757)
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.963+:
>>> 15233: error : remoteDispatchAuthSaslInit:3411 : authentication failed:
>>> authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 libvirtd: 2018-02-16 16:39:53.963+:
>>> 15226: error : virNetSocketReadWire:1808 : End of file while reading data:
>>> Input/output error
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: libvirt: XML-RPC error :
>>> authentication failed: authentication failed
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: Traceback (most recent call last):
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: File "/usr/bin/vdsm-tool", line
>>> 219, in main
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: return
>>> tool_command[cmd]["command"](*args)
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: File "/usr/lib/python2.7/site-packa
>>> ges/vdsm/tool/upgrade_300_networks.py", line 83, in upgrade_networks
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: networks = netinfo.networks()
>>> Feb 16 11:39:53 hv-ausa-02 vdsm-tool: File 
>>>