It seems like just about every other day when I try to log into OME (3.2.1.29), the login just hangs. I type in my creds, click the button to log in, and the three little blue dots start flashing across the screen. It never gets past that. I have to go into the VM console, and restart the services to get the thing working again. It doesn't matter if I use AD creds or local creds. There is nothing in the audit log that even shows a login attempt was made either. This is getting to be VERY annoying.....
I haven't experienced this. It sounds like a browser or network issue. I would make sure you are using a supported browser and perform network tests between your computer and the appliance to check for packet loss or other issues.
If you are able to track down something that may be a bug then please post as much information as you can to reproduce it.
It happens regardless of the browser I am using, and I can guarantee there isn't a network issue. I'm on the same vLAN and switch. If it was a network issue, restarting the services wouldn't help.
This past weekend, I built a fresh install of OME VMware appliance v3.3.1 (Build 12) and have almost the exact same issue. The difference for me is that rebooting the OME VM and/or restarting all OME services via the text UI doesn't have any impact for being able to log on. I have tried using different passwords (I'm only logging on with the local admin account, not AD), I've tried connecting from different subnets, etc. I am using Windows 10 1909 (patched and up-to-date) and I'm having this issue with Chrome, Firefox and EDGE (Chromium). I don't have any problems being able to log on to OME when I'm using IE 11 (so at least I can access OME when needed). Otherwise, the other browsers mentioned will often just sit there and show the three dots flashing. Chrome and EDGE (Chromium) seem to have better success at logging on to the OME interface versus using Firefox. I've tried connecting using the NetBIOS name, FQDN and IP address, same results. Seems like a bug.
We also have a fairly new DELL OMIVV appliance deployed (local admin only) and on the same subnet as the OME appliance. No problems at all when logging into it from any browser.
We have the same issue after upgrading to 3.4.0 (build 55). It is no longer possible to login to the console with any other browser than IE11 and it doesn't matter what kind of account we are trying to use (local / AD).
Unfortunately, despite several people posting that they have the same issue, we have yet to receive a useful response from Dell.
However, I have discovered that this issue only happens for me when I attempt to edit our discovery jobs. For some reason, when I try to edit either of the discovery jobs (one is for iDRAC IPs, the other is for VMware Host IPs, about 700 in each discovery job), whenever I try to save my changes, the browser basically locks up. The changes are never saved, and I am never returned to the discovery jobs page. I have to close the tab in the browser. At that point, the entire appliance basically becomes non-responsive. I have to log into the appliance via the CLI, and restart the services before I can log back into it, and perform any other tasks. I’ve tried deleting and recreating the discovery jobs. When I do this, they do not lock up when making changes to them for perhaps a week, or so. Then, all of a sudden, the same thing begins happening again, every time I try to edit them. I have built, and rebuilt the appliance from scratch multiple times. Every time, the result is the same. A week or so after creating the iDRAC and VMware Discovery Jobs, I am no longer able to edit them, without the entire appliance becoming unusable, until I restart all of the services on it via the CLI.
As a workaround, when you are accessing to OME, remove the "login" string in the URL to show only : https:// /core/console/console.html#/ . Let me know if this works.
thanks for your reply, this workaround works for me. For all others with this issue, I have to go to the login page and enter my credentials. Then the issue appears, no redirection to the console. So I have to manually delete the /login from the url to just show https:// FQDN>/core/console/console.html#/ and the console opens up like before.
Daniel My
12 Elder
•
6204 Posts
2601
0
Posted October 3rd, 2019 09:00
Hello
I haven't experienced this. It sounds like a browser or network issue. I would make sure you are using a supported browser and perform network tests between your computer and the appliance to check for packet loss or other issues.
If you are able to track down something that may be a bug then please post as much information as you can to reproduce it.
Thanks