Am Dienstag, 9. April 2019 14:16:50 UTC+2 schrieb Erik Šolc:
> On Tuesday, April 9, 2019 at 1:59:51 PM UTC+2, Dat Nguyen wrote:
> > Am Dienstag, 9. April 2019 13:00:06 UTC+2 schrieb Erik Šolc:
> > > > 
> > > > I did it the hard way and give all config files 777 and owner 
> > > > bareos:bareos, so this shouldn't be the problem i guess
> > > 
> > > So the versions are the same? 18.2 also on client?
> > > what does director shows in bconsole when you run status 
> > > client=your_client ?
> > 
> > Hi, server and client are on version 18.2.
> > 
> > Bconsole with status client=my_client:
> > 
> > 
> > *status client=*CLIENT*.local
> > Connecting to Client *CLIENT*.local at 10.100.0.73:9102
> >  Handshake: Cleartext, Encryption: None
> > 
> > *CLIENT*.local Version: 18.2.5 (30 January 2019)  Linux-4.4.92-6.18-default 
> > redhat Red Hat Enterprise Linux Server release 7.0 (Maipo)
> > Daemon started 09-Apr-19 10:46. Jobs: run=0 running=0, bareos.org build 
> > binary
> >  Heap: heap=135,168 smbytes=22,940 max_bytes=23,329 bufs=65 max_bufs=68
> >  Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s
> > 
> > Running Jobs:
> > bareos-dir (director) connected at: 09-Apr-19 13:54
> > No Jobs running.
> > ====
> > 
> > Terminated Jobs:
> >  JobId  Level    Files      Bytes   Status   Finished        Name
> > ======================================================================
> > 174061  Incr        686    12.37 G  OK       11-Oct-18 21:21 *CLIENT*
> > 174127  Incr          0         0   OK       11-Oct-18 22:03 
> > *CLIENT*-database
> > 174233  Incr        723    13.84 G  OK       12-Oct-18 21:57 *CLIENT*
> > 174299  Incr          0         0   OK       13-Oct-18 00:12 
> > *CLIENT*-database
> > 174405  Incr        666    11.43 G  OK       13-Oct-18 21:07 *CLIENT*
> > 174471  Full          0         0   OK       13-Oct-18 23:38 
> > *CLIENT*-database
> > 174577  Incr        746    13.97 G  OK       14-Oct-18 22:01 *CLIENT*
> > 174643  Incr          0         0   OK       15-Oct-18 00:22 
> > *CLIENT*-database
> > 174841  Full     66,868    58.53 G  OK       16-Oct-18 06:32 *CLIENT*
> > 174842  Incr        817    19.39 G  OK       16-Oct-18 07:42 *CLIENT*
> > ====
> > 
> > 
> > 
> > As we can see, there were jobs that went well. a while a go...
> > Never changed config files.
> > Communication between SD and DIR , DIR and FD is good.
> > Is it possible to test communication between FD and SD?
> 
> One more thing, I dont see any plugin info (python-fd.so). Could you try to 
> install package bareos-vmware-plugin-compat? 
> In documentation "Since Bareos Version >= 17.2.4 the module_path is without 
> vmware_plugin directory."
> Nothing else comes to my mind.
> 
> Erik

I installed bareos-vmware-plugin-compat restarted DIR and rerun the job.

Bareos Log:

09-Apr 10:39 bareosdir JobId 199361: Fatal error: Socket error on Storage 
command: ERR=No data available
09-Apr 10:39 bareosdir JobId 199361: Fatal error: Network error with FD during 
Backup: ERR=No data available
09-Apr 10:39 bareosdir JobId 199361: Fatal error: No Job status returned from 
FD.


Socket error on Storage is new to me 

-- 
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 [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to