On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie <devin.bou...@cornell.edu> 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 DisableFenceAtStartupInSec" from the > new hosted-engine VM, my connection closes. > [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt > to > [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g > DisableFenceAtStartupInSec > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > Connection to the Database failed. Please check that the hostname and port > number are correct and that the Database service is up and running. > Connection to 192.168.222.25 closed. > > Any new suggestions or more tests I can run would be greatly appreciated. > > Thanks, > Devin > > The key thing here is that for some reason it seems it is not able to connect to the database and so when "engine-config" command tries to get the second field of the output (the " | cut -d' ' -f2" part) it gets the "to" string here: Connection to the Database failed and anyway it returns error with failure of the overall playbook It should be investigated if there is a problem with the database itself on the new engine or if for some reason the "engine-config" command is not able to implicitly connect to the database
_______________________________________________ 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/FR7KU3LAMEDTAZYBWJM4JO22M3FUVO65/