Roy Eastwood
2021-Aug-30 10:00 UTC
[Samba] samba-ad-dc.service: Got notification message from PID 27448, but reception only permitted for main PID 27410
Using Louis' repo I upgraded a samba DC to version 4.14.7 on a raspberry pi running Debian Bullseye. I noticed the above message when I checked the status of the samba-ad-dc service. The messages were: Aug 30 10:41:48 rpi3-dc systemd[1]: samba-ad-dc.service: Got notification message from PID 27448, but reception only permitted for main PID 27410 Aug 30 10:41:48 rpi3-dc systemd[1]: samba-ad-dc.service: Got notification message from PID 27416, but reception only permitted for main PID 27410 The two processes were as follows: root at rpi3-dc:~# ps ax | egrep '27416 | 27448' 27416 ? Ss 0:01 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground 27448 ? Ss 0:01 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground 28130 pts/0 S+ 0:00 grep -E 27416 | 27448 Is this to be expected? Thanks, Roy
Rowland Penny
2021-Aug-30 10:17 UTC
[Samba] samba-ad-dc.service: Got notification message from PID 27448, but reception only permitted for main PID 27410
On Mon, 2021-08-30 at 11:00 +0100, Roy Eastwood via samba wrote:> Using Louis' repo I upgraded a samba DC to version 4.14.7 on a > raspberry pi running Debian Bullseye. I noticed the above message > when I checked the status of the samba-ad-dc service. The messages > were: > > Aug 30 10:41:48 rpi3-dc systemd[1]: samba-ad-dc.service: Got > notification message from PID 27448, but reception only permitted for > main PID 27410 > Aug 30 10:41:48 rpi3-dc systemd[1]: samba-ad-dc.service: Got > notification message from PID 27416, but reception only permitted for > main PID 27410 > > The two processes were as follows: > root at rpi3-dc:~# ps ax | egrep '27416 | 27448' > 27416 ? Ss 0:01 /usr/sbin/smbd -D --option=server role > check:inhibit=yes --foreground > 27448 ? Ss 0:01 /usr/sbin/winbindd -D --option=server > role check:inhibit=yes --foreground > 28130 pts/0 S+ 0:00 grep -E 27416 | 27448 > > Is this to be expected? >Yes it is, because the 'Type' in samba-ad-dc.service is set to 'notify', try changing it to 'fork' Rowland