> On 20. Jul 2022, at 12:06, Martin Simmons <mar...@lispworks.com> wrote:
>
> There are two levels of error here: firstly, the "Connection refused" occurs
> when the client tries to connect to the Director; then that eventually
> succeeds and the error message is sent back to the Director when it doesn't
> expect it which leads to the "Malformed message" error.
>
> Does the client machine have permanent access to the Director machine (via the
> firewall)? It looks to me like it might only have intermittent access, so
> gets "Connection refused" for some time before it connects.
It has permanent access. However, the machine running the Dir and SD is busy
with local FD jobs (as in “Dir, SD and FD on same host”) when also the jobs for
remote FDs are initiated. The jobs I had so far for remote hosts just waited
with a cogwheel showing in Baculum. The job for the FD with ConnectToDirector
also shows the cogwheel, but it seems at the point in time when its turn has
come, the connection messages are occuring.
> Alternatively, does "bacula-dir.lan.net" resolve to more than one address on
> the client machine? If so, maybe some of the addresses fail to connect.
Nope. This is a CNAME and it resolves to exactly 1 FQDN and exactly 1 IP
address.
> Also, does "(FD 13)" and "Director (11)" mean that the client machine is
> running Bacula version 13 and the Director is running Bacula version 11?
This.
> That
> is not a supported configuration (it must be Director = Storage >= Client).
Oh well I did not know this. Then I would have to go down to 11 for this FD.
Will do so later today.
>
> __Martin
>
>
>>>>>> On Wed, 20 Jul 2022 00:55:56 +0200, Justin Case said:
>>
>> Hi all
>>
>> I have a client machine (FD 13) in a firewalled admin network that cannot be
>> connected to by the Director (11), so it is using ConnectToDirector = yes,
>> i.e the FD connects through the firewall to the Director.
>>
>> The client machine is backed up to two different tiers, so there are two
>> daily jobs backing up the machine.
>> The backup to both tiers works fine, - however:
>>
>> the first backup generates a larger number of error messages before it
>> starts:
>>
>> Error: getmsg.c:217 Malformed message: [bsockcore.c:265 Unable to connect to
>> Director daemon on bacula-dir.lan.net:9101. ERR=Connection refused
>>
>> Then the backup runs through fine, it says it terminates with warnings
>> (although there are NO warnings in the log, but the aforementioned errors)
>>
>> Termination: Backup OK -- with warnings
>>
>> The second backup later runs though without those errors.
>>
>> It looks to me like the FD was initially not connected to the director, but
>> then it it does successfully connect. I am not sure if this is the correct
>> interpretation.
>>
>> Generally its not nice to have errors in the log as I need to check for them
>> every day..
>>
>> Is there a way to better configure the FD or DIrector so that the errors do
>> not occur?
>>
>>
>> The FD config:
>>
>> Director {
>> Name = bacula-dir
>> Password = “redacted"
>> # DirPort = 9101
>> Address = bacula-dir-redacted
>> ConnectToDirector = yes
>> ReconnectionTime = 40 min
>> }
>>
>> FileDaemon { # this is me
>> Name = redacted
>> # FDport = 9102 # where we listen for the director
>> WorkingDirectory = /var/lib/bacula
>> Pid Directory = /run/bacula
>> Maximum Concurrent Jobs = 20
>> Plugin Directory = /usr/lib/bacula
>> # FDAddress = 127.0.0.1
>> }
>>
>>
>>
>>
>> _______________________________________________
>> 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
