Hello Community, our daemon log is flooded from these, although we switched off TLS on client and director side. To the developers: It would be really helpful to add my suggestions below.
bareos-dir: lib/bnet.cc:122 TLS Negotiation failed. [...] bareos-dir: Connect failure: ERR=error:14201076:SSL routines:tls_choose_sigalg:no suitable signature algorithm [...] bareos-dir: lib/bnet.cc:122 TLS Negotiation failed. It took me almost one day to figure out, that it was a DNS cache problem. After switching to IPs, everything is fine. A hint, with quoting the error test in https://docs.bareos.org/TasksAndConcepts/TransportEncryption.html, would be an excellent point to avoid others to run into the same issue. Please point out, that there is a DNS cache on mostly all systems. On Linux: sudo systemd-resolve --flush-caches / sudo resolvectl flush-caches: By the way: It would be really helpfully, when there would be an error message besides "*bareos-dir: lib/bnet.cc:122 TLS Negotiation failed.*”! Better would be: *" bareos-dir: lib/bnet.cc:122 TLS Negotiation from director god.example.net to storage eden.example.net failed.*" But maybe the code from community edition to subscription differs... Best regards Joerg -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/6c1d43dd-03e3-4de3-b6d1-1218c6246054n%40googlegroups.com.
