I cannot for the life of me figure this one out. I am running bacula 2.2.4 with patches:
2.2.4-poll-mount.patch 2.2.4-restore.patch 2.2.4-sd-auth-fail.patch 2.2.4-verify.patch My backup server and the client I'm having issues with are centos 4.5 with 2.6.9-55.0.9.ELsmp. I am running bacula over a private network. I am able to connect to the client from the backup server via ssh. There is no firewall between the client and the server, and I disabled iptables. I checked the director passwords, and even copied the bacula-fd.conf from another client that is working fine. I also rebuild bacula on my server and the client. I have 10 clients now, they are all over the same network setup in the same way, and this is the only one that just won't work. This client was working with bacula-2.2.0, but I just upgraded to bacula-2.2.4 and it hasn't worked since. I tried to revert back to 2.2.0 and that didn't solve the issue either. I am able to connect from the client to the bconsole on the server. Here is an attempt to connect from the server to the client via telnet over port 9102: [EMAIL PROTECTED] ~]# telnet 192.168.1.162 9102 Trying 192.168.1.162... Connected to nattybo-i (192.168.1.162). Escape character is '^]'. Connection closed by foreign host. Client output during telnet, it seems to see the server (.151): [EMAIL PROTECTED] bacula]# netstat -pant | grep 9102 tcp 0 0 0.0.0.0:9102 0.0.0.0:* LISTEN 24175/bacula-fd tcp 0 0 192.168.1.162:9102 192.168.1.151:32812 TIME_WAIT - [EMAIL PROTECTED] ~]# telnet 0 9102 Trying 0.0.0.0... Connected to 0 (0.0.0.0). Escape character is '^]'. <<Connects just fine>> >From bconsole on the server, status: Select Client (File daemon) resource (1-10): 7 Connecting to Client nattybo-fd at 192.168.1.162:9102 Failed to connect to Client nattybo-fd. ==== 08-Oct 14:28 backup1-dir: -Console-.2007-10-08_14.28.30 Fatal error: Unable to authenticate with File daemon at "192.168.1.162:9102". Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the FD or FD networking messed up (restart daemon). Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors for help. Client bacula-fd.conf file: Director { Name = backup1-dir Password = "RHqexkjps8NywXP3xi15yTooF6pU0zQVviDUwiHc+1TC" } Director { Name = backup1-mon Password = "LY/hERpxTupJxwYV1QC8lMYJMruclkIdMJJEmRQT0GaX" Monitor = yes } Name = nattybo-fd WorkingDirectory = /var/bacula Pid Directory = /var/run Maximum Concurrent Jobs = 1 } Messages { Name = Standard director = nattybo-dir = all, !skipped, !restored } Server bacula-dir.conf snipets: Director { # define myself Name = backup1-dir DIRport = 9101 # where we listen for UA connections QueryFile = "/etc/bacula/query.sql" WorkingDirectory = "/home/bacula/working" PidDirectory = "/var/run" Maximum Concurrent Jobs = 2 Password = "H4POezITf8d0fkdx3aKJXI602eebG5+wqrDCuP5Fpxtm" # Console p assword Messages = Daemon } Job { Name = "nattybo" Client = nattybo-fd JobDefs = "Full Backups" FileSet = "DB_Server" Storage = Dump1 Write Bootstrap = "/home/bacula/working/nattybo.bsr" } Client { Name = nattybo-fd Address = 192.168.1.162 FDPort = 9102 Catalog = MyCatalog Password = "RHqexkjps8NywXP3xi15yTooF6pU0zQVviDUwiHc+1TC" # password for FileDaemon File Retention = 14 days # 30 days Job Retention = 6 months # six months AutoPrune = yes # Prune expired Jobs/Files } Any ideas??? Thanks, Megan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
