Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a Bacula setup with 9 clients, and it's working happily. Today I had to add another client, so I went and copied+adapted the existing configuration files from another client, but when I schedule a job for the new client, I get these errors:

20-Mar 17:50 tools-dir JobId 39: Start Backup JobId 39, Job=BackupPresenze2.2012-03-20_17.50.49_04
20-Mar 17:50 tools-dir JobId 39: Using Device "FileStorage"
20-Mar 17:50 presenze2-fd JobId 39: Fatal error: Failed to connect to Storage daemon: bacula.mylan.local:9103
20-Mar 17:50 tools-dir JobId 39: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage

From the client I can telnet to bacula.mylan.local:9103 just fine, and jobs for other clients work successfully... What could I check?
(Server and client run Ubuntu 10.04, if it's relevant)

share|improve this question

1 Answer 1

up vote 3 down vote accepted

It looks like it was a "slow DNS" kind of problem... I added the hostname to /etc/hosts and now Bacula works happily.

share|improve this answer
1  
Thanks for replying back when you fixed. Helped me out :) –  user3227965 May 19 at 10:36
1  
In my case I used an external DNS-server on the file-deamon-machine which doesn't know about the internal DNS-zone (and therefore the information about the storage-daemon). I got the DNS-response "NXDONAIN" while using nslookup to verify the IP-address. After adding the IP/FQDN-combination of the storage-daemon in the /etc/hosts-file on the file-daemon-machine nslookup's response is still "NXDOMAIN" but ping works and bacula also. Thanks to the answer from "Joril" (above) which gaves the clue to fix my problem. –  Martin Sep 25 at 5:57

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.