samba - Oct 2023 - rpc_pipe_open_ncalrpc: connect(/run/samba/ncalrpc/EPMAPPER) failed: No such file or directory

on two of my DCs:

 > samba -V
Version 4.17.10-Debian
 > file /run/samba/ncalrpc/EPMAPPER
/run/samba/ncalrpc/EPMAPPER: socket

 > samba -V
Version 4.18.6-Debian
 > file /run/samba/ncalrpc/EPMAPPER
/run/samba/ncalrpc/EPMAPPER: socket

On 02.10.2023 14:10, Rowland Penny via samba wrote:
> On Mon, 2 Oct 2023 11:34:23 +0200
> Ingo Asche via samba <samba at lists.samba.org> wrote:
>
>> Forgot to tell: I'm on Samba 4.17.10 and that are no files, but
>> sockets
>>
> Interestingly, I was looking on Samba 4.17.10 running on my DCs
> (Raspberry pi OS hasn't got to Bookworm yet) and that is where I have
> /run/samba/ncalrpc/EPMAPPER.
>
> I have just updated my main client and it is running 4.18.6 and it
> doesn't have the 'EPMAPPER' socket, just
/run/samba/ncalrpc/np/epmapper.
>
> Rowland
>

02.10.2023 15:22, Norbert Hanke via samba:
> on two of my DCs:
> 
>  > samba -V
> Version 4.17.10-Debian
>  > file /run/samba/ncalrpc/EPMAPPER
> /run/samba/ncalrpc/EPMAPPER: socket
Yes, this socket does exist on a DC. It is being listened
by "samba: task[rpc] pre-forked worker(0)".

It does not exist on a member server, where I observe these
log messages.

Here, on a member server, samba-dcerpc is being started and
exited numerous times, each time logging a warning about it
being unable to connect to /run/samba/ncalrpc/EPMAPPER - which
does not exist on a member server.

/run/samba/ncalrpc/np/epmapper socket is being listened by
samba-dcerpc itself.  So these are two different sockets.

Instead of observing the behavour and guessing, I'd love to
know how things *should* work.

Thanks,

/mjt