Hi Guys,
We have been running vCenter server appliance version 6 (version=6.0.0, build=2776510) in production for about 6 weeks now without issue. 2 days ago logons failed to the server. quick fix was a reboot of the appliance. going through the logs show too many entries with error or failed to filter.
but before the Crash we can see entries such as below: (name of user has been replaced)
2015-12-14T23:54:52.062Z error vpxd[7FED01109700] [Originator@6876 sub=[SSO] opID=24c46df0] [UserDirectorySso] AcquireToken exception: N9SsoClient22CommunicationExceptionE(Operation timed out)
2015-12-14T23:54:52.062Z error vpxd[7FED01109700] [Originator@6876 sub=User opID=24c46df0] Failed to authenticate user 2015-12-14T23:54:52.527Z error vpxd[7FECF3060700] [Originator@6876 sub=[SSO] opID=5ac13399] [UserDirectorySso] AcquireToken exception: N9SsoClient22CommunicationExceptionE(Operation timed out)
2015-12-14T23:54:52.527Z error vpxd[7FECF3060700] [Originator@6876 sub=User opID=5ac13399] Failed to authenticate user 2015-12-14T23:54:57.068Z info vpxd[7FED01109700] [Originator@6876 sub=vpxLro opID=24c46df0] [VpxLRO] -- FINISH task-internal-275213344
2015-12-14T23:54:57.068Z info vpxd[7FED01109700] [Originator@6876 sub=Default opID=24c46df0] [VpxLRO] -- ERROR task-internal-275213344 -- SessionManager -- vim.SessionManager.login: vim.fault.InvalidLogin:
looks like an SSO issue.
SR has been logged with VMware but it seems they are too busy with other customers to deal with our case.
Has anyone experienced anything similar? T
his happens in the middle of a busy backup period (netbackup using snapshot based backup of VMs)
Regards
Ciarán
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
