On Wed, Jan 5, 2022 at 6:53 AM Graham Sparks wrote:
> I've just checked the "Privacy" screen and I actually have "bacula-fd",
> "bacula", "bconsole" AND "sh" in the Full Disk Access list. I probably
> shouldn't have "sh" in that list. That might actually be worse than your
> suggestion to run "
___
From: David Brodbeck
Sent: 05 January 2022 00:19
To: Graham Sparks
Cc: bacula-users
Subject: Re: [Bacula-users] Packet size too big (NOT a version mismatch)
On Tue, Jan 4, 2022 at 4:56 AM Graham Sparks
mailto:g...@hotmail.co.uk>> wrote:
I've personally not run in to problems
On 1/4/22 17:18, Stephen Thompson wrote:
>
> Thanks Bill, you nailed it.
>
> 04-Jan-2022 16:13:52 FD: backup.c:1356-884680
> fname=/Users/USER/Library/Containers/com.apple.Safari.CacheDeleteExtension
> snap=/Users/USER/Library/Containers/com.apple.Safari.CacheDeleteExtension
> link=/Users/USER/Lib
On Tue, Jan 4, 2022 at 4:56 AM Graham Sparks wrote:
> I've personally not run in to problems with System Integrity Protection,
> although I do give the bacula-fd executable "Full Disk" permissions.
>
What I find is bacula-fd is unable to back up files in users Desktop,
Documents, etc. folders wi
Thanks Bill, you nailed it.
04-Jan-2022 16:13:52 FD: backup.c:1356-884680
fname=/Users/USER/Library/Containers/com.apple.Safari.CacheDeleteExtension
snap=/Users/USER/Library/Containers/com.apple.Safari.CacheDeleteExtension link=/Users/USER/Library/Containers/com.apple.Safari.CacheDeleteExtens
Sent: 04 January 2022 19:33
To: Martin Simmons
Cc: g...@hotmail.co.uk; bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Packet size too big (NOT a version mismatch)
However, even just backing up /Users results in...
04-Jan 11:31 SD JobId 88: Fatal error: bsock.c:530 Packet
size=
c: g...@hotmail.co.uk; bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Packet size too big (NOT a version mismatch)
However, even just backing up /Users results in...
04-Jan 11:31 SD JobId 88: Fatal error: bsock.c:530 Packet
size=1387166 too big from "client:1.2.3.4:9103". Maxim
On 1/4/22 12:26, Stephen Thompson wrote:
>
> Yes, backing up a single file on my problem hosts does succeed.
>
> H...
>
> Stephen
Hello Stephen,
This issue looked familiar to me, so I checked internally and I think I found
something.
I am pretty sure that this is an issue due to the larger
Thanks.
I have large file support off, though I am not sure that's intentional.
I will double check that.
On 1/4/22 11:55 AM, Graham Sparks wrote:
I'm afraid I don't enable encryption in my backup jobs (I know I should 😕) so I
don't know if that causes an issue. I'll have a quick look so
em Integrity
Protection,
although I do give the bacula-fd executable "Full Disk" permissions.
Thanks.
--
Graham Sparks
From: David Brodbeck
Sent: 03 January 2022 18:36
Cc: bacula-users@lists.sourceforge.net <
bacula-users@lists.sourceforge.net>
Subject: Re: [Bacula-users] Pa
Graham,
Thanks.
I am confident that it's not a networking issue (at least one external
to the Macs). The new problem only shows on hosts that have been
updated to Big Sur or Monterey (with or without rebuilt client, both 9x
and 11s). High Sierra and earlier hosts never yield the 'too big..
ms with System Integrity
Protection,
although I do give the bacula-fd executable "Full Disk" permissions.
Thanks.
--
Graham Sparks
From: David Brodbeck
Sent: 03 January 2022 18:36
Cc: bacula-users@lists.sourceforge.net <
bacula-users@lists.sourceforge.net>
Subject: Re: [Bacula
Sent: 03 January 2022 18:36
Cc: bacula-users@lists.sourceforge.net <
bacula-users@lists.sourceforge.net>
Subject: Re: [Bacula-users] Packet size too big (NOT a version mismatch)
I'm curious if anyone has moved away from Bacula on macOS and what
alternatives they're using. Even be
ry (I skipped Big Sur. Not
> >> for good reason---just laziness). Both v9 and v11 clients were compiled
> >> from source (setting the linker flags to "-framework CoreFoundation" as
> >> already suggested).
> >>
> >> I've personally not r
x27;, so
there's a chance it affects compilation).
I'm not a big Mac user, I'm afraid. It seems that just owning a Mac
automatically makes one the "Mac guy" 🙂.
Thanks.
--
Graham Sparks
From: Stephen Thompson
Sent: 04 January 2022 16:13
To: Graham Sparks
Cc: bacula-u
Brodbeck
Sent: 03 January 2022 18:36
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Packet size too big (NOT a version mismatch)
I'm curious if anyone has moved away from Bacula on macOS and what alternatives
they're using. Even before this, it was getting more and more aw
" as
>> already suggested).
>>
>> I've personally not run in to problems with System Integrity Protection,
>> although I do give the bacula-fd executable "Full Disk" permissions.
>>
>> Thanks.
>> --
>> Graham Sparks
>>
>>
&
k CoreFoundation" as
> already suggested).
>
> I've personally not run in to problems with System Integrity Protection,
> although I do give the bacula-fd executable "Full Disk" permissions.
>
> Thanks.
> --
> Graham Sparks
>
>
>
> From: David Brod
Brodbeck
Sent: 03 January 2022 18:36
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Packet size too big (NOT a version mismatch)
I'm curious if anyone has moved away from Bacula on macOS and what alternatives
they're using. Even before this, it was getting more and more aw
I'm curious if anyone has moved away from Bacula on macOS and what
alternatives they're using. Even before this, it was getting more and more
awkward to set up -- bacula really doesn't play well with SIP, for example,
and running "csrutil disable" on every system is not a security best
practice.
O
Disappointing... I am having the same issue on BigSur with the 11.0.5
release as I had with 9x.
08-Dec 15:42 SD JobId 878266: Fatal error: bsock.c:530 Packet
size=1387166 too big from "client:1.2.3.4:8103". Maximum permitted
100. Terminating connection.
Setting 'Maximum Network Buffer Size
Not sure if this is correct, but I've been able to at least compile bacula
client 11.0.5 on Big Sur by doing before configure step:
LDFLAGS='-framework CoreFoundation'
We'll see next up whether it runs and whether it exhibits the issue seen
under Big Sur for 9x client.
Stephen
On Tue, Nov 23, 2
Josh,
Thanks for the tip. That did not appear to be the cause of this issue,
though perhaps it will fix a yet to be found issue that I would have run
into after I get past this compilation error.
Stephen
On Mon, Nov 22, 2021 at 9:22 AM Josh Fisher wrote:
>
> On 11/22/21 10:46, Stephen Thomp
On 11/22/21 10:46, Stephen Thompson wrote:
All,
I too was having the issue with running a 9x client on Big Sur. I've
tried compiling 11.0.5 but have not found my way past:
This might be due to a libtool.m4 bug having to do with MacOS changing
the major Darwin version from 19.x to 20.x. T
All,
I too was having the issue with running a 9x client on Big Sur. I've tried
compiling 11.0.5 but have not found my way past:
Linking bacula-fd ...
/Users/bacula/src/bacula-11.0.5-CLIENT.MAC/libtool --silent --tag=CXX
--mode=link /usr/bin/g++ -L../lib -L../findlib -o bacula-fd filed.o
auth
Hello,
On 11/15/21 21:46, David Brodbeck wrote:
To do that I'd have to upgrade the director and the storage first, right?
(Director can't be an earlier version than the FD, and the SD must have the
same version as the director.)
In general yes, the code is designed to support Old FDs but can h
To do that I'd have to upgrade the director and the storage first, right?
(Director can't be an earlier version than the FD, and the SD must have the
same version as the director.)
On Mon, Nov 15, 2021 at 12:16 AM Eric Bollengier via Bacula-users <
bacula-users@lists.sourceforge.net> wrote:
> Hel
Hello David,
On 11/12/21 23:14, David Brodbeck wrote:
I'm getting this error trying to back up a macOS client. I recently
re-installed bacula from macports on this client, after an upgrade to macOS
Big Sur.
| russell.math.ucsb.edu-sd JobId 80985: Fatal error: bsock.c:520 Packet
size=1387166 too
On Fri, Nov 12, 2021 at 3:16 PM Heitor Faria wrote:
> Hello They,
>
> Are all the NICs using the same MTU?
>
Yes, all have an MTU of 1500.
> Have you checked for network layer problems?
>
None of the machines involved show any network errors. The network in
between is out of my hands, but it's f
David,
Sorry I can't offer a solution, but I can report that am I getting the
same error when trying to run bacula-fd 9.x on Big Sur (hand compiled).
I've tried the other suggestion of Maximum Network Buffer Size to no avail.
Stephen
On 11/12/21 2:14 PM, David Brodbeck wrote:
I'm getting
Hello They,
Are all the NICs using the same MTU?
Have you checked for network layer problems?
I have no clue regarding your error, but I would try to limit the packet size
with the following FD directive:
Maximum Network Buffer Size =
Rgds.
--
MSc Heitor Faria (Miami/USA)
CEO Bacula LatAm
mobi
I'm getting this error trying to back up a macOS client. I recently
re-installed bacula from macports on this client, after an upgrade to macOS
Big Sur.
| russell.math.ucsb.edu-sd JobId 80985: Fatal error: bsock.c:520 Packet
size=1387166 too big from "client:128.111.88.29:62571". Maximum permitted
32 matches
Mail list logo
