My guess from the manpage of sendmsg() is that this applies. The SOCK_DGRAM
may not working as a transport.
to specify the size. The length of the message is supplied by the len
parameter. For socket types such as SOCK_DGRAM and SOCK_RAW that
require atomic messages, the error EMSGSIZE is returned and the message
is not transmitted when it is too long to pass atomically through the
underlying protocol. The same restrictions do not apply to SOCK_STREAM
sockets.
So as we never use or verify the datagram protocol ourselves. I have wondered
how fast it streams from a big client.
I am guessing here that some problem shows up whence we're sending longer
packets than the 1460 or so that can be supported?
> -----Original Message-----
> From: Gunnarsson, Gunnar <gunnar.gunnars...@svk.se>
> Sent: Tuesday, March 22, 2022 9:30 AM
> To: Chris Hassell <chris.hass...@betsol.com>; li...@xunil.at; ? amanda users
> <amanda-users@amanda.org>
> Subject: SV: Sent out a pull-request to upgrade the packaging system....
>
> WARNING: This email originated from outside of BETSOL. Do not click links or
> open attachments unless you recognize the sender and know the content is safe.
>
>
> Hi,
>
> I'm testing the amanda-3_5-packaging-upgrade-wip and now it builds on my
> solaris 11.4 system.
> Amrecover fails to connect to the amindexd server see trace from below.
> Complains about too big message size see trace below.
> Server works if the amrecover client is 3.4.5 and the backup client seems to
> be
> working using th 3.4.5 version.
>
> Thanks Gunnar
>
> Tue Mar 22 15:42:21.445289090 2022: pid 11472: thd-100124a00: amindexd: pid
> 11472 ruid 91 euid 91 version 3.5.1+233: start at Tue Mar 22 15:4
> 2:21 2022
> Tue Mar 22 15:42:21.445353790 2022: pid 11472: thd-100124a00: amindexd:
> version 3.5.1+233
>
> 11484/2: setsockopt(4, SOL_SOCKET, SO_REUSEADDR,
> 0xFFFFFFFF7E8FB07C, 4, SOV_DEFAULT) = 0
> 11484/2: setsockopt(4, SOL_SOCKET, SO_KEEPALIVE, 0xFFFFFFFF7E8FB07C,
> 4, SOV_DEFAULT) = 0
> 11484/2: so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL,
> SOV_XPG4_2) = 5
> 11484/2: so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL,
> SOV_XPG4_2) = 6
> 11484/2: so_socketpair(5, 6) = 0
> 11484/2: pipe() = 7 [8]
> 11484/2: lwp_suspend(1) = 0
> 11484/2: forkx(0) = 11487
> 11487: forkx() (returning as child of pid 11484) = 0
> 11484/2: lwp_continue(1) = 0
> 11487: getpid() = 11487 [11484]
> 11484/2: lwp_sigmask(SIG_SETMASK, 0x00000000, 0x00000000,
> 0x00000000, 0x00000000) = 0xFFBFFEFF [0xFFFFFFFF]
> 11487: lwp_self() = 2
> 11484/2: close(6) = 0
> 11484/2: close(8) = 0
> 11487: lwp_sigmask(SIG_SETMASK, 0x00000000, 0x00000000, 0x00000000,
> 0x00000000) = 0xFFBFFEFF [0xFFFFFFFF]
> 11484/2: sendmsg(5, 0xFFFFFFFF7E8F8E48, MSG_XPG4_2) Err#97
> EMSGSIZE
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^^^^^^^
> 11487: schedctl() = 0xFFFFFFFF7F5E4000
> 11484/2: shutdown(5, SHUT_RDWR, SOV_DEFAULT) = 0
> 11484/2: close(5) = 0
> 11484/2: close(7) = 0
> 11487: close(5) = 0
> 11484/2: close(4) = 0
> 11484/2: getpid() = 11484
> [11483]
> 11487: fcntl(8, F_DUP2FD, 0x00000002) = 2
> 11484/2: write(10, 0x100147A64, 124) = 124
> 11484/2: r e c o v e r : a m b i n d f a i l e d : s e n d m
> s g
> 11484/2: f a i l e d A : M e s s a g e t o o l o n g\n\n
> 11487: fcntl(0, F_GETFD) = 0
> 11484/2: getpid() = 11484
> [11483]
> 11487: fcntl(1, F_GETFD) = 0
> 11484/2: write(10, 0x100147A64, 130) = 130
> 11484/2: T u e M a r 2 2 1 5 : 4 4 : 5 4 . 0 4 9 9 5 3 7 3 0
> 2 0
> 11484/2: 2 2 : p i d 1 1 4 8 4 : t h d - 1 0 0 1 5 5 0 0 0 :
> a m
> 11484/2: r e c o v e r : s t r e a m _ c l i e n t : C o u l d
> n o
> 11484/2: t b i n d t o p o r t i n r a n g e 5 1 2 - 1
> 0 2 3
> 11484/2: .\n
> 11487: fcntl(2, F_GETFD) = 0
> 11484/2: getpid() = 11484
> [11483]
> 11487: close(3) = 0
> 11484/2: write(10, 0x100147A64, 185) = 185
> 11484/2: T u e M a r 2 2 1 5 : 4 4 : 5 4 . 0 5 0 0 8 5 5 1 0
> 2 0
> 11484/2: 2 2 : p i d 1 1 4 8 4 : t h d - 1 0 0 1 5 5 0 0 0 :
> a m
> 11484/2: r e c o v e r : s e c u r i t y _ s e t e r r o r ( h a
> n d l
> 11484/2: e = 1 0 0 1 5 6 4 0 0 , d r i v e r = f f f f f f f f 7
> 1 3 9
> 11484/2: 2 f 4 0 ( B S D T C P ) e r r o r = s e n d m s g f
> a i l
> 11484/2: e d A : M e s s a g e t o o l o n g\n )\n
>
>
> -----Ursprungligt meddelande-----
> Från: Chris Hassell <chris.hass...@betsol.com>
> Skickat: den 21 mars 2022 20:37
> Till: li...@xunil.at; ? amanda users <amanda-users@amanda.org>; Gunnarsson,
> Gunnar <gunnar.gunnars...@svk.se>
> Ämne: RE: Sent out a pull-request to upgrade the packaging system....
>
> NOTE: it seems at least gcc 7 is a good idea for the Solaris build.
> Autoconf 2.69
> seems to be the minimal level.
>
> To start from a clean set of source.
>
> % git clean -dfx
> % ./autogen
>
> ( Not sure if autogen is necessary any more. It can be done automatically
> in the
> scripts. )
>
> To build binaries and packages in the top directory (where the source is) ...
> depending what you are running on. [Same dir setup as old].
>
> % ./packaging/rpm/build client
> % ./packaging/deb/build client
> % ./packaging/sun-pkg/build client
>
> To build current working dirs in a subdirectory (rpmbuild, debbuild or
> pkgbuild)
> and keep the top clear.
>
> % ./packaging/rpm/buildpkg client
> % ./packaging/rpm/buildpkg client
> % ./packaging/sun-pkg/buildpkg client
>
> The Solaris 11 wasn't fully going until today when I adjusted where the
> license is
> installed.
>
> > -----Original Message-----
> > From: Stefan G. Weichinger <s...@amanda.org>
> > Sent: Friday, March 18, 2022 3:31 AM
> > To: Chris Hassell <chris.hass...@betsol.com>; ? amanda users <amanda-
> > us...@amanda.org>
> > Subject: Re: Sent out a pull-request to upgrade the packaging system....
> >
> > WARNING: This email originated from outside of BETSOL. Do not click
> > links or open attachments unless you recognize the sender and know the
> content is safe.
> >
> >
> > Am 17.03.22 um 22:28 schrieb Chris Hassell:
> > > First of many. It is not configured-and-tested as is but it is very
> > > close to our working version.
> > >
> > > -Versioning based on tags from git
> > >
> > > -An in-directory build as well as below-directory package build
> > >
> > > -Solaris 10 and Solaris 11 packages
> > >
> > > -Better handling of pre/post scripts (may need to update Debian
> > > ones??)
> > >
> > > -Systemd services are included as well.
> > >
> > > If I can get someone to look over it and give it a spin I’d really
> > > appreciate it.
> > >
> > > I have more fixes for the installcheck directory to allow some good
> > > and solid self-tests.
> >
> > Nice to see progress.
> >
> > I assume you want us to try to build the code in that PR?
> >
> > pls point to some howto, I can't remember the procedure anymore (autoconf?
> > etc)
> >
> > I can test on Debian 11, for example.
> Confidentiality Notice | The information transmitted by this email is intended
> only for the person or entity to which it is addressed. This email may contain
> proprietary, business-confidential and/or privileged material. If you are not
> the
> intended recipient of this message, be aware that any use, review, re-
> transmission, distribution, reproduction or any action taken in reliance upon
> this
> message is strictly prohibited. If you received this in error, please contact
> the
> sender and delete the material from all computers.
Confidentiality Notice | The information transmitted by this email is intended
only for the person or entity to which it is addressed. This email may contain
proprietary, business-confidential and/or privileged material. If you are not
the intended recipient of this message, be aware that any use, review,
re-transmission, distribution, reproduction or any action taken in reliance
upon this message is strictly prohibited. If you received this in error, please
contact the sender and delete the material from all computers.
