Hi there
Just a followup
I never managed to find out what was causing this problem but found that the
following changes solved the issue.
client bacula-fd - updated FDAddress = FQDN (from ip address)
Bacula server updated the client record to use the same FQDN (again replacing
the ip address)
Thanks to everybody who offered any advice or suggestions.
Brad
- Original Message -
step 3.: "Mac"
To: "Josh Fisher"
Cc: bacula-users@lists.sourceforge.net
Sent: Tuesday, 3 December, 2019 4:17:35 PM
Subject: Re: [Bacula-users] Sudden error on Bacula client 7.4.4
Hi Josh
Thank you for your reply and advice
I have checked again and there is nothing using that port.
I have also tried changing the port but bacula-fd still fails to bind to the
new port with the same error message.
Kind Regards
Brad
- Original Message -
step 3.: "Josh Fisher"
Cc: bacula-users@lists.sourceforge.net
Sent: Tuesday, 3 December, 2019 3:47:37 PM
Subject: Re: [Bacula-users] Sudden error on Bacula client 7.4.4
On 12/2/2019 2:29 PM, Brad Sales and Support wrote:
> Hi Josh
>
> Thank you for your suggestion - the port is open - Second thing I tried
> was temporarily disabling my firewall.
>
> All I can think of is that one of the files has become corrupt - possibly
> due to the client vm having an issue during a routine backup
I don't know. It still seems like something is amiss in the networking
config, because I believe that error means that the bind() call failed
when bacula-fd attempted to bind to the configured addr:port. With
bacula-fd stopped, does netstat -nlt show some other app, (perhaps a
bacula-fd zombie process), bound to TCP port 9102 on ANY interface?
>
>
> Kind Regards
> Brad
>
> - Original Message -
> step 3.: "Josh Fisher"
> To: "Mac"
> Cc: bacula-users@lists.sourceforge.net
> Sent: Monday, 2 December, 2019 7:01:00 PM
> Subject: Re: [Bacula-users] Sudden error on Bacula client 7.4.4
>
>
> On 12/2/2019 11:46 AM, Mac wrote:
>> Hi Josh
>>
>> Thank you for your suggestion
>>
>> This vm is a web server and all sites use remote DNS - everything else is
>> working as expected.
>>
>> interfaces - is all correct.
>>
>> So I do not this is an ip address issue.
>
> Then are there iptables rules on the VM blocking bacula-fd's port (TCP
> 9102)?
>
>
>> Jose
>>
>> This is an unmanaged vps from a host - I have two vps's from them and the
>> other one is working as expected
>>
>> I have already checked with the host if they were possibly blocking port
>> 9102 - I have also tried changing the port. They are not blocking the port
>> and another port also failed.
>>
>> Kind regards
>> Brad
>>
>> - Original Message -
>> step 3.: "Josh Fisher"
>> To: bacula-users@lists.sourceforge.net
>> Sent: Monday, 2 December, 2019 3:15:42 PM
>> Subject: Re: [Bacula-users] Sudden error on Bacula client 7.4.4
>>
>>
>> On 12/2/2019 7:49 AM, Mac wrote:
>>> Hi Martin
>>>
>>> Thank you for your reply and suggestion.
>>>
>>> Yes I do have the ip address hardwired - No it has not changed.
>> Does 'ip addr show' show that that IP address is bound to the (correct)
>> interface?
>>
>>
>>> The vm configuration is also not unique and I have a few other vm all
>>> configured the same way who's Bacula clients are all working as expected.
>>>
>>> Anything else I can look at?
>>>
>>> Kind Regards
>>> Brad
>>>
>>>
>>> - Original Message -
>>> step 3.: "Martin Simmons"
>>> To: "Mac"
>>> Cc: bacula-users@lists.sourceforge.net
>>> Sent: Monday, 2 December, 2019 12:24:58 PM
>>> Subject: Re: [Bacula-users] Sudden error on Bacula client 7.4.4
>>>
On Mon, 2 Dec 2019 10:52:56 + (GMT), Mac said:
Hi there
I have a client on a Debian 9 vm that has been working perfectly for 18
months.
I have just received an error on bconsole that the scheduled backup failed.
I have done all the standard operations including full reboot of the vm.
The Client come online after a restart for a short time showing this error
(status)
**
Warning: Cannot bind port 9102: ERR=Cannot assign requested address:
Retrying ...
>>> This error is:
>>>
>>> EADDRNOTAVAIL
>>> A nonexistent interface was requested or the requested
>>> address was not local.
>>>
>>> Do you have the client's IP address hardwired in the bacula-fd.conf on the
>>> vm?
>>> If so, is it the correct IP address (maybe the vm's IP address has changed)?
>>>
>>> __Martin
>>>
>>>
>>> ___
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>
>> ___
>> Bacula-users mailing list
