On Sun, 2009-12-06 at 17:41 -0700, Craig White wrote: > On Sat, 2009-12-05 at 13:24 -0500, John Drescher wrote: > > > I've been all through the documentation and I was sure I set up things > > > correctly. > > > > > > Server is CentOS-5 built 3.0.3 > > > Client is Macintosh built 3.0.3 > > > > > > Server can telnet to client port 9102 > > > Client can telnet to server port 9103 > > > > > > Server can back itself up and passes tests including autochanger. > > > > > > I know firewalls are not the issue and that the client fd is running and > > > if I stop the client-fd, I cannot telnet to the client on port 9102 > > > > > > Because I read that the storage daemon must be resolvable by the client, > > > I am using an fqdn that is internally resolvable by both server and > > > client from intranet dns server (represented as FQDN) > > > > > > Director calls itself... > > > Director { > > > Name = SRV1-dir > > > DIRport = 9101 > > > QueryFile = "/etc/bacula/query.sql" > > > WorkingDirectory = "/var/lib/bacula" > > > PidDirectory = "/var/run" > > > SubSysDirectory = "/var/lock/subsys" > > > Maximum Concurrent Jobs = 1 > > > Password = "password" > > > Messages = Standard > > > } > > > > > > Director says about client... > > > Client { > > > Name = ja > > > Address = 192.168.1.18 > > > FDPort = 9102 > > > Catalog = MyCatalog > > > Password = "password" > > > File Retention = 75d > > > Job Retention = 75d > > > AutoPrune = yes > > > } > > > > > > Director says about storage... > > > Storage { > > > Name = FQDN-sd > > > Address = 127.0.0.1 > > > SDPort = 9103 > > > Password = "password" > > > Device = LTO-4 > > > Media Type = LTO-4 > > > } > > > > > You should not have 127.0.0.1 in any bacula configuration file unless > > you are using ssh tunnels . > ---- > my problem seems to be with ipv6 > > If I launch the Macintosh client in the default manner... > > launchctl unload -w /Library/LaunchDaemons/org.bacula.bacula-fd.plist > > I can connect to the client's fd but cannot communicate with it and I > can see both an ipv4 and ipv6 socket are created on 9102 > # netstat -an|grep 9102 > tcp4 0 0 *.9102 *.* LISTEN > tcp6 0 0 *.9102 *.* LISTEN > > but if I kill that off, and then just launch it via... > > # /usr/local/bacula-3.0.3/etc/bacula-ctl-fd start > > I only get the ipv4 socket / listener > # netstat -an|grep 9102 > tcp4 0 0 *.9102 *.* LISTEN > > and I can use it and back up and everything works so I just need to > adjust the startup script for now but this is not the default and it's > messy. ---- I may need to take this to the bacula developers list but I'm not subscribed and maybe someone on the list understands the Macintosh configuration.
No matter what changes I make to the client's fd.conf file they seem to be ignored... FileDaemon { # this is me Name = Scanner-Power-Mac-G5-fd FDAddresses = { ipv4 = { port = 9102;} } It still starts the daemon with both ipv4 & ipv6 listeners. If I start it manually with the same options in /Library/LaunchDaemons/org.bacula.bacula-fd.plist or /usr/local/bacula-3.0.3/etc/bacula-ctl-fd start or /usr/local/bacula-3.0.3/sbin/bacula-fd \ -c /Library/Preferences/bacula/bacula-fd.conf it reads those options and complies happily This is just not good Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users