[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

I fixed the permission error with btmp but it made no difference. ___ 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:

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

Thanks everyone for the troubleshooting so far. I agree that the cockpit auth file is the same as 4.4.5. The timestamps are before the upgrade too. I get the same errors in the secure log. I found an error messages, looking at it now. secure log May 18 21:50:57 unix_chkpwd[529704]:

[ovirt-users] Re: Unable start self hosted engine after accidental shut down

I connected to the hypervisor, and run the hosted engine from there successfully. However the node status is still bad. I've set back the maintenance mode to none, but it's still showing that the cluster is in global maintenance mode. Furthermore it seems like the the system is having a disk

[ovirt-users] Re: Unable start self hosted engine after accidental shut down

But the score is 3400. The engine Image should be ok. Is the engine volume mounted and available as brick? gluster volume status engine Br Marcel Am 18. Mai 2021 23:37:38 MESZ schrieb Edward Berger : >With all the other VMs paused, I would guess all the VM disk image >storage >is offline or

[ovirt-users] Re: Unable start self hosted engine after accidental shut down

With all the other VMs paused, I would guess all the VM disk image storage is offline or unreachable from the hypervisor. login to this hypervisor host. df -kh to see whats mounted check the fileserving from hosts there. On Tue, May 18, 2021 at 4:33 PM Eugène Ngontang wrote: > Hi, > > Our

[ovirt-users] Re: Gluster volumes not healing (perhaps after host maintenance?)

Hi David, just spotted this post from a couple of weeks ago -- I have the same problem (Gluster volume not healing) since the upgrade from 7.x to 8.4. Same exact errors on glustershd.log -- and same errors if I try to heal manually. Typically I can get the volume healed by killing the specific

[ovirt-users] Unable start self hosted engine after accidental shut down

Hi, Our self hosted engine has been accidentally shut down by a teammate and now I'm trying hard to get it back up without success. I've tried the --vm-start command but it says the VM is in WaitForLaunch status. I've set the global maintenance mode but it does nothing. root@milhouse-main ~]#

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

Gianluca, I hope I my frustration didn't come across too strong - I apologize if so. I certainly now understand your posting of 4.4.5 as a diff source against 4.4.6 - thanks! - regards - Glenn ___ Users mailing list -- users@ovirt.org To unsubscribe

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

I swapped out the /etc/authselect login and system files and It seems to be that the updated node 4.6 pam stack is calling /usr/sbin/chkpwd and that fails for all cockpit users, root and otherwise. for root May 18 13:03:02 br014 unix_chkpwd[14186]: check pass; user unknown May 18 13:03:02 br014

[ovirt-users] Re: Gluster Geo-Replication Fails

Now to make it perfect , leave it running and analyze the AVCs with semanage. In the end SELINUX will remain working and geo-rep should be running also. I've previously tried the rpm generated from  https://github.com/gluster/glusterfs-selinux but it didn't help at that time. If possible, give

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

/etc/pam.d/cockpit under node 4.4.6 is the same as you posted. Something else changed. #%PAM-1.0 # this MUST be first in the "auth" stack as it sets PAM_USER # user_unknown is definitive, so die instead of ignore to avoid subsequent modules mess up the error code -auth [success=done

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

On Tue, May 18, 2021 at 4:50 PM Glenn Farmer wrote: > The current thread is about 4.4.6 - nice that you can login to your 4.4.5. > The subject of the thread says it all... ;-) My point was to ask if you see differences in /etc/pam.d/cockpit in your 4.4.6, in respect with the version I pasted

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

I see the same thing on a test cluster. I presumed it was due to using sssd and kerberos for local user logins. Here's an example of what gets written to /var/log/secure when root login to cockpit fails. May 18 11:29:07 br014 unix_chkpwd[26429]: check pass; user unknown May 18 11:29:07 br014

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

The current thread is about 4.4.6 - nice that you can login to your 4.4.5. I changed the admin password on the engine - still cannot access the Cockpit GUI on any of my hosts. Do I have to reboot them? Restart Cockpit - tried that - failed. Cannot access Cockpit on all hosts in a cluster

[ovirt-users] Re: oVirt deploy new HE Host problem

Hi Yedidyah, This feels like we are both just repeating ourselves. I have been mentioning from beginning that this is on latest 4.3. I understand oVirt dream team cannot support all versions, but as I already mentioned I have big production platform that I cannot just upgrade overnight. This

[ovirt-users] Re: oVirt deploy new HE Host problem

On Mon, May 17, 2021 at 10:34 AM Marko Vrgotic wrote: > > Hi gentleman, > > > > Hope you had a great weekend. > > Can I assume that you will be able to look into log files this week ? > > > > As per Yedidyah’s comment, I stopped troubleshooting . > > > > Kindly awaiting your reply. Hi Marko,

[ovirt-users] Re: Gluster Geo-Replication Fails

Perfect, worked a treat - thanks Strahil  From: Strahil Nikolov Sent: Tuesday 18 May 2021 04:10 To: Simon Scott ; users@ovirt.org Subject: Re: [ovirt-users] Re: Gluster Geo-Replication Fails If you are running on EL8 -> It's the SELINUX. To verify that, stop

[ovirt-users] Re: poweroff and reboot with ovirt_vm ansible module

Thank you very much for the clear help! ___ 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:

[ovirt-users] Re: Problems provisioning 4.4.6 hosted engine

On Thu, May 13, 2021 at 3:34 PM Sketch wrote: > > This is a new system is CentOS 8.3, with the oVirt-4.4 repo and all > updates applied. When I try to install the hosted engine with my engine > backup from 4.3.10, the installation fails with a too many open files > error. My 8.3 hosts already

[ovirt-users] [ANN] Async release for oVirt 4.4.6

oVirt 4.4.6 Async update #3 On May 18th 2021 the oVirt project released an async update to the following packages: - Vdsm 4.40.60.7 - oVirt Node 4.4.6.3 Fixing the following bugs: - Bug 1959945 - [NBDE] RHVH 4.4.6

[ovirt-users] Re: Ovirt Engine -- Connection Refused to all hosts

Hi Nick, Could you post some more information about your setup? In particular it would be useful to have the following: 1) *ovirt-engine *version 2) *vdsm-jsonrpc-java *version 3) vdsm logs from the host (*/var/log/vdsm/{vdsm,supervdsm}.log*, check for errors & warnings) 4) libvirt logs (if any) ,

[ovirt-users] Re: Ooops! in last step of Hyperconverged deployment

Cockpit crashes with an Ooops! And therefore closes the ansible output console, so we need to find the file with that output. /ovirt-dashboard just shows blank white screen. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

On Tue, May 18, 2021 at 7:39 AM wrote: > Hello. > I'm having the same issue with cockpit on the nodes. I'm unable to login > as root or local user. I went from 4.4.5 to 4.4.6. It worked fine before > the upgrade. I know the password is correct because I can log into the node > via console and

[ovirt-users] Re: Ovirt Engine -- Connection Refused to all hosts

On Tue, May 18, 2021 at 8:37 AM Nick Polites wrote: > > Hi All, > > I am not sure if my original post is being reviewed before posting but trying > again in case it failed to send. > > I tried logging in this morning to oVrit and see that all of my hosts are > unresponsive. I am seeing a