Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"An error occurred while starting service 'VMwareDNSService'" - vCenter Server convergence failure during VMAFD firstboot (68159)

Last Updated: 10/25/2019Categories: TroubleshootingTotal Views: 13464Language:
English

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Symptoms

vCenter converge process fail during VMAFD firstboot

Running firstboot stage 1 of 4 failed

In /var/log/firstboot/vmafd-firstboot.py_stdout.log, you see entries similar to:

2019-05-07T07:31:50.515Z  Running command: ['/opt/likewise/bin/lwsm', 'status', 'vmdns']
2019-05-07T07:31:50.522Z  Error: LW_ERROR_NO_SUCH_SERVICE (41204) No service with the specified name exists
2019-05-07T07:31:50.523Z  VMAFD Boot failed

In /var/log/firstboot/vmafd-firstboot.py_stderr.log, you see entries similar to:

2019-05-07T07:31:50.524Z  Exception: Traceback (most recent call last):
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 177, in main
controller.firstboot()
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 51, in firstboot
self.start()
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 67, in start
service.start()
File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmdnsInstall.py", line 50, in start
self.utils.start_service(self.__VMDNS_SERVICE_NAME, self.__VMDNS_COMPONENT_NAME)
File "/usr/lib/vmware-vmafd/firstboot/identityinstall/LinuxUtils.py", line 131, in start_service
raise ServiceStartException(serviceName)
cis.exceptions.ServiceStartException: {
"componentKey": null,
"problemId": null,
"detail": [
{
"localized": "An error occurred while starting service 'VMwareDNSService'",
"args": [
"VMwareDNSService"
],
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"resolution": null
}

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

There are two DNS RPMs: vmware-dns-server and vmware-dns-client. The client RPM is installed on vCenter with external PSC node, while the server RPM is installed on PSC nodes. When the RPMs are installed, several configuration parameters are added to the "registry”. The client and server RPMs each register a different set of config parameters, however both sets are stored in the same location in the registry, so when the server RPM is installed, it should overwrite the client parameters with the server set.

This issue occurs when the vmware-dns-server RPM is correctly installed on the machine, but the registry values still correspond to the client settings, not the server settings. This causes the VMwareDNSService service fail to start, since the service can't find the server settings that it needs in the registry, causing the vmafd firstboot to fail.

Resolution

This issue is resolved in vCenter Server 6.7 U3a, available at VMware Downloads.

Workaround

Note: Take snapshot of all the vCenter Servers and PSCs (which are part of ELM) in a Powered off state before proceeding with below steps:

To workaround this issue, proceed with below steps on the vCenter Server Appliance where Convergence failed :

Find the vmware-dns-server rpm:

find / -name vmware-dns-server*.rpm

Remove the vmware-dns-server rpm

rpm -ev --nodeps vmware-dns-RPMName-FromStep1 (without .rpm extension)

Example - rpm -ev --nodeps vmware-dns-server-1.0.0-12304056.x86_64

Install the vmware-dns-server rpm

rpm -ivh --nodeps /root/velma/rpm/<vmware-dns-name-FromStep1.rpm>

Example - rpm -ivh --nodeps /root/velma/rpm/vmware-dns-server-1.0.0-12304056.x86_64.rpm

Stop VMAFD Service

service-control --stop vmafdd

Recreate VECS DB from convergence process backup

mv /storage/db/vmware-vmafd/afd.db /storage/db/vmware-vmafd/afd.db_backup

Copy AFD DB from backup

ls /root/velma/rollback/ -l (list the files and identify the full name of afd.db backup with the converge date)

Copy the backup DB to /storage/db/vmware-vmafd folder with file name 'afd.db' (Example - cp /root/velma/rollback/2019-08-09_05-58-37afd.db /storage/db/vmware-vmafd/afd.db)

Start VMAFD Service

service-control --start vmafdd

Modify file /etc/vmware/install-defaults/deployment.node.type from embedded to management

vi /etc/vmware/install-defaults/deployment.node.type

Modify the string embedded to management

Save and Exit the VI editor (Press Esc Key followed by :wq! and Enter)

Modify file /etc/issue from embedded to Exernal

vi /etc/issue

Modify the string embedded to External

Save and Exit the VI editor (Press Esc Key followed by :wq! and Enter)

Modify file /etc/vmware/deployment.node.type from embedded to management

vi /etc/vmware/deployment.node.type

Modify the string embedded to management

Save and Exit the VI editor (Press Esc Key followed by :wq! and Enter)

Modify file /etc/applmgmt/appliance/appliance.conf from embedded to management

vi /etc/applmgmt/appliance/appliance.conf

Modify the string embedded to External

Save and Exit the VI editor (Press Esc Key followed by :wq! and Enter)

Modify DomainState in Likewise Registry to 0x00000002

/opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\vmafd\Parameters]' DomainState 2

Verify the modified value using list_values command - /opt/likewise/bin/lwregshell list_values '[HKEY_THIS_MACHINE\Services\vmafd\Parameters]'

Recreate the Deleted Machine Account by following the Steps in KB Recreate vCenter Server Machine Account in Platform Services Controller after Failed Convergence

Rename the Convergence failed backup folder /root/velma

mv /root/velma /root/velma_$(date +%d-%m-%Y_%H_%M_%S)

Rename failed Convergence logs under /var/log/vmware/converge/

mv /var/log/vmware/converge/converge.log /var/log/vmware/converge/converge_$(date +%d-%m-%Y_%H_%M_%S).log

mv /var/log/vmware/converge/converge_status.json /var/log/vmware/converge/converge_status_$(date +%d-%m-%Y_%H_%M_%S).json

mv /var/log/vmware/converge/converge_rest.log /var/log/vmware/converge/converge_rest_$(date +%d-%m-%Y_%H_%M_%S).log

Start all the services

service-control --start --all

Retry the Convergence

Related Information

Deploying or Installing an additional Platform Service Controller 6.0 Update 1b fails during vmafd firstboot
Recreate vCenter Server Machine Account in Platform Services Controller after Failed Convergence

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Chrome 75 を使用している場合、展開フォームに送信、次、キャンセルボタンが表示されない (70879)

KB
•
vCloud Availability 3.0 で Replicator サービスを起動すると、「offlineSyncStopper という名前の bean の作成中にエラーが発生しました (Error creating bean with name offlineSyncStopper)」というエラーが表示される (71216)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant