> Just as I thought I'm ready for prime time, I'm back to square one with TWO > unexpected issues that popped up. > > # bconsole Director authorization problem: > After upgrading to 2.2.6 I noticed I get failures time to time when I issue > the bconsole command. Following is what I see from my CLI. > Connecting to Director nfsserver:9101 > Director authorization problem. > Most likely the passwords do not agree. > If you are using TLS, there may have been a certificate validation error > during the TLS handshake. > Following is what I got in my email alert. > 15-Nov 07:53 nfsserver-dir: ERROR in authenticate.c:380 Unable to > authenticate console "*UserAgent*" at client: 192.168.15.34:36131. > The ip 192.168.15.34 is where I have my Bacula DIR & SD services running. > > After Bacula dir, fd and sd daemons are restarted, "bconsole" will work a > number of times and then all of a sudden the connection fails. Please note I > didn't modify ANY entries in any of the DIR, FD or SD conf files. > What version of bacula did you upgrade from?
Are you sure you do not have network communications problems (faulty NIC/ switch). I ask that because both problems can be caused by a bad network connection. > # Tapes put into read error: > The backups will work perfectly fine for a number of times on the same > tape/Volume from multiple clients through multiple Bacula daemon start/stops > and then all of a sudden slams the working tape/Volume into Error. > You need to post the log or console message when this happens otherwise it will be impossible to help. John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
