Failed to validate the user credential, configuring ethernet interfaces
Greetings.
I am hoping this community can offer some direction or guidance.
I have a NetBackup 8.2 appliance configured at one site (network and IPMI access were all functioning). This appliance was to be moved to another site, and consequently another network. Before physically moving the appliance, I conigured the IPMI to match the network at the new site (which I was unable to take advantage of due to not having access to a computer with Java on it).
Once the appliance was mounted and the IPMI was connected at the new site (the other ethernet interfaces were unplugged/disconnected still), I started noticing some behaviors:
- Longer than usual boot up time.
- When logging in with the local administrative account, the time to login was longer than usual, and a message would appear that read "Unable to authenticate the user for web service access."
- When I would finally be logged in (this was being done using a KVM in the rack and not IPMI remote management), I would attempt to configure an ethernet interface to match the new network, and I would receive an error of "Failed to validate the user credentials. Please logout and login to Appliance Shell Menu and retry the operation."
- Furthermore, this "Failed to validate..." error would also be received when trying to run Appliance.Network > Show Configuration.
- Logging out/logging in and restarting for good measure did not seem to have an effect on the behaviors.
Regarding the "Unable to authenticate the user for web service access..." I did execute Appliance.Infraservices > Show All, and all 3 (Database, Message queue and Web server) are all reported as running.
I am hoping there is something I am missing.
Assistance, recommendations and guidance are all welcome.
Thank you in advance.
Hi edwardd
Another thing to check/ask - is the appliance configured to use Active Directory (or LDAP) authorization/authentication? If so, you could try removing this (you can reconfigure this later once the network is functioning again).
Also, if you are able to log in and can get an elevated shell running, you could try renaming the /etc/resolv.conf file to see if this helps you configure the network correctly.
David