This issue is due to a regression in the log4j properties file.
This issue is resolved in VMware vCenter Server 6.7 Update 3s.
# cd /storage/log/vmware/content-library/
# echo > content-library-runtime.log.stdout
# cd /etc/vmware-content-library/ # cp -R log4j.properties log4j.properties.old # cat /dev/null > log4j.properties # vi log4j.properties - insert data from file attached to this document
# chown content-library:cis log4j.properties
# chmod 640 log4j.properties
# service-control --restart content-library