On Feb 10, 2017, at 12:14 PM, Dean E. Weimer <dweimer AT dweimer DOT net> wrote:

On 2017-02-10 10:47 am, Dan Langille wrote:

On Feb 10, 2017, at 11:45 AM, Dean E. Weimer <dweimer AT dweimer DOT net> wrote:

On 2017-02-10 10:02 am, Dan Langille wrote:

NOTE: this message is not about resolving the permissions error.  It is about [what appears to be] a DNS issue.

 

Please help me understand which hostname is not being resolved in these messages.  My checks with dig to verify DNS have found no errors.

 

I have checked:

 

Client:                 crey-fd

Read Storage:           "bacula-sd-01-file" 

Write Storage:          "tape01" (From Job resource)

 

I've checked the bacula configuration files, looked for the Address, and run 'dig +short' on the hostname

 

Then, with the IP address from the previous dig, I do 'dig +short -x'.  I get the original hostname.

 

Ideas please?

 

 

Dan, unfortunately this isn't solution to your problem, but I can say, your not alone I have had periodic issues with Bacula failing to resolve host names on FreeBSD. I just gave up and went to IP Addresses. When it occurs it has only been the Bacula process. I have tried testing every which way I can from the OS and always received successful resolution of names. I have had it do it after running fine for several days, then without a reboot, service restart or anything just start failing to resolve. Rebooting server sometimes would fix it, but sometimes it wouldn't, even removed Bacula and reinstalled once without it fixing the problem.

 

I just upgraded my home Bacula server to 7.4.5 this morning and after seeing this, tried switching one of my clients over to name instead of of IP and it did resolve ok and check status of that client. Then checked with my storage daemon switched to name as well. So it doesn't seem to be the latest update that broke your system, perhaps you found that same bug I have periodically ran into, but not found a solution to yet.

 

On the server in question, are you using unbound?  I've found that the SD in question is using unbound, running FreeBSD 11, and there is a DNS issue on that host.

-- 

Dan Langille - BSDCan / PGCon

dan AT langille DOT org

 

I have had it occur on two separate servers, my home Server and one at work. Both installations are fairly small, only backing up my other FreeBSD servers at work since they aren't supported by our main Tivoli installation. Can't say for sure when it occurred the first time, At least since October of 2015, that's the oldest date time of last modified on my client configuration files, and it has a commented out Address= line with hostname followed by a replacement line with IP. can't remember which version of FreeBSD was at that time and when the switch to Unbound occurred in base.

 

We have two larger installations at work running in remote facilities that are on Linux, and haven't had the issue. However they are also older versions of Bacula as the Linux distributions they are running don't have the latest in their package management systems. They were installed on Linux to hopefully simplify a possible upgrade to Bacula Enterprise in the future. However management has turned down the budget item the every year, and my personal (likely biased view/opinion) of FreeBSD being better keeps making me want to switch them over..

 

I will switch my home system over to names, to see if I can get it to occur again and possible find something to help troubleshoot it with, but it may take a while to occur.