Am 13.01.2019 um 04:52 schrieb 권순혁: > I am using bacula9 and I can backup it locally, but if I install fd to > another server and start backup, I can communicate with fd. What can I > identify and solve?
The messages you posted don't look like a complete and unaltered excerpt from your log, but from what I see the trouble is with communication to the SD, not to the FD. > JobId 50: Error: bsockcore.c:285 gethostbyname() for host "slave" > failed: ERR=Name or service not known > > Master JobId 50: Fatal error: job.c:2138 Failed to connect to Storage > daemon: slave:9103 This line seems to say that "master" (apparently the other server you're trying to back up) fails to connect back to the SD on "slave" (apparently your Bacula server). Can "master" resolve the name "slave" correctly?. > slave-dir JobId 50: Fatal error: Bad response to Storage command: wanted > 2000 OK storage > > , got 2902 Bad storage This confirms that the trouble is with the storage, not the file daemon. > 13-Jan 12:42 slave-dir JobId 50: Error: Bacula slave-dir 9.4.1 (20Dec18): > > > > Build OS: x86_64-pc-linux-gnu redhat Enterprise release > > JobId: 50 > > Job: test_job.2019-01-13_12.42.50_16 > > Backup Level: Full > > Client: "master" 9.4.1 (20Dec18) > x86_64-pc-linux-gnu,redhat,Enterprise release This confirms that the director was able to contact the FD, otherwise it couldn't display the version information. _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
