1 Rookie
•
98 Posts
0
1691
July 18th, 2021 14:00
Dell OMSA v10.1 (necessary for ESXi 7.0) is unstable
Has anyone else noticed that the new v10.1 release of OMSA (needed for ESXI 7.x) stops working?
On a Dell R630 running VMware ESXi 7.0Update2, the recent release of OMSA v10.1 (released July 14, 2021) paired with OMSA managed node for Windows (v10.1 of this software released on the same date) stopped working after a simple reboot of the host. CIM was still running.
I had to remove the OMSA VIB then reinstall it. OMSA immediately started working again.
The OMSA managed node for Windows was accessed using Edge and Chrome-- no difference. Neither worked after the host reboot. Only reinstalling the OMSA VIB for VMware fixed the issue.
No Events found!
DELL-Vivek S
1 Rookie
•
118 Posts
0
July 18th, 2021 22:00
Hi,
Could you share the login error message when you say OMSA "stopped working".
Also please confirm if the OM service was not running?
Based on the Linux user guide - link, Page 29 - there is a note around this to debug.
So if there is a reboot, it needs some time before login is attempted.
Also, what is the status with sfcbd based on the below input context on page 28?
Please share your inputs.
Thanks
Vivek
#IWork4Dell
hudson8
1 Rookie
•
98 Posts
0
July 19th, 2021 05:00
The error was something like "login timeout" or another word like "credentialing timeout". I don't remember what the first word was, but the second word was definitely "timeout" not failure. I do get a "login failure" when CIM is turned off.
CIM server and slpd were both running and the server had been up for more than a day.
More details-- OMSA had been loaded and was working fine. I needed to reboot the host.
I rebooted the host and may have tried to access OMSA too soon. Received the "credential timeout" error (again, I'm unsure of the first word), but OMSA was permanently down. I waited an hour. CIM server and slpd were both running.
OMSA still gave this "credential timeout" (again the error said timeout, not failure).
I tried /sbin/services.sh restart which has worked in the past for other versions of OMSA, but that did not work. I then rebooted the host and waited an hour before trying OMSA. Still did not work.
The next day I uninstalled the v10 OMSA VIBs and immediately reinstalled with no reboot. OMSA has worked fine, now for 2 days.
To me, it seems like something about trying OMSA too early after a reboot of the host permanently inactivated something needed to access OMSA. Uninstalling and reinstalling the VIBs fixed the issue.
I have not tested rebooting the host and waiting an hour or so before trying OMSA. But this is not something I want to do. I'll let you know through this post if OMSA stops working again.
Thank you for picking up this thread.
hudson8
1 Rookie
•
98 Posts
0
July 19th, 2021 08:00
In case this happens again. Can you give me specific instructions for checking whether sfcbd service is set to run in read-only mode. Can this be done from the ESXi gui? If not, can you tell me in detail how to sort this out using putty to the host server. How to read the sfcb.cfg file and how to edit it.
Thank you.
DELL-Vivek S
1 Rookie
•
118 Posts
0
July 19th, 2021 22:00
Hi,
Also, there is a VMWare KB for ESXi 7.0 Update 2 - Link
Thanks
Vivek
#IWork4Dell
hudson8
1 Rookie
•
98 Posts
0
July 27th, 2021 17:00
I think this is what happened. I tried to login too early to OMSA and this did something to OMSA in a permanent manner that prevented all future logins. I had to remove and re-install OMSA on the VMware host. Perhaps this "permanent" change was making sfcbd and read only. If it happens again I will check the read-only status of sfcbd and report back here.
hudson8
1 Rookie
•
98 Posts
0
August 6th, 2021 11:00
Actually, this is not the issue.
I just rebooted the Host, waited 15 minutes and tried to connect using OMSA v10.1. It fails.
I ran the command esxcli system wbem get
and got among other things Readonly: false
So wbem is not readonly.
Do you have other suggestions? I can keep OMSA down for a while, before uninstalling it and re-installing it to fix this.