Thanks, I will do these debugging steps. Yes, I have already checked the things suggested. I downgraded back to 9.6.5 and I still have the error.
Now for a slightly different Q: How do I set command-line options for the bacula director? My installation lacks systemd integration, which is problematic: It never restarts on boot, and I have to start it with the manual bespoke scripts in /opt/bacula, and I don't have the expertise or wherewithal to wrestle with systemd long enough to create a service unit file of my very own. Bacula should be doing that automatically in the installation, it's not my job! Robert On Tue, Apr 6, 2021 at 10:50 AM Martin Simmons <mar...@lispworks.com> wrote: > >>>>> On Mon, 5 Apr 2021 01:27:07 -0700, Robert Earl said: > > > > I recently upgraded Bacula from 9.6.5 to 9.6.7 on the director host. Now > I > > have received an authentication error when running backups on my client > > Fedora machine. > > > > aten-dir JobId 3491: Start Backup JobId > 3491,Job=matthew-Backup.2021-04-05_01.22.01_26 > > aten-dir JobId 3491: Using Device "FileStorage" to write. > > aten-dir JobId 3491: Fatal error: Unable to authenticate with File > daemon at "matthew-vpn.spiritus.cox.net:9102". Possible causes: > > Passwords or names not the same or > > Maximum Concurrent Jobs exceeded on the FD or > > FD networking messed up (restart daemon). > > For help, please see: > > > http://www.bacula.org/rel-manual/en/problems/Bacula_Frequently_Asked_Que.html > > Did you check these things? > > If so, try running the Director and the FD with debug level 50 to see what > messages are being sent. E.g. restart the daemons with arguments -f -d50 > added to the normal command line. > > > > aten-dir JobId 3491: Fatal error: No Job status returned from FD. > > aten-dir JobId 3491: Error: Bacula aten-dir 9.6.7 (10Dec20): > > Build OS: x86_64-pc-linux-gnu ubuntu 18.04 > > JobId: 3491 > > Job: matthew-Backup.2021-04-05_01.22.01_26 > > Backup Level: Full > > Client: "matthew-fd" 9.6.6 (20Sep20) > x86_64-redhat-linux-gnu-bacula,redhat,One) > > FileSet: "Matthew Set" 2021-04-05 00:58:25 > > Pool: "File" (From Command input) > > Catalog: "matthew-Catalog" (From Client resource) > > Storage: "File" (From Command input) > > Scheduled time: 05-Apr-2021 01:22:01 > > Start time: 05-Apr-2021 01:22:03 > > End time: 05-Apr-2021 01:22:14 > > Elapsed time: 11 secs > > Priority: 10 > > FD Files Written: 0 > > SD Files Written: 0 > > FD Bytes Written: 0 (0 B) > > SD Bytes Written: 0 (0 B) > > Rate: 0.0 KB/s > > Software Compression: None > > Comm Line Compression: None > > Snapshot/VSS: no > > Encryption: no > > Accurate: no > > Volume name(s): > > Volume Session Id: 6 > > Volume Session Time: 1617609357 > > Last Volume Bytes: 1,880,205,247 (1.880 GB) > > Non-fatal FD errors: 1 > > SD Errors: 0 > > FD termination status: Error > > SD termination status: Waiting on FD > > Termination: *** Backup Error *** > > > > > > The bizarre thing now is that the log reports file director version > 9.6.6, > > but the FD actually running on matthew is 9.6.7, double-checked and > > verified against packages and command output. So would a 9.6.6 client FD > > cause this error, and where could it be lurking? > > Did you upgrade the FD as well? The job log will report the last known > version of the FD, which will be the previous version if the authentication > fails. > > __Martin > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
