|
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.
| 