On Thu, Feb 4, 2021 at 12:15 PM Roderick Mooi wrote:
>
> Thanks so much, this worked!
>
> For the record/list benefit, I first put the host into maintenance and then
> selected Enroll Certificate - this regenerated the certs.
> (VDSM cert can be checked with: certtool -i --infile
>
Thanks so much, this worked!
For the record/list benefit, I first put the host into maintenance and then
selected Enroll Certificate - this regenerated the certs.
(VDSM cert can be checked with: certtool -i --infile
/etc/pki/vdsm/certs/vdsmcert.pem)
I then took these steps on the affected
On Thu, Feb 4, 2021 at 10:09 AM Roderick Mooi wrote:
>
> Hi Didi!
>
> Ok, I started the clean metadata process and then found the real issue - I
> had copied the certs (just /etc/pki/vdsm; other pki folders were intact) from
> a working host (host 2) to host 1 following the re-deploy cleanup as
Hi Didi!
Ok, I started the clean metadata process and then found the real issue - I had
copied the certs (just /etc/pki/vdsm; other pki folders were intact) from a
working host (host 2) to host 1 following the re-deploy cleanup as part of the
process to get it online again. The problem is the
On Wed, Feb 3, 2021 at 4:52 PM Roderick Mooi wrote:
>
> Thanks,
>
> > I didn't check, but am pretty certain that it's not related to the
> > engine db. Do you see such duplicates there as well (using the web ui
> > or sql against it)? If so, fix these first. If no other means, put the
> > host to
Thanks,
I didn't check, but am pretty certain that it's not related to the
engine db. Do you see such duplicates there as well (using the web ui
or sql against it)? If so, fix these first. If no other means, put the
host to maintenance and reinstall with the correct name.
Not seeing
On Wed, Feb 3, 2021 at 4:21 PM Roderick Mooi wrote:
>
> Hi,
>
> > Any idea how this happened?
>
> Somehow related to the power being "pulled" at the wrong time?
>
> > Perhaps this is a backup done by emacs?
>
> Not sure what does it but I'm glad it did ;)
>
> > Please compare it to your other
Hi,
Any idea how this happened?
Somehow related to the power being "pulled" at the wrong time?
Perhaps this is a backup done by emacs?
Not sure what does it but I'm glad it did ;)
Please compare it to your other hosts. It should be (mostly?)
identical, but make sure that host_id= is
On Wed, Feb 3, 2021 at 11:12 AM Roderick Mooi wrote:
>
> Hello and thanks for assisting!
>
> I think I may have found the problem :)
>
> /etc/ovirt-hosted-engine/hosted-engine.conf
>
> is blank.
>
> But I do have hosted-engine.conf~
Any idea how this happened?
Perhaps this is a backup done by
Hello and thanks for assisting!
I think I may have found the problem :)
/etc/ovirt-hosted-engine/hosted-engine.conf
is blank.
But I do have hosted-engine.conf~
Can I cp this to restore the original?
Anything else I need to do?
Appreciated
On 2021/02/02 11:37, Strahil Nikolov wrote:
Usually,
I would start with checking the output of the
/var/log/ovirt-hosted-engine-ha/{broker,agent}.log
I'm typing it on my phone, so the path could have a typo.
Check if the following services (also typed by memory, might have to remove the
'd') are running:- sanlock- supervdsmd- vdsmd
11 matches
Mail list logo
