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...
Maximum permitted 1000000' error, but Big Sur/Monterey always do.
I use xcode along with homebrew openssl 1.1.
To further describe, the BigSur/Monterrey host jobs do partially
complete, successfully sending many GBs of data and files, including a
few warnings about unreadable system files, but ultimately the jobs crap
out with the same error.
My build options...
BHOME=/Users/bacula
EMAIL=bacula@DOMAINNAME
env CFLAGS='-g -O2' LDFLAGS='-framework CoreFoundation' \
./configure \
--prefix=$BHOME \
--sbindir=$BHOME/bin \
--sysconfdir=$BHOME/conf \
--with-working-dir=$BHOME/work \
--with-archivedir=$BHOME/archive \
--with-bsrdir=$BHOME/log \
--with-logdir=$BHOME/log \
--with-pid-dir=/var/run \
--with-subsys-dir=/var/run \
--with-basename=SERVER \
--with-hostname=SERVER.DOMAINNAME \
--with-dump-email=$EMAIL \
--with-openssl=/usr/local/opt/openssl\@1.1 \
--enable-smartalloc \
--disable-readline \
--enable-conio \
--enable-client-only \
| tee configure.out
thanks again,
Stephen
On 1/4/22 10:54 AM, Graham Sparks wrote:
Hi Stephen,
I've had a quick read of the archive (I'm late to the mailing list party) and
see you've tried lots, so I'll try to say something constructive.
I tried to recreate the packet size error, crudely, by directing the Bacula server to a
web page instead of the client FD (incidentally, this recreates it well). Therefore, I
think it's worth making sure the server and client are communicating without
interruption, just in case something else is being returned (perhaps a transparent
proxy/firewall/web filter "blocked" message, or similar).
Maybe try:
1. "status client=<client-name>" in bconsole to check Bacula can communicate
with the client.
2. If not, issue "lsof -i -P | grep 9102" at the terminal on the client, to
make sure 'bacula-fd' is running (on the default port).
3. If 'bacula-fd' is listed as running, stop the Bacula File Daemon on the client to free port 9102,
then run "nc -l 9102" to open a listener on the same port the file daemon uses, and send some
text from the Bacula server using "nc <client-name> 9102". If TCP communications are
good, you should see exactly the text you type on the server appear on the Mac's terminal after pressing
return.
Sorry in advance if this is stuff you've already tried.
Just for completeness, one of the few things I have done to the Mac in question
is install Xcode (I think it replaces the shipped installation of 'make', 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.
--
Stephen Thompson Berkeley Seismology Lab
stephen.thomp...@berkeley.edu 307 McCone Hall
Office: 510.664.9177 University of California
Remote: 510.214.6506 (Tue) Berkeley, CA 94720-4760
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
