vSphere Data Protection Core Services fail to start and report the error: FATAL ERROR: licensevalidator::body no valid license found
search cancel

vSphere Data Protection Core Services fail to start and report the error: FATAL ERROR: licensevalidator::body no valid license found

book

Article ID: 307825

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • vSphere Data Protection (VDP) Core Services fail to start
  • Rebooting the appliance does not resolve the issue
  • This issue occurs after 30 days of the VDP appliance deployment
  • In the dpnctl.log file, located at /usr/local/avamar/var/log, or the gsan.log file, located at /data01/cur, you see messages similar to:

    <YYYY-MM-DD>T<time>.91800 {0.0} [licensevalidator:114] ERROR: <0948> license grace period expired 10 days ago (Mon Dec 17 19:47:16 2012)
    </time>
    <YYYY-MM-DD>T<time></time>.91809 {0.0} [licensevalidator:114] FATAL ERROR: <0001> licensevalidator::body no valid license found

  • Your ESXi hosts and vCenter Server meet the minimum license requirements as described in vSphere Data Protection (VDP) appliance licensing logic (2044613)

Note: This article does not apply if the hosts do not meet the minimum license requirements.


Environment

VMware vSphere Data Protection 5.1.x

Cause

This issue occurs when the license check function fails to validate the vCenter Server user configured for the VDP connection.

Initial validation occurs against vCenter Server. If the validation is successful, the gsan.log file reports entries similar to:

<YYYY-MM-DD>T<time></time>.94454 {0.0} [licensevalidator:114] gsankeyhash::readkeydata open failed /usr/local/avamar/etc/license.xml
<YYYY-MM-DD>T<time></time>.94623 {0.0} [runlevelbeat] runlevelmanager::taskrunner::isreadyfornextlevel licensevalidator is not ready for next level
<YYYY-MM-DD>T<time></time>.94639 {0.0} [runlevelbeat] runlevelmanager::taskrunner::isreadyfornextlevel licensevalidator is not ready for next level
<YYYY-MM-DD>T<time></time>.39269 {0.0} [licensevalidator:114] licensevalidator::testexpiration vSphere Data Protection (VDP) licensing mode
<YYYY-MM-DD>T<time></time>.39272 {0.0} [licensevalidator:114] licensevalidator::body ready for next runlevel

To check if the license validator is correctly validating the license:
  1. Open an SSH session to the VDP appliance.
  2. Browse to the /usr/local/vdr/bin directory.
  3. Run the license validator script:

    # ./hostLicenseCheck.sh

    If the license validation is working, it reports LICENSED. If it reports ERROR, proceed to the Resolution section.

Resolution

To troubleshoot and resolve the license validator error:

  1. Open an SSH session to the VDP appliance.

  2. Change to the /usr/local/vdr/bin directory by running this command:

    cd /usr/local/vdr/bin

  3. Run this command:

    /usr/java/latest/bin/java -jar /usr/local/vdr/lib/vdp-configure.jar


    You see an output similar to:

    Jan 28, 2013 8:23:28 AM com.emc.vdr.vmware.license.LicenseManager getLocalHostLicensed
    SEVERE: Error while checking for host is licensed:
    com.vmware.vim25.InvalidLogin
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at java.lang.Class.newInstance0(Unknown Source)
    at java.lang.Class.newInstance(Unknown Source)
    at com.vmware.vim25.ws.XmlGen.fromXml(XmlGen.java:201)
    at com.vmware.vim25.ws.XmlGen.parseSoapFault(XmlGen.java:80)
    at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:132)
    at com.vmware.vim25.ws.VimStub.login(VimStub.java:1491)
    at com.vmware.vim25.mo.SessionManager.login(SessionManager.java:149)
    at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:97)
    at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:69)
    at com.emc.vdr.vmware.vi.VIAccess.getServiceInstance(VIAccess.java:96)
    at com.emc.vdr.vmware.vi.VIAccess.isHostLicensed(VIAccess.java:444)
    at com.emc.vdr.vmware.license.LicenseManager.getLocalHostLicensed(LicenseManager.java:15)
    at com.emc.vdr.vmware.Main.main(Main.java:17)
    ERROR

  4. Verify the VDP vCenter user account is correctly configured:
    • vCenter user account validation can fail due to insufficient privileges or security restrictions imposed on the account. Ensure that the VDP vCenter user account can successfully log into the target vCenter Server and the user has access to the relevant administrative privileges, for details see the Minimum Required vCenter User Account Permissions section of the vSphere Data Protection Administration Guide.
    • Verify that the account is not locked and the password is not expired.
    • Verify that there are no special characters or spaces in the vCenter Server password for the configured user. If special characters exist, modify the password so that there are no special characters or configure a new user with a suitable password.

  5. Open the /usr/local/vdr/etc/vcenterinfo.cfg file using a text editor.
  6. Change these entries to match the newly created password (and username, if applicable):

    vcenter-username=username
    vcenter-password=password

  7. Run the /usr/local/vdr/bin/hostLicenseCheck.sh script again. It should now show as LICENSED.

  8. Go to the VDP GUI at https://VDP_Appliance_IP_Address:8543/vdp-configure.

  9. Restart Core Services and File System Services.

  10. Restart Management Services.

    Note: Click Yes when you see this error while restarting Management Services:

    Management services failed to start. Would you like to attempt to restore them to a backed up state?

    The VDP appliance should now be fully functional.


Additional Information

Active Directory account locks out due to repeated failed login attempts from VMware vCenter Server
vSphere Data Protection (VDP) appliance licensing logic
vSphere Data Protection コア サービスの起動が失敗し、次のエラーが報告される: FATAL ERROR: <0001> licensevalidator::body no valid license found