Hello all, At my work we have a Bareos 20.0.1 server on RHEL 7.9. We're about to decommission the last of our Solaris systems and and wanted to do one final full backup before we turn them off for good.
Our Bareos administrator did a final backup of our two remaining Solaris 11.4 systems already using the Bareos 20.0.0.1-1 pkg for Solaris 11.4. So far so good. However, we also have a few Solaris 10 1/13 systems, so I compiled & built Bareos 17.2.4 on them. (Most recent version I could get to easily compile.) But when our Bareos administrator tried to back them up, it failed. The error messages were: *2021-08-10 02:45:55 bareos-dir JobId 6801: Fatal error: No Job status returned from FD.* *2021-08-10 02:45:55 bareos-dir JobId 6801: Fatal error: Unable to authenticate with File daemon at "[IP]:9102"* *2021-08-10 02:45:50 bareos-dir JobId 6801: Fatal error: Wrong format of the CRAM challenge with [IP].* *2021-08-10 02:45:45 bareos-dir JobId 6801: TLS negotiation failed (while probing client protocol)* The Bareos admin thinks that it's because OpenSSL on the Solaris 10 systems is too old, despite being patched with the very latest Oracle Solaris 10 patches for OpenSSL. That's probably true, so I'm wondering if we have any options here. Is there a way to* turn off TLS* and/or *not use an MD5 password* *on a per-client basis*, so we can just enable it for these 3 remaining Solaris 10 systems and then remove them all from the Bareos config if it successfully completes a full backup after that? Thanks for any replies. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/6f047881-5dcd-4a23-99b7-ac0f660fc196n%40googlegroups.com.
