We're connecting to Active Directory via LDAPS, and sometime within the past few weeks the above logfile begain spinning until finally our vcenter went yellow for log space utilization. All the log entries are substantially in the form:
2019-03-07T23:48:58.061441+00:00 warning vmdird t@140142492772096: No SD found for cn=DSE Root
Haven't made any changes to AD schema or SSO config on vsphere. Searching Google I find a few people asking about this, but nobody answering. So, what gives?
Hello mikeely
If the cause of the log spew was fixed in 6.7 U1 it is not in the release notes - whether these logging messages were present previously before you noticed from running out of space is another thing you should consider.
There was an issue with syslog log rotation that was resolved in 6.7 U1:
'Disk usage of syslog files might grow exponentially due to an issue with the log rotation
Log rotation and compression for some syslog files might stop after the first round and file size might grow significantly. The affected files are: /var/log/vmware/messages, /var/log/vmware/*/*-syslog.log and /var/log/vmware/esx/*/*-syslog.log.
This issue is resolved in this release.'
VMware vCenter Server 6.7 Update 1 Release Notes
Did you perchance upgrade this vCenter from 6.5U2 to 6.7 or is it a fresh install?
Bob
What version of Vcenter ?
This is seems to be a known bug with VC 6.7 and fixed in 6.7 U1 and U2
Please mark this as "correct" or " Helpfull" if this answers your query.
regards
Gayathri
We're on 6.7.0.
Is there a release note addressing this fix I can use to justify the update priority?
Hello mikeely
If the cause of the log spew was fixed in 6.7 U1 it is not in the release notes - whether these logging messages were present previously before you noticed from running out of space is another thing you should consider.
There was an issue with syslog log rotation that was resolved in 6.7 U1:
'Disk usage of syslog files might grow exponentially due to an issue with the log rotation
Log rotation and compression for some syslog files might stop after the first round and file size might grow significantly. The affected files are: /var/log/vmware/messages, /var/log/vmware/*/*-syslog.log and /var/log/vmware/esx/*/*-syslog.log.
This issue is resolved in this release.'
VMware vCenter Server 6.7 Update 1 Release Notes
Did you perchance upgrade this vCenter from 6.5U2 to 6.7 or is it a fresh install?
Bob
Thanks to you both. I'm pretty sure this was an upgrade.
Hello mikeely,
You should find out from whom performed the upgrade was it a supported upgrade path e.g. 6.5 U2 to 6.7 GA is a 'back in time' upgrade which could potentially cause issues (that merely updating won't fix):
VMware Product Interoperability Matrices
Bob
Hello,
Update on this - looks like resolved in 6.7 U2.
Bob