VMware Cloud Community
pedrocalixto
Contributor
Contributor

VDP 6.1 Internal Proxy Error

Hello,

After a Storage VMotion of the VDP appliance, it became unresponsive. I'm not able to manage it through vCenter nor its web interface. I guess it's something related to its internal proxy.

When I try to enable it, it fails. I've already rebooted the VDP appliance and the VCSA. Also, I've checked via CLI the health of the VDP services and the backup data. Seems fine.

I've also tried to unregister VDP VM and register again. I need help Smiley Sad

My environment:

ESXi 6.0 U2

VCSA 6.0 build 3634794

VDP 6.1

Here it comes some screenshots and logs of the issue:

/usr/local/avamar/var/vdr/server_logs/vdr-server.log

2016-06-15 11:48:12,020 ERROR [Timer_CustomValue]-vi.ViJavaAccess: doGetAveVirtualMachine(): Unable to obtain local AVE virtual machine from its IP address [10.12.73.253]

2016-06-15 11:48:12,021 ERROR [Timer_CustomValue]-vi.ViJavaAccess: getAveVirtualMachine(): Unable to obtain local AVE virtual machine. Might be an Avamar physical machine.

2016-06-15 11:48:12,021 ERROR [Timer_CustomValue]-vi.ViJavaAccess: Failure to determine local AVE instance-uuid

2016-06-15 11:48:12,061 ERROR [Timer_CustomValue]-schedule.CustomValueUpdateTimerTask: Could not update the custom values.

java.lang.NullPointerException

        at java.lang.String.contains(Unknown Source)

        at com.emc.vdp2.schedule.CustomValueUpdateTimerTask.checkAndUpdateAnnotation(CustomValueUpdateTimerTask.java:97)

        at com.emc.vdp2.schedule.CustomValueUpdateTimerTask.run(CustomValueUpdateTimerTask.java:72)

        at java.util.TimerThread.mainLoop(Unknown Source)

        at java.util.TimerThread.run(Unknown Source)

2016-06-15 11:48:16,869 ERROR [Timer_ServiceHealthValidator]-vi.ViJavaAccess: doGetAveVirtualMachine(): Unable to obtain local AVE virtual machine from its IP address [10.12.73.253]

2016-06-15 11:48:16,869 ERROR [Timer_ServiceHealthValidator]-vi.ViJavaAccess: getAveVirtualMachine(): Unable to obtain local AVE virtual machine. Might be an Avamar physical machine.

2016-06-15 11:48:16,869 ERROR [Timer_ServiceHealthValidator]-schedule.AlarmCheckTimerTask: Failed to get aveVM. aveVM is null

2016-06-15 11:48:16,869 INFO  [Timer_ServiceHealthValidator]-schedule.ServiceHealthValidatorTimerTask: Starting Service Health Check on Wed Jun 15 11:48:16 BRT 2016

2016-06-15 11:48:16,878 INFO  [Timer_retireVM]-schedule.RetireVirtualMachineTask: Searching for virtual machine registrations to retire...

2016-06-15 11:48:16,879 ERROR [Timer_HFSValidator]-vi.ViJavaAccess: doGetAveVirtualMachine(): Unable to obtain local AVE virtual machine from its IP address [10.12.73.253]

2016-06-15 11:48:16,879 ERROR [Timer_HFSValidator]-vi.ViJavaAccess: getAveVirtualMachine(): Unable to obtain local AVE virtual machine. Might be an Avamar physical machine.

2016-06-15 11:48:16,880 ERROR [Timer_HFSValidator]-schedule.AlarmCheckTimerTask: Failed to get aveVM. aveVM is null

2016-06-15 11:48:17,136 INFO  [Timer_retireVM]-connection.Mcsdk10StubManager: ServiceInstanceMoref desc=Service Id: urn:uuid:08FCE6D79ECB43283E1466002109508 name=urn:uuid:08FCE6D79ECB43283E1466002109508 value=SERVICE

2016-06-15 11:48:17,186 INFO  [Timer_retireVM]-connection.McAccessManager: Creating new mcsdk stub handler for connection key: [1151234205, Service Id: urn:uuid:08FCE6D79ECB43283E1466002109508] on Thread: [Timer_retireVM]

2016-06-15 11:48:17,240 INFO  [Timer_HFSValidator]-schedule.HFSValidatorTimerTask: HFS ValidRangeHours 48

2016-06-15 11:48:17,240 INFO  [Timer_HFSValidator]-schedule.HFSValidatorTimerTask: Last validated checkpoint happended on Tue Jun 14 15:06:25 BRT 2016

2016-06-15 11:48:17,360 INFO  [Timer_ServiceHealthValidator]-schedule.ServiceHealthValidatorTimerTask: Internal proxy configured?true

2016-06-15 11:48:17,360 INFO  [Timer_ServiceHealthValidator]-services.BaseCLI: GsanCLI: Updating service state.

2016-06-15 11:48:18,421 INFO  [GsanCLI-update]-services.BaseCLI$4: GsanCLI-update: State update complete. New state: running

2016-06-15 11:48:18,421 INFO  [Timer_ServiceHealthValidator]-services.BaseCLI: McsCLI: Updating service state.

2016-06-15 11:48:18,441 INFO  [McsCLI-update]-service.AdapterUtils: MCS Web Services URL: https://vdp6.epl.gov.br:9443/services/mcService  MCUserId="MCUser"

2016-06-15 11:48:18,632 INFO  [McsCLI-update]-connection.Mcsdk10StubManager: ServiceInstanceMoref desc=Service Id: urn:uuid:08FCE6D79ECB43283E1466002111165 name=urn:uuid:08FCE6D79ECB43283E1466002111165 value=SERVICE

2016-06-15 11:48:18,650 INFO  [McsCLI-update]-connection.McAccessManager: Creating new mcsdk stub handler for connection key: [1151234205, Service Id: urn:uuid:08FCE6D79ECB43283E1466002111165] on Thread: [McsCLI-update]

2016-06-15 11:48:18,699 INFO  [McsCLI-update]-services.McsCLI: MC Connection with Key: [McConnectionKey URI: https://vdp6.epl.gov.br:9443/services/mcsdk10 Username: MCUser Locale: en_US mcDomain: / trustAllSSLCerts: true productName: VDP] isConnected: [true]

_________________________________________ If you find an answer that helps you, please mark it as "correct" or "helpful". VCP6-DCV Http://pedrocalixto.com | virtually anything is possible
Tags (1)
Reply
0 Kudos
3 Replies
SavkoorSuhas
Expert
Expert

I have the exact same issue.

Any thoughts?


Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

Reply
0 Kudos
Franck999
Enthusiast
Enthusiast

Hi,

Got the same problem today here.

In fact it comes from the wmare tools of the vdp appliance, they didn't work, I had to reinstall them.

The vmware tools give the ip information to the vcenter, and in our case, vdp is looking for it.

Max

Reply
0 Kudos
Jongoodson
Contributor
Contributor

Anyone have a solution regarding this?

I have tried this guide http://www.virtuallypeculiar.com/2017/04/failed-to-start-internal-proxy-in-vdp-6x.html , but still no luck.

regards.

Reply
0 Kudos