Bug 745084

Summary:	net-fs/samba-4.13 and sys-apps/systemd-246-r1: Samba wont start after upgrade
Product:	Gentoo Linux	Reporter:	René Fuchs <r.fuchs>
Component:	Current packages	Assignee:	Gentoo's SAMBA Team <samba>
Status:	RESOLVED TEST-REQUEST
Severity:	critical	CC:	jstein, sam, systemd
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	739558

Description René Fuchs 2020-09-28 11:40:46 UTC

Samba wont start after upgrade to 4.13 and systemd  sys-apps/systemd-246-r1


systemd[1]: samba.service: Got notification message from PID 545, but reception only permitted for main PID 538
systemd[1]: samba.service: Got notification message from PID 578, but reception only permitted for main PID 538
systemd[1]: samba.service: Got notification message from PID 545, but reception only permitted for main PID 538




also Reported at arch linux 

https://bugs.archlinux.org/task/68025

Workaround:

As a hotfix I created a systemd drop in for samba.service with the following contents:
[Service]
NotifyAccess=all

But this might just cure the symptoms, not the problem. As this might also be related to systemd, it is version 246.6-1.


or change in in samba.service
Type=notify
to
Type=forked


Reproducible: Always

Comment 1 Mike Gilbert gentoo-dev

2020-09-29 03:32:03 UTC

I doubt this has anything to do with the systemd upgrade. Please test it with and older version to isolate the fault.