JedB
Contributor
Contributor

Proxy Error VDP 5.8.4

Hi,

I have updated my vCenter server appliance to version 5.5.0 4180647 for my ESXi 5.5 Update 3b enviroment.

Since that day, one of my two VDP appliances can't backup my VMs anymore.

It is the newer one with the version 5.8.4.6. My older VDP (5.8.0.467) is still working!

The VDP log file reports the error "30983" - a proxy problem.

But in the webinterface the proxy entry is shown:

proxy.PNG

I have SSH into the vdp and asked for the proxy setting. These are my results:

admin@L6399W05:/root/#: echo "select * from proxy_datastore_mapping" | psql mcdb -p 5555 -U admin

could not change directory to "/root"

proxy_cid | datastore_id | vc_cid

-----------+--------------+--------

(0 rows)

root@L6399W05:~/#: mccli activity show

0,23000,CLI command completed successfully.

ID               Status              Error Code Start Time           Elapsed     End Time             Type             Progress Bytes New Bytes Client     Domain

---------------- ------------------- ---------- -------------------- ----------- -------------------- ---------------- -------------- --------- ---------- -----------------------------------------

9147872340903909 No Eligible Proxies 0          2016-11-09 21:30 CET 00h:00m:14s 2016-11-09 21:30 CET Scheduled Backup 0 bytes        0%        RadiusW05d /vcenterlan.xyz.com/VirtualMachines

9147872341354809 No Eligible Proxies 0          2016-11-09 21:30 CET 00h:00m:09s 2016-11-09 21:30 CET Scheduled Backup 0 bytes        0%        L6804W05   /vcenterlan.xyz.com/VirtualMachines

9147872340453109 No Eligible Proxies 0          2016-11-09 21:30 CET 00h:00m:18s 2016-11-09 21:30 CET Scheduled Backup 0 bytes        0%        L6805W05   /vcenterlan.xyz.com/VirtualMachines

9147872341805709 No Eligible Proxies 0          2016-11-09 21:30 CET 00h:00m:05s 2016-11-09 21:30 CET Scheduled Backup 0 bytes        0%        RadiusW05c /vcenterlan.xyz.com/VirtualMachines

9147872342256609 No Eligible Proxies 0          2016-11-09 21:30 CET 00h:00m:00s 2016-11-09 21:30 CET Scheduled Backup 0 bytes        0%        IAC-BOX-V4 /vcenterlan.xyz.com/VirtualMachines

I have restartet the VDP four or five times but no luck.

Also I can't  create a new backup job? The VDP creates the job but the VMs are not added to the job. The error just says, that it was unable to add the client to the backup job.

Any ideas?

0 Kudos
2 Replies
JedB
Contributor
Contributor

I found detailed informations in the vdr-configure.log:

2016-11-10 10:30:41,486 ERROR [localhost-startStop-1]-mc.MCDataSourceProviderImpl: Failed To Initialize DataSource

javax.naming.NameNotFoundException: Name [mcdb] is not bound in this Context. Unable to find [mcdb].

2016-11-10 10:30:41,489 ERROR [localhost-startStop-1]-mc.BaseMCDAO: Failed to create data source.

javax.naming.NameNotFoundException: Name [mcdb] is not bound in this Context. Unable to find [mcdb].

2016-11-10 10:30:41,496 ERROR [localhost-startStop-1]-mc.MCDataSourceProviderImpl: Failed To Initialize DataSource

javax.naming.NameNotFoundException: Name [mcdb] is not bound in this Context. Unable to find [mcdb].

2016-11-10 10:31:08,932 ERROR [pool-9-thread-1]-backupagent.BackupAgentServiceImpl: List returned for the proxy nodes is null, return empty list

Seems to be a database problem? Does anyone knows if it is possible to repair this?

0 Kudos
JedB
Contributor
Contributor

The VMware support contacted me this week regarding my error with the following email:

----------------------------------------------------------------------------

In reviewing the logs, we can see the below error, quite a few time:

Caught Exception :  Exception : org.apache.axis.AxisFault Message : ; nested exception is:

  1. javax.net.ssl.SSLHandshakeException: Unsupported curve: 1.2.840.10045.3.1.7 StackTrace :

The below KB deals with this issue:

Communication fails in vSphere Data Protection with vCenter Server 5.5 Update 3 (2146825)

http://kb.vmware.com/kb/2146825

This KB works for other versions, not just VDP 6.1

------------------------------------------------------------------------------------------

I was not able to apply the hotfix successfully. There was always an error during the installation.


Yesterday I connected via webex to the VMware support. After two hours of troubleshooting we decided to deploy a new VDP. VMware recommends to install VDP appliance version 6.1.3 which is compatible with my vCenter server 5.5. Now it works!


0 Kudos