This might be a bit outdated but we had the exact same error messages
and finally drilled it down to an SSL issue with urllib3 that
was always complaining about insecure requests. Assume that warning
spoiled the result output from the cbt_tool.
After a rough and dirty deletion (not recommended) of the appropriate
section in file
/usr/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py
the backup of my VMs runs smoothly. 

Am Freitag, 18. Dezember 2015 15:05:33 UTC+1 schrieb Sylvain Donnet:
> Le jeudi 3 décembre 2015 09:38:39 UTC+1, Sylvain Donnet a écrit :
> > Hi,
> > 
> > I have installed the Vmware plugin, and it seems operational. But when I 
> > test it, on several VM with CBT enabled, I got the following error :
> > 
> > Fatal error: Traceback (most recent call last):
> >   File "/usr/lib/bareos/plugins/BareosFdWrapper.py", line 42, in 
> > start_backup_file
> >     return bareos_fd_plugin_object.start_backup_file(context, savepkt)
> >   File "/usr/lib/bareos/plugins/vmware_plugin/BareosFdPluginVMware.py", 
> > line 160, in start_backup_file
> >     if not self.vadp.get_vm_disk_cbt(context):
> >   File "/usr/lib/bareos/plugins/vmware_plugin/BareosFdPluginVMware.py", 
> > line 887, in get_vm_disk_cbt
> >     changeId=cbt_changeId)
> >   File "/usr/lib/python2.7/dist-packages/pyVmomi/VmomiSupport.py", line 
> > 566, in <lambda>
> >     self.f(*(self.args + (obj,) + args), **kwargs)
> >   File "/usr/lib/python2.7/dist-packages/pyVmomi/VmomiSupport.py", line 
> > 375, in _InvokeMethod
> >     return self._stub.InvokeMethod(self, info, args)
> >   File "/usr/lib/python2.7/dist-packages/pyVmomi/SoapAdapter.py", line 
> > 1301, in InvokeMethod
> >     raise obj # pylint: disable-msg=E0702
> > vim.fault.FileFault: (vim.fault.FileFault) {
> >    dynamicType = <unset>,
> >    dynamicProperty = (vmodl.DynamicProperty) [],
> >    msg = u'Erreur provoqu\xe9e par le fichier 
> > /vmfs/volumes/19536d18-6870b949/vm124.ddo.net_1/vm124.ddo.net.vmdk',
> >    faultCause = <unset>,
> >    faultMessage = (vmodl.LocalizableMessage) [],
> >    file = 
> > '/vmfs/volumes/19536d18-6870b949/vm124.ddo.net_1/vm124.ddo.net.vmdk'
> > }
> > 
> > "msg" could be translated by "error coming from the file ..."
> > 
> > The plugin setup is good, as it has found the vCenter and the VM.
> > Other VMs generate also this kind of message.
> > I have checked that these VM are really CBT enabled.
> > 
> > Any idea ?
> > 
> > BR
> > 
> > Sylvain
> 
> Seems to be the real problem. Yes, our Vmware datastores are NFS-based.
> 
> Is there a workaround, or will be a fix for the plugin ?

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to