Hi,
Quite often I'm facing the issue that the C:\ partition of my vCenter server gets filled up with vmdird dmp files. I first looked around a bit to see if there was some kind of tool I could use to analyse these dumps, but haven't found anything. I did however find out that my vmdir.log (in C:\ProgramData\VMware\CIS\logs\vmdird) was full with errors like these:
2015-02-09 17:38:32.735:t@23378464:INFO: Reading Reg: ConfigPath
2015-02-09 17:38:32.735:t@23378464:INFO: Reading Reg: ConfigPath
2015-02-09 17:39:02.772:t@23378016:INFO: Reading Reg: dcAccountPassword
2015-02-09 17:39:02.792:t@23378016:INFO: Reading Reg: dcAccountPassword
2015-02-09 17:39:02.795:t@23378464:ERROR: VmDirSASLGSSBind failed. (-2)(Local error)
2015-02-09 17:39:02.795:t@23378464:ERROR: vdirReplicationThrFun: VmDirKerberosBind FAILED (-2)
These errors seem to repeat themselves every 30s. vSphere setups in other locations don' have these kind of errors. Apart from the occasional out of space issues on the vcenter server due to the big dmp files, this doesn't seem to impact our environment a lot, but I still like to get it fixed
I'm aware of VMware KB: Reinstalling vCenter Single Sign-On 5.5 stops after displaying the message: Configuring S..., but these error messages are slightly different and even reinstalling the SSO components from a recent vCenter ISO doesnt seem to help.
If anyone coud clarify what's going on here, it would be greatly appreciated!
Dieter
Heya,
from a quick look there seems to be something going funny with Kerberos, the authentication component of Active Directory - can you perhaps check with your AD Team?
Hi Alistar,
Thanks for taking a look. On the AD side we don't see any problems. Logging in with domain accounts for example, still works. We've also checked all accounts used to run the services and they are all valid, non-expired accounts.
The only catch I can think of is that the error seems to be initiated by a replication of information - are you using linked mode between your vCenters by any chance?
Anyways,if someone else doesn't know and you don't have support from VMware, I'm all out of bullets to shoot this trouble ![]()
