Phil Stracchino <alaric <at> metrocast.net> writes: > > I have an OpenBSD 4.6 client upon which the Bacula 5.0.3 client works > perfectly, and has worked perfectly since 5.0.3. I've just upgraded my > servers from 5.2.6 to 5.2.9, and realized I hadn't updated the OpenBSD > client in a while. So I went and updated it to 5.2.9, only to find that > nothing can connect to the 5.2.9 client. It starts, it listens on port > 9102, but all connection attempts fail. It's not a password problem, I > haven't changed the config file at all. I tried both static and dynamic > builds, and got the exact same behavior. > > Is anyone else encountering similar problems on OpenBSD 4.6 or versions > in that general range? > 5.2.7 added support for getaddrinfo and as it seems that finds a lot more addresses then good old gethostbyname.
You might be bitten by http://bugs.bacula.org/view.php?id=1897 which states ipv6 but is a problem that getaddrinfo finds multiple the same addresses for your host and as such all daemons try to listen multiple times on the same port. Which of course is kind of lame. Simple test is to change the config.h autogenerated by configure and change the HAVE_GET_ADDRINFO to undefined and then get the old gethostbyname. Or wait for a patch that I'm working on. What is kind of interesting is running any daemon with -d 100 to see what addresses it want to bind to. It could also bee something else then a bug report should be made with some debugging info. Marco ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
