This chapter was not yet closed and I have interesting further results
(actually a bug report).
I opened another thread here where bacula-dir was crashing. Today I found the
cause.
A macOS FD was earlier using normal connection from bacula-dir, but later I
adapted it to connect to bacula-dir on
I think it is great support here from you people!
Today I think I might have understood what is happening, and Bill’s
explanations about what might be going on were probably correct in the core,
but not in the details.
Let me try to lay out what I think is going on and where I had my problem
> On Mon, 25 Jul 2022 15:50:15 +, Bill Arlofski said:
>
> On Monday, July 25th, 2022 at 08:54, Martin Simmons =
> wrote:
> >
> > You could try running bacula-fd with debugging output. Unfortunately,
> > it doesn't include timestamps, but you can do it like this:
>
> Hey Martin, Not sure
On Monday, July 25th, 2022 at 08:54, Martin Simmons
wrote:
>
> You could try running bacula-fd with debugging output. Unfortunately,
> it doesn't include timestamps, but you can do it like this:
Hey Martin, Not sure if this is recent or not, but:
8<
$ /opt/comm-bacula/sbin/bacula-fd -?
C
You could try running bacula-fd with debugging output. Unfortunately, it
doesn't include timestamps, but you can do it like this:
bacula-fd -d50,scheduler -f -v ...your normal bacula-fd args... | perl -pe
'use POSIX strftime; print strftime "[%Y-%m-%d %H:%M:%S] ", localtime'
That might show ex
The last two scheduled runs of the job again had the connection errors (and
again the the backup was still taken fine). yesterday I even ran the longer
running job a few hours ahead to see if this was the reason why the connection
error disappeared the other night - but that was not it. Also com
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
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
Hello Justin,
My guess is that the FD is configured to call the Director, and it tries, but
fails either due t
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
Can you show the whole log line where this is displayed?
Curious to know if it is coming from the FD called `r
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 dail
20 matches
Mail list logo
