Thank you for the feedback and the test, Justin.
AS you can imagine, we need to be 100% sure to clear up all possible questions
to be able to better understand the whole picture.
Plus, it's an interesting topic/issue you have here. :)
Best regards,
Bill
--
Bill Arlofski
w...@protonmail.com
Hey Bill, thanks for spending time on this!
> On 20. Jul 2022, at 21:46, Bill Arlofski via Bacula-users
> wrote:
>
>
> Justin,
>
> I know what you told us, but I think we have a situation that I (and Martin)
> described:
I understand your experiment, but it is not like that here.
> - FD c
Justin,
I know what you told us, but I think we have a situation that I (and Martin)
described:
- FD cannot connect to Director due to firewall
- Director CAN connect to FD (I know, I know... :)
- Job starts, Director connects to FD and receives all the queued "Cannot
connect" messages
- Job
Bill, thanks for clarification. So the problem remains a mystery, so far.
> On 20. Jul 2022, at 21:33, Bill Arlofski via Bacula-users
> wrote:
>
>
>>> It will try to connect every 5 seconds until it succeeds.
>> Why every 5 seconds?
>> The FD config has ReconnectionTime = 40 min
>> Let me rem
It will try to connect every 5 seconds until it succeeds.
Why every 5 seconds?
The FD config has ReconnectionTime = 40 min
Let me remove this clause and restart the FD. Maybe it helps.
Hello Justin,
Don't confuse the two different things.
On startup, the FD will immediately attempt to co
Hi Martin please find my response inline:
> On 20. Jul 2022, at 20:39, Martin Simmons wrote:
>
>> On Wed, 20 Jul 2022 16:25:15 +0200, Justin Case said:
>>
>>> On 20. Jul 2022, at 12:06, Martin Simmons wrote:
>>>
>>> There are two levels of error here: firstly, the "Connection refused" occ
> On Wed, 20 Jul 2022 16:25:15 +0200, Justin Case said:
>
> > On 20. Jul 2022, at 12:06, Martin Simmons 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
> On 20. Jul 2022, at 12:06, Martin Simmons 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 w
inline response continued:
> On 20. Jul 2022, at 01:38, Bill Arlofski via Bacula-users
> wrote:
>
> On 7/19/22 16:55, Justin Case wrote:
>> Error: getmsg.c:217 Malformed message: [bsockcore.c:265 Unable to connect to
>> Director daemon on bacula-dir.lan.net:9101. ERR=Connection refused
>
>
>
Thanks for your interest, Bill, I will respond to your requests inline:
> On 20. Jul 2022, at 01:11, Bill Arlofski via Bacula-users
> wrote:
>
> On 7/19/22 16:55, Justin Case wrote:
> >
>> Error: getmsg.c:217 Malformed message: [bsockcore.c:265 Unable to connect to
>> Director daemon on bacula
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 ma
11 matches
Mail list logo
