Hi Jörg,

Jörg Bernau schrieb am Freitag, 24. Februar 2023 um 19:25:00 UTC+1:

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:

I don't think anyone from the team will take care of that. However, feel 
free to open a PR for that documentation change.


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 <http://god.example.net> to storage eden.example.net 
<http://eden.example.net> failed.*"

That's a good idea. I'm not sure the data you'd want to display here is 
actually present in the location the message is created. Also, feel free to 
propose something in a PR. 
 

But maybe the code from community edition to subscription differs...

That's definietly not the case. The subscription binaries are built from 
the same source code.

Best Regards,
Andreas

-- 
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/74a5ad60-acbc-41d4-8118-19d2bba9bb53n%40googlegroups.com.

Reply via email to