Hi Ulrich,
[Reviving an old thread - I owe you an answer :-)]
On Thu, 9 Mar 2023 17:02:15 +0000, Ulrich Sibiller via samba
<samba at lists.samba.org> wrote:
> Martin Schwenke schrieb am 01.03.2023 23:53:
> > On Wed, 1 Mar 2023 16:18:58 +0000, Ulrich Sibiller
<ulrich.sibiller at atos.net> wrote:
> > > which ignores the port and thus matches all connections for the
ip
> > > anyway. On the other hand there's
> > > update_tickles 2049
> > > in /etc/ctdb/events/legacy/60.nfs without a corresponding tickle
> > > handling for lockd connections. I am thinking about adding an
> > > update_tickles 599 for lockd connections (what's the best way
to
> > > determine that port?). Any objections?
> > I just rebased this old 2015 branch for the first time in ~6 years:
> > I think it would help.
>
> Is this tested in any way? I don't think I can run this on my
> production systems. And on test systems I do not have the load to see
> the problems in the first place.
I've finally debugged this (definitely finding at least 1 important
bug) and modified it to just register all TCP connections to public IP
addresses (instead of using a configuration variable to specify
relevant ports), so this moves to 10.interface.
In this old thread, we also discussed problems with ctdb_killtcp. The
patch series containing the above change also adds a script option to
enable use of "ss -K" for resetting TCP connections to a public IP
address.
These changes should be in the next version of Samba/CTDB.
peace & happiness,
martin