I've had a chance to try this restore again, and this time login to the local
(new) hosted-engine VM to verify that /root/DisableFenceAtStartupInSec.txt just
contains:
to
And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new
hosted-engine VM, my connection closes.
On Tue, Oct 24, 2023 at 01:16:27PM -, Michaal R via Users wrote:
> Well, that's interesting... I wonder if the other imports I've tried give the
> same error. That VM SHOULD have been shut down properly, but I'll check
> again. I've three VMs that won't import, I'll check them again. Do you
On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie
wrote:
> I've had a chance to try this restore again, and this time login to the
> local (new) hosted-engine VM to verify that
> /root/DisableFenceAtStartupInSec.txt just contains:
> to
>
> And if I try the "engine-config -g
I checked for the Fast Startup feature, which I figured wouldn't be enabled,
and it's not even configurable.
I tried, again, to import from vCenter and got error "All chosen VMs couldn't
be retrieved by the external system and therefore have been filtered. Please
see log for details." When I
Thanks again, Gianluca.
I'm currently ssh'd into the new local engine VM, and Postgres is running.
However, an engine DB doesn't exist? Should it at this point, and do you have
any other suggestions of where I should look?
Devin
--
[root@lnxvirt-engine ~]# su - postgres
Last login: Wed
5 matches
Mail list logo
