VDP backup scheduler fails to start and VDP proxy is not initialized
search cancel

VDP backup scheduler fails to start and VDP proxy is not initialized

book

Article ID: 339441

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • After upgrading VDP to version 6.1.5, the VDP backup scheduler fails to start and VDP proxy is not initialized.
  • The service fails even when after you start manually or through command: You see the user_locked error.
  • ​Running this command reports error:
​root@kp1vdp01:~/#: ls -l /usr/local/avamar-tomcat/lib/mccommons.jar

ls: cannot access /usr/local/avamar-tomcat/lib/mccommons.jar: No such file or directory


Environment

VMware vSphere Data Protection 6.1.x

Cause

This issue occurs because the mccommons.jar file is missing from Tomcat directory after upgrade to VDP v6.1.5

Resolution

To resolve this issue:
  1. Run this command to create a symbolic link from the /usr/local/avamar/lib/mccommons.jar under Tomcat directory.
root@kp1vdp01:~/#: /bin/ln -fs  /usr/local/avamar/lib/mccommons.jar /usr/local/avamar-tomcat/lib/mccommons.jar
 
  1. To check if the symbolic link is created successfully, run this command:
root@kp1vdp01:~/#: ls -l /usr/local/avamar-tomcat/lib/mccommons.jar

You see output similar to:

lrwxrwxrwx 1 root root 35 Nov 30 16:07 /usr/local/avamar-tomcat/lib/mccommons.jar -> /usr/local/avamar/lib/mccommons.jar

  1. Restart the Tomcat service.


Additional Information

简体中文:VDP backup scheduler fails to start and VDP proxy is not initialized