[ovirt-users] Re: upgrade from 4.38 to 4.39
On March 14, 2020 1:10:06 PM GMT+02:00, eev...@digitaldatatechs.com wrote: >It worked with the password. >I recopied the authorized keys and ssh keys from engine host to it and >copied it's keys back. >What do I need to look at to prevent this in the future? > >Eric Evans >Digital Data Services LLC. >304.660.9080 > > >-Original Message- >From: Strahil Nikolov >Sent: Saturday, March 14, 2020 5:24 AM >To: users@ovirt.org; eev...@digitaldatatechs.com >Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39 > >On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com >wrote: >>This is from the secure log, /var/log/secure >> >>Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from >>192.168.254.240 port 39668 ssh2: RSA >>SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY >>Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session >>opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: >>Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 >>19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user >>root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: >pam_unix(sudo:session): >>session closed for user root Mar 13 19:24:24 kvm01 sudo: >>pam_unix(sudo:session): session opened for user root by root(uid=0) >Mar >>13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for >user >>root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by >>192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: >>pam_unix(sudo:session): session opened for user root by root(uid=0) >Mar >>13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for >user >>root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session >opened >>for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: >>pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 >>kvm01 cockpit-session: pam_unix(cockpit:session): >>session closed for user root >>Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by >192.168.254.240 >>port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection >>closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 >>sudo: pam_unix(sudo:session): session opened for user root by (uid=0) >>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for > >>user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session >>opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: >>pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 >>kvm01 sudo: pam_unix(sudo:session): session opened for user root by >>(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session >>closed for user root Mar 13 19:32:34 kvm01 sudo: >>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >>19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user >>root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session >opened >>for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: >>pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 >>kvm01 sudo: pam_unix(sudo:session): session opened for user root by >>(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session >>closed for user root Mar 13 19:32:35 kvm01 sudo: >>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >>19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user >>root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session >opened >>for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: >>pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 >>kvm01 sudo: pam_unix(sudo:session): session opened for user root by >>(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session >>closed for user root Mar 13 19:32:36 kvm01 sudo: >>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >>19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user >>root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session >opened >>for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: >>pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 >>kvm01 sudo: pam_unix(sudo:session): session opened for user root by >>(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session >>closed for user root Mar 13 19:32:39 kvm01 sudo: >>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >>19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user >>root Mar 13 19:32:39 kvm01 sudo:
[ovirt-users] Re: upgrade from 4.38 to 4.39
I recopied the authorized keys from the engine host, did restorecon -RFv /root, and chmod 644 on .ssh. I’ll try it again. Eric Evans Digital Data Services LLC. 304.660.9080 From: Maton, Brett Sent: Saturday, March 14, 2020 7:44 AM To: eev...@digitaldatatechs.com Cc: Strahil Nikolov ; Ovirt Users Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39 I think all you need on the inaccessible host is /root/.ssh/authorized_keys copied from a working host (with the same ownership, permissions and SELinux context) On Sat, 14 Mar 2020 at 11:15, mailto:eev...@digitaldatatechs.com> > wrote: It worked with the password. I recopied the authorized keys and ssh keys from engine host to it and copied it's keys back. What do I need to look at to prevent this in the future? Eric Evans Digital Data Services LLC. 304.660.9080 -Original Message- From: Strahil Nikolov mailto:hunter86...@yahoo.com> > Sent: Saturday, March 14, 2020 5:24 AM To: users@ovirt.org <mailto:users@ovirt.org> ; eev...@digitaldatatechs.com <mailto:eev...@digitaldatatechs.com> Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39 On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com <mailto:eev...@digitaldatatechs.com> wrote: >This is from the secure log, /var/log/secure > >Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from >192.168.254.240 port 39668 ssh2: RSA >SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY >Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session >opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: >Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 >19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user >root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): >session closed for user root Mar 13 19:24:24 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar >13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by >192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar >13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 >kvm01 cockpit-session: pam_unix(cockpit:session): >session closed for user root >Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 >port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection >closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 >sudo: pam_unix(sudo:session): session opened for user root by (uid=0) >Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for >user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session >opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:34 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:35 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:36 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 >kvm01 sudo: pam_unix(sudo:session): session open
[ovirt-users] Re: upgrade from 4.38 to 4.39
I think all you need on the inaccessible host is /root/.ssh/authorized_keys copied from a working host (with the same ownership, permissions and SELinux context) On Sat, 14 Mar 2020 at 11:15, wrote: > It worked with the password. > I recopied the authorized keys and ssh keys from engine host to it and > copied it's keys back. > What do I need to look at to prevent this in the future? > > Eric Evans > Digital Data Services LLC. > 304.660.9080 > > > -Original Message- > From: Strahil Nikolov > Sent: Saturday, March 14, 2020 5:24 AM > To: users@ovirt.org; eev...@digitaldatatechs.com > Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39 > > On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com wrote: > >This is from the secure log, /var/log/secure > > > >Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from > >192.168.254.240 port 39668 ssh2: RSA > >SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY > >Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session > >opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: > >Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 > >19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user > >root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): > >session closed for user root Mar 13 19:24:24 kvm01 sudo: > >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar > >13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user > >root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by > >192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: > >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar > >13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user > >root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened > >for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: > >pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 > >kvm01 cockpit-session: pam_unix(cockpit:session): > >session closed for user root > >Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 > >port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection > >closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 > >sudo: pam_unix(sudo:session): session opened for user root by (uid=0) > >Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for > >user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session > >opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: > >pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 > >kvm01 sudo: pam_unix(sudo:session): session opened for user root by > >(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session > >closed for user root Mar 13 19:32:34 kvm01 sudo: > >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user > >root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened > >for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: > >pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 > >kvm01 sudo: pam_unix(sudo:session): session opened for user root by > >(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session > >closed for user root Mar 13 19:32:35 kvm01 sudo: > >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user > >root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened > >for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: > >pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 > >kvm01 sudo: pam_unix(sudo:session): session opened for user root by > >(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session > >closed for user root Mar 13 19:32:36 kvm01 sudo: > >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user > >root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened > >for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: > >pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 > >kvm01 sudo: pam_unix(sudo:session): session opened for user root by > >(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session > >closed for user root Mar 13 19:32:39 kvm01 sudo: > >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 > >19:32:39 kvm01 sudo: pam_unix(su
[ovirt-users] Re: upgrade from 4.38 to 4.39
It worked with the password. I recopied the authorized keys and ssh keys from engine host to it and copied it's keys back. What do I need to look at to prevent this in the future? Eric Evans Digital Data Services LLC. 304.660.9080 -Original Message- From: Strahil Nikolov Sent: Saturday, March 14, 2020 5:24 AM To: users@ovirt.org; eev...@digitaldatatechs.com Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39 On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com wrote: >This is from the secure log, /var/log/secure > >Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from >192.168.254.240 port 39668 ssh2: RSA >SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY >Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session >opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: >Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 >19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user >root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): >session closed for user root Mar 13 19:24:24 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar >13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by >192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar >13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 >kvm01 cockpit-session: pam_unix(cockpit:session): >session closed for user root >Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 >port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection >closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 >sudo: pam_unix(sudo:session): session opened for user root by (uid=0) >Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for >user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session >opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:34 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:35 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:36 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:39 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 >19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user >root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened >for user root by (uid=0) Mar 13 19:32:39 kvm01 sudo: >pam_unix(sudo:session): session closed for user root Mar 13 19:32:39 >kvm01 sudo: pam_unix(sudo:session): session opened for user root by >(uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session >closed for user root Mar 13 19:32:40 kvm01 sudo: >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
[ovirt-users] Re: upgrade from 4.38 to 4.39
I dd a autorelabel and checked to make sure they were 644. Eric Evans Digital Data Services LLC. 304.660.9080 From: Maton, Brett Sent: Saturday, March 14, 2020 5:35 AM To: eev...@digitaldatatechs.com Cc: Strahil Nikolov ; Ovirt Users Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39 Have you checked the file permissions and SELinux context of the SSH keys you copied to kvm01 ? On Fri, 13 Mar 2020 at 23:39, mailto:eev...@digitaldatatechs.com> > wrote: This is from the secure log, /var/log/secure Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from 192.168.254.240 port 39668 ssh2: RSA SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 kvm01 cockpit-session: pam_unix(cockpit:session): session closed for user root Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user root Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session
[ovirt-users] Re: upgrade from 4.38 to 4.39
: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
>
> Maybe an issuewith sudo? It should be installing as root, right?
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: eev...@digitaldatatechs.com
> Sent: Friday, March 13, 2020 2:10 PM
> To: 'Strahil Nikolov' ; 'users@ovirt.org' <
> users@ovirt.org>
> Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
> When I try the reinstall it fails with this in events on the web interface:
>
> Host kvm01 installation failed. SSH authentication to '
> r...@kvm01.digitaldatatechs.com' failed. Please verify provided
> credentials. Make sure key is authorized at host.
>
> I can ssh into the host from the engine host with no password and no
> problem.
> I will dig deeper until I hear from you.
> Thanks.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: eev...@digitaldatatechs.com
> Sent: Friday, March 13, 2020 1:15 PM
> To: 'Strahil Nikolov' ; 'users@ovirt.org' <
> users@ovirt.org>
> Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
> I'll try that and let you know.
> Thank you.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Strahil Nikolov
> Sent: Friday, March 13, 2020 12:54 AM
> To: eev...@digitaldatatechs.com; users@ovirt.org
> Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
> On March 10, 2020 5:33:18 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
> >
> >
> >Since the upgrade, for some reason I get this message when checking for
> >upgrade on one host:
> >
> >Failed to check for available updates on host kvm01 with message
> >'Failed to run check-update of host 'kvm01.digitaldatatechs.com'.
> >Error: fatal:
> >[kvm01.digitaldatatechs.com]: FAILED! => {"changed": false, "msg":
> >"Failed
> >to connect to the host via ssh: Permission denied
> >(publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable":
> >true}
> >
> >
> >
> >I can ssh into the server from the ovirt server and re-copied the ssh
> >keys and authorized keys but the problem persists.
> >
> >I am still unable to manually migrate but auto load balance seems to be
> >working again.
> >
> >
> >
> >I am attaching the engine log for your review.
> >
> >
> >
> >Thank you so much for your help.
> >
> >
> >
> >Eric Evans
> >
> >Digital Data Services LLC.
> >
> >304.660.9080
> >
> >
> >
> >
>
> Hi Eric,
>
> Can you try the following:
> 1. Set the node in maintenance
> 2. From the Hosts section -> Installation -> Reinstall 3. Fill in if the
> host is hosting the HostedEngine and the rest of the wizard 4. Start the
> install 5. If it succeeds -> remove the maintenance
>
> Best Regards,
> Strahil Nikolov
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/DXHNAGGS4PIDSF5HEJN3LJMBKNWX3PNU/
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/AZETVUP4O7PXJVM6Y4A64LQN444HAI37/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CQQT6OMWH2JSYOKY25BA5IXDVPLL4HUT/
[ovirt-users] Re: upgrade from 4.38 to 4.39
gt;Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>
>Maybe an issuewith sudo? It should be installing as root, right?
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-
>From: eev...@digitaldatatechs.com
>Sent: Friday, March 13, 2020 2:10 PM
>To: 'Strahil Nikolov' ; 'users@ovirt.org'
>
>Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
>When I try the reinstall it fails with this in events on the web
>interface:
>
>Host kvm01 installation failed. SSH authentication to
>'r...@kvm01.digitaldatatechs.com' failed. Please verify provided
>credentials. Make sure key is authorized at host.
>
>I can ssh into the host from the engine host with no password and no
>problem.
>I will dig deeper until I hear from you.
>Thanks.
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-----
>From: eev...@digitaldatatechs.com
>Sent: Friday, March 13, 2020 1:15 PM
>To: 'Strahil Nikolov' ; 'users@ovirt.org'
>
>Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
>I'll try that and let you know.
>Thank you.
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-
>From: Strahil Nikolov
>Sent: Friday, March 13, 2020 12:54 AM
>To: eev...@digitaldatatechs.com; users@ovirt.org
>Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
>On March 10, 2020 5:33:18 PM GMT+02:00, eev...@digitaldatatechs.com
>wrote:
>>
>>
>>Since the upgrade, for some reason I get this message when checking
>for
>>upgrade on one host:
>>
>>Failed to check for available updates on host kvm01 with message
>>'Failed to run check-update of host 'kvm01.digitaldatatechs.com'.
>>Error: fatal:
>>[kvm01.digitaldatatechs.com]: FAILED! => {"changed": false, "msg":
>>"Failed
>>to connect to the host via ssh: Permission denied
>>(publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable":
>>true}
>>
>>
>>
>>I can ssh into the server from the ovirt server and re-copied the ssh
>>keys and authorized keys but the problem persists.
>>
>>I am still unable to manually migrate but auto load balance seems to
>be
>>working again.
>>
>>
>>
>>I am attaching the engine log for your review.
>>
>>
>>
>>Thank you so much for your help.
>>
>>
>>
>>Eric Evans
>>
>>Digital Data Services LLC.
>>
>>304.660.9080
>>
>>
>>
>>
>
>Hi Eric,
>
>Can you try the following:
>1. Set the node in maintenance
>2. From the Hosts section -> Installation -> Reinstall 3. Fill in if
>the host is hosting the HostedEngine and the rest of the wizard 4.
>Start the install 5. If it succeeds -> remove the maintenance
>
>Best Regards,
>Strahil Nikolov
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@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/DXHNAGGS4PIDSF5HEJN3LJMBKNWX3PNU/
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@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/AZETVUP4O7PXJVM6Y4A64LQN444HAI37/
Try reinstalling by providing the root user's password.
Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VSF5T3EF3Q6RBTBDHXSZUCM27DUUT5CH/
[ovirt-users] Re: upgrade from 4.38 to 4.39
: pam_unix(sudo:session): session opened for user
root by (uid=0)
Mar 13 19:32:41 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Maybe an issuewith sudo? It should be installing as root, right?
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: eev...@digitaldatatechs.com
Sent: Friday, March 13, 2020 2:10 PM
To: 'Strahil Nikolov' ; 'users@ovirt.org'
Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
When I try the reinstall it fails with this in events on the web interface:
Host kvm01 installation failed. SSH authentication to
'r...@kvm01.digitaldatatechs.com' failed. Please verify provided credentials.
Make sure key is authorized at host.
I can ssh into the host from the engine host with no password and no problem.
I will dig deeper until I hear from you.
Thanks.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: eev...@digitaldatatechs.com
Sent: Friday, March 13, 2020 1:15 PM
To: 'Strahil Nikolov' ; 'users@ovirt.org'
Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
I'll try that and let you know.
Thank you.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: Strahil Nikolov
Sent: Friday, March 13, 2020 12:54 AM
To: eev...@digitaldatatechs.com; users@ovirt.org
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
On March 10, 2020 5:33:18 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>
>
>Since the upgrade, for some reason I get this message when checking for
>upgrade on one host:
>
>Failed to check for available updates on host kvm01 with message
>'Failed to run check-update of host 'kvm01.digitaldatatechs.com'.
>Error: fatal:
>[kvm01.digitaldatatechs.com]: FAILED! => {"changed": false, "msg":
>"Failed
>to connect to the host via ssh: Permission denied
>(publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable":
>true}
>
>
>
>I can ssh into the server from the ovirt server and re-copied the ssh
>keys and authorized keys but the problem persists.
>
>I am still unable to manually migrate but auto load balance seems to be
>working again.
>
>
>
>I am attaching the engine log for your review.
>
>
>
>Thank you so much for your help.
>
>
>
>Eric Evans
>
>Digital Data Services LLC.
>
>304.660.9080
>
>
>
>
Hi Eric,
Can you try the following:
1. Set the node in maintenance
2. From the Hosts section -> Installation -> Reinstall 3. Fill in if the host
is hosting the HostedEngine and the rest of the wizard 4. Start the install
5. If it succeeds -> remove the maintenance
Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DXHNAGGS4PIDSF5HEJN3LJMBKNWX3PNU/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/AZETVUP4O7PXJVM6Y4A64LQN444HAI37/
[ovirt-users] Re: upgrade from 4.38 to 4.39
When I try the reinstall it fails with this in events on the web interface:
Host kvm01 installation failed. SSH authentication to
'r...@kvm01.digitaldatatechs.com' failed. Please verify provided credentials.
Make sure key is authorized at host.
I can ssh into the host from the engine host with no password and no problem.
I will dig deeper until I hear from you.
Thanks.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: eev...@digitaldatatechs.com
Sent: Friday, March 13, 2020 1:15 PM
To: 'Strahil Nikolov' ; 'users@ovirt.org'
Subject: RE: [ovirt-users] Re: upgrade from 4.38 to 4.39
I'll try that and let you know.
Thank you.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: Strahil Nikolov
Sent: Friday, March 13, 2020 12:54 AM
To: eev...@digitaldatatechs.com; users@ovirt.org
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
On March 10, 2020 5:33:18 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>
>
>Since the upgrade, for some reason I get this message when checking for
>upgrade on one host:
>
>Failed to check for available updates on host kvm01 with message
>'Failed to run check-update of host 'kvm01.digitaldatatechs.com'.
>Error: fatal:
>[kvm01.digitaldatatechs.com]: FAILED! => {"changed": false, "msg":
>"Failed
>to connect to the host via ssh: Permission denied
>(publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable":
>true}
>
>
>
>I can ssh into the server from the ovirt server and re-copied the ssh
>keys and authorized keys but the problem persists.
>
>I am still unable to manually migrate but auto load balance seems to be
>working again.
>
>
>
>I am attaching the engine log for your review.
>
>
>
>Thank you so much for your help.
>
>
>
>Eric Evans
>
>Digital Data Services LLC.
>
>304.660.9080
>
>
>
>
Hi Eric,
Can you try the following:
1. Set the node in maintenance
2. From the Hosts section -> Installation -> Reinstall 3. Fill in if the host
is hosting the HostedEngine and the rest of the wizard 4. Start the install
5. If it succeeds -> remove the maintenance
Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DXHNAGGS4PIDSF5HEJN3LJMBKNWX3PNU/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IOUSCGCB3AHXYWZAFX7TQDE7DM43WZYF/
[ovirt-users] Re: upgrade from 4.38 to 4.39
I'll try that and let you know.
Thank you.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: Strahil Nikolov
Sent: Friday, March 13, 2020 12:54 AM
To: eev...@digitaldatatechs.com; users@ovirt.org
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
On March 10, 2020 5:33:18 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>
>
>Since the upgrade, for some reason I get this message when checking for
>upgrade on one host:
>
>Failed to check for available updates on host kvm01 with message
>'Failed to run check-update of host 'kvm01.digitaldatatechs.com'.
>Error: fatal:
>[kvm01.digitaldatatechs.com]: FAILED! => {"changed": false, "msg":
>"Failed
>to connect to the host via ssh: Permission denied
>(publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable":
>true}
>
>
>
>I can ssh into the server from the ovirt server and re-copied the ssh
>keys and authorized keys but the problem persists.
>
>I am still unable to manually migrate but auto load balance seems to be
>working again.
>
>
>
>I am attaching the engine log for your review.
>
>
>
>Thank you so much for your help.
>
>
>
>Eric Evans
>
>Digital Data Services LLC.
>
>304.660.9080
>
>
>
>
Hi Eric,
Can you try the following:
1. Set the node in maintenance
2. From the Hosts section -> Installation -> Reinstall 3. Fill in if the host
is hosting the HostedEngine and the rest of the wizard 4. Start the install
5. If it succeeds -> remove the maintenance
Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DXHNAGGS4PIDSF5HEJN3LJMBKNWX3PNU/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/L2ACM6KIJSI6GJXPOZY7MTOYHH54YYCU/
[ovirt-users] Re: upgrade from 4.38 to 4.39
On March 10, 2020 5:33:18 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>
>
>Since the upgrade, for some reason I get this message when checking for
>upgrade on one host:
>
>Failed to check for available updates on host kvm01 with message
>'Failed to
>run check-update of host 'kvm01.digitaldatatechs.com'. Error: fatal:
>[kvm01.digitaldatatechs.com]: FAILED! => {"changed": false, "msg":
>"Failed
>to connect to the host via ssh: Permission denied
>(publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable":
>true}
>
>
>
>I can ssh into the server from the ovirt server and re-copied the ssh
>keys
>and authorized keys but the problem persists.
>
>I am still unable to manually migrate but auto load balance seems to be
>working again.
>
>
>
>I am attaching the engine log for your review.
>
>
>
>Thank you so much for your help.
>
>
>
>Eric Evans
>
>Digital Data Services LLC.
>
>304.660.9080
>
>
>
>
Hi Eric,
Can you try the following:
1. Set the node in maintenance
2. From the Hosts section -> Installation -> Reinstall
3. Fill in if the host is hosting the HostedEngine and the rest of the wizard
4. Start the install
5. If it succeeds -> remove the maintenance
Best Regards,
Strahil Nikolov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DXHNAGGS4PIDSF5HEJN3LJMBKNWX3PNU/
[ovirt-users] Re: upgrade from 4.38 to 4.39
On Sat, Mar 7, 2020 at 11:19 PM Strahil Nikolov wrote: > > On March 7, 2020 10:11:13 PM GMT+02:00, eev...@digitaldatatechs.com wrote: > >The upgrade went successfully, however I have lost the ability to > >migrate vm's manually. > >The engine log: > >2020-03-07 15:05:32,826-05 INFO > >[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] > >(EE-ManagedThreadFactory-engineScheduled-Thread-58) [] Fetched 0 VMs > >from VDS '3e4e1779-045d-4cee-be45-99a80471a1e4' > >2020-03-07 15:05:59,675-05 WARN > >[org.ovirt.engine.core.bll.SearchQuery] (default task-5) > >[f2f9faa4-41ac-475b-ad57-cb17792d4c77] > >ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : > >id='' > >2020-03-07 15:07:31,640-05 WARN > >[org.ovirt.engine.core.bll.SearchQuery] (default task-5) > >[edce2f10-d670-4e7e-a69a-937d91882146] > >ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : > >id='' > >If I put a host into maintenance the vm's migrate automatically.But > >manual migration is broken for some reason. > >Any ideas? Are you sure that above is all you get in engine.log when trying to migrate? Please try again and check/share engine.log over all the relevant time interval. > >___ > >Users mailing list -- users@ovirt.org > >To unsubscribe send an email to users-le...@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/KKWY5FAL2FZRU2NRYJ5LP4N3PMYR36AQ/ > > Check the libvirt log. > Sometimes it gives more clues: > > /var/log/libvirt/qemu/.log > > Also, check if it can be done via the API. > If API works, core functionality is OK and only UI is affected. > > Best Regards, > Strahil Nikolov > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/SW6X2EBB5RLCRLQW3QYGYHTDAPVS3F6D/ -- Didi ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/SQN5JANNPL2JKDTPSGN7B3SGEGN67QKH/
[ovirt-users] Re: upgrade from 4.38 to 4.39
On March 7, 2020 10:11:13 PM GMT+02:00, eev...@digitaldatatechs.com wrote: >The upgrade went successfully, however I have lost the ability to >migrate vm's manually. >The engine log: >2020-03-07 15:05:32,826-05 INFO >[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] >(EE-ManagedThreadFactory-engineScheduled-Thread-58) [] Fetched 0 VMs >from VDS '3e4e1779-045d-4cee-be45-99a80471a1e4' >2020-03-07 15:05:59,675-05 WARN >[org.ovirt.engine.core.bll.SearchQuery] (default task-5) >[f2f9faa4-41ac-475b-ad57-cb17792d4c77] >ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : >id='' >2020-03-07 15:07:31,640-05 WARN >[org.ovirt.engine.core.bll.SearchQuery] (default task-5) >[edce2f10-d670-4e7e-a69a-937d91882146] >ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : >id='' >If I put a host into maintenance the vm's migrate automatically.But >manual migration is broken for some reason. >Any ideas? >___ >Users mailing list -- users@ovirt.org >To unsubscribe send an email to users-le...@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/KKWY5FAL2FZRU2NRYJ5LP4N3PMYR36AQ/ Check the libvirt log. Sometimes it gives more clues: /var/log/libvirt/qemu/.log Also, check if it can be done via the API. If API works, core functionality is OK and only UI is affected. Best Regards, Strahil Nikolov ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/SW6X2EBB5RLCRLQW3QYGYHTDAPVS3F6D/
[ovirt-users] Re: upgrade from 4.38 to 4.39
The upgrade went successfully, however I have lost the ability to migrate vm's manually. The engine log: 2020-03-07 15:05:32,826-05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [] Fetched 0 VMs from VDS '3e4e1779-045d-4cee-be45-99a80471a1e4' 2020-03-07 15:05:59,675-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [f2f9faa4-41ac-475b-ad57-cb17792d4c77] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' 2020-03-07 15:07:31,640-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [edce2f10-d670-4e7e-a69a-937d91882146] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' If I put a host into maintenance the vm's migrate automatically.But manual migration is broken for some reason. Any ideas? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/KKWY5FAL2FZRU2NRYJ5LP4N3PMYR36AQ/
[ovirt-users] Re: upgrade from 4.38 to 4.39
On March 7, 2020 6:07:51 PM GMT+02:00, eev...@digitaldatatechs.com wrote: >I read documentation on upgrade procedures for minor upgrades. >Before I begin, I wanted to know of any issues or special procedures I >need to follow. >Please advise. >I appreciate any advice or guidance. >Thank you. >Eric >___ >Users mailing list -- users@ovirt.org >To unsubscribe send an email to users-le...@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/B2VX4OMNQCJV6HIZ7SK32NVLCMWFUDCK/ Hi Eric, If you use gluster for your HostedEngine's storage domain (and you didn't add any VMs there) - shutdown the VM and make a snapshot before the patch ... Just in case. Patch the engine , then the hosts. If you have intel-based cpu hosts, you might hit some spectre fixes. Once a node is patched do basic test (at least) - stop a VM, start a VM, make a snapshot, delete the snapshot, live migration... Something like that. If it's OK, you can procceed with the next node and repeat. Best Regards, Strahil Nikolov ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/KGSJA6DSL7UBRDCNVUVYXTXMVVAHE7OB/
