On Tue, Nov 10, 2020 at 3:13 PM [email protected] <[email protected]> wrote: > > Hello Ritesh > > Engine and host is the same. There is only one box.
This is called all-in-one. Was officially supported until 3.6, and is unsupported, undocumented and untested these days, although people seem to be using it, and even more-or-less successfully. To get an overview of what you should do, if you follow the current documentation, you should read both engine-specific parts and hosts-specific parts. > The vdsm daemon does not seem to exist. > > # systemctl status vdsmd > Unit vdsmd.service could not be found. > > Should I assume that there is a component missing, which should have been > installed? > I just checked the installation documentation, and was not able to spot a > step that could be missing. > https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/#Installing_the_Red_Hat_Virtualization_Manager_SM_localDB_deploy > > Thanks, Toni > > > On 10 Nov 2020, at 13:47, Ritesh Chikatwar <[email protected]> wrote: > > Hello, > > Looks like you are checking this directory in the engine. You will get this > in the host. > Also check vdsm service is running or not using systemctl status vdsmd > > On Tue, Nov 10, 2020 at 6:09 PM [email protected] <[email protected]> > wrote: >> >> Hello Ritesh >> >> I can see the NIC attached to the host in the UI. >> However, I don’t have a directory /var/log/vdsm. >> I am sharing the filetree of my /var/log in the separately attached text >> file: >> >> Thanks, Toni >> >> >> On 10 Nov 2020, at 13:04, Ritesh Chikatwar <[email protected]> wrote: >> >> Hello, >> >> Can you share vdsm logs you can find at /var/log/vdsm/vdsm.log. >> >> I guess this might be a vdsm issue between an engine and host. >> also check in ui whether a nic is attached to the host after upgrade. >> >> On Tue, Nov 10, 2020 at 5:18 PM [email protected] >> <[email protected]> wrote: >>> >>> Hi >>> >>> I am looking for help after my oVirt upgrade failed. >>> >>> >>> I have upgraded from ovirt 4.3 to 4.4 following the instructions here: >>> >>> https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 >>> >>> It's a single-host (standalone engine) test environment. >>> I wiped CentOS 7 and reinstalled a fresh CentOS 8. >>> I installed the oVirt 4.4 repo and all the necessary software packets. >>> >>> I used `engine-backup --mode=restore >>> --file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from >>> a backup file I created before I started the upgrade. >>> After the restore, I ran `engine-setup`. >>> >>> I did not get any errors during any of these steps on the console. >>> So the upgrade could be considered successful from that perspective. >>> >>> After the upgrade, I login to the ovirt admin portal, and I try to >>> "Activate" my host (was set to "Maintenance" mode before upgrade). Please try 'Reinstall'. This should install vdsm for you, among many other things. Best regards, >>> The Activation fails with error "NonResponsive" in the GUI. >>> Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non >>> responsive.” >>> >>> In /var/log/ovirt-engine/engine.log, I find the following error: >>> ``` >>> 2020-11-09 23:12:21,080+01 ERROR >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] >>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] >>> Command 'GetCapabilitiesAsyncVDSCommand(HostName = nuc1.feric.ch, >>> VdsIdAndVdsVDSCommandParametersBase:{hostId='d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb', >>> vds=‘Host[nuc1.feric.h,d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb]'})' execution >>> failed: java.net.ConnectException: Connection refused >>> ``` >>> >>> `systemctl status ovirt-engine` shows that the engine is running. >>> I am able to reboot the host from the oVirt GUI directly. >>> >>> Does anyone have an idea how to proceed? >>> >>> Many thanks >>> Toni >>> _______________________________________________ >>> Users mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> 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/[email protected]/message/QWVBKDG2Q4BJHDHXNAHIWIG3QLW5E235/ >> >> > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/BBBWNXCC5R3TC4FZC2MHKPCBLX3Q4ZHK/ -- Didi _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/6G5GG2EMLZIIZI5M2MIFMXON5H5GANRF/
