Based on your logs, this is the error that's happening:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
ERROR: lock directory /run/samba does not exist
ERROR: pid directory /run/samba does not exist
Server role: ROLE_STANDALONE
[1mdpkg:[0m erro ao processar o pacote samba-common-bin (--configure):
o subprocesso instalado, do pacote samba-common-bin, o script post-installation retornou erro do status de saída 1
This issue is known and has been reported to the Debian samba package as well:
Although I wasn't able to reproduce it, the rationale described in the link above makes sense to me, and I can confirm that, on Focal, samba-common-bin.postinst is calling systemd-tmpfiles *after* calling testparm, which is what causes this issue.
Thanks for the bug report.
Based on your logs, this is the error that's happening:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
ERROR: lock directory /run/samba does not exist
ERROR: pid directory /run/samba does not exist
Server role: ROLE_STANDALONE
[1mdpkg:[0m erro ao processar o pacote samba-common-bin (--configure):
o subprocesso instalado, do pacote samba-common-bin, o script post-installation retornou erro do status de saída 1
This issue is known and has been reported to the Debian samba package as well:
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 975422
Although I wasn't able to reproduce it, the rationale described in the link above makes sense to me, and I can confirm that, on Focal, samba-common- bin.postinst is calling systemd-tmpfiles *after* calling testparm, which is what causes this issue.
Debian's fix is here:
https:/ /salsa. debian. org/samba- team/samba/ -/commit/ 0c3b2056764cd1a 566766c3e1764d7 c312eab5d7
I'm adding this bug to our TODO list, and marking it as Triaged.