You are not logged in.
Hello guys first time posting for problem i cant find how to or fix myself. This started after upgrading samba to 4.15. Other devices cant connect to server and after systemctl
× smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2021-09-24 21:03:45 CEST; 30min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 29238 ExecStart=/usr/bin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 29238 (code=exited, status=1/FAILURE)
Status: "daemon failed to start: Samba failed to init printing subsystem"
Error: 13 (Permission denied)
CPU: 57msSep 24 21:03:45 ArchNAS systemd[1]: Starting Samba SMB Daemon...
Sep 24 21:03:45 ArchNAS smbd[29238]: [2021/09/24 21:03:45.831138, 0] ../../source3/smbd/server.c:1738(main)
Sep 24 21:03:45 ArchNAS smbd[29238]: smbd version 4.15.0 started.
Sep 24 21:03:45 ArchNAS smbd[29238]: Copyright Andrew Tridgell and the Samba Team 1992-2021
Sep 24 21:03:45 ArchNAS systemd[1]: Started Samba SMB Daemon.
Sep 24 21:03:45 ArchNAS smbd[29238]: [2021/09/24 21:03:45.844215, 0] ../../lib/util/become_daemon.c:119(exit_daemon)
Sep 24 21:03:45 ArchNAS smbd[29238]: exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13
Sep 24 21:03:45 ArchNAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Sep 24 21:03:45 ArchNAS systemd[1]: smb.service: Failed with result 'exit-code'.
here is testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowedServer role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
dns proxy = No
log file = /var/log/samba/log.%m
max log size = 50
server role = standalone server
server string = Samba Server
idmap config * : backend = tdb[homes]
browseable = No
comment = Home Directories
read only = No
Last edited by quietsoviet (2021-09-25 18:23:45)
Offline
Sep 24 21:03:45 ArchNAS smbd[29238]: exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13
Since you don't seem to share printers, try
disable spoolss = yes
Could be outfall of https://www.bleepingcomputer.com/news/s … -printing/
Edit: https://wiki.archlinux.org/title/Samba# … er_sharing
Last edited by seth (2021-09-24 21:48:47)
Online
I hope this is not hijacking the post.
I am getting the same error. But unfortunately I need to share a cups printer. So I cannot disable printer sharing.
Is there any other fix to this problem?
Offline
Is https://paalijarvi.fi/tgblog/2020/05/25 … e-network/ an option?
(For POSIX systems you should™ be using cups anyway, no need to add MS' somethingsomethingnetwork protocol…)
Judging from MS panic-patches that boil down to disabling SPOOLSS I guess this is FUBAR (what to SMB is SNAFU ;-) and would look around for ways to share printers that do not use SMB.
Though there's no mention of this in samba's release notes or CVE history, so it could be a completely unrelated bug that you should report https://bugzilla.samba.org/
(In any event, failing to start samba because of the printing situation isn't an ideal way to cope w/ the issue ;-)
Online
Thank you for replay i added all options from https://wiki.archlinux.org/title/Samba# … er_sharing and its working perfectly now. I don't know how it happened because i don't even have printer in house.
Offline
The SMB print service is active by default (it's a really horrible protocol…) - you don't need a printer for this and this is also not a problem with your configuration.
There's certainly a bug and my guess is that it's related to the fact that the SMB print service is basically an invitation to get your system hacked
Explicitly deacitvating the print service simply side-steps the bug.
Online
Thank you, @seth.
The alternative (using cups directly) works for me.
Offline