Samba also not working for me in Impish, slightly different error message. Apparently related to unmasked samba-ad-dc.service
. This service has always been masked in the past, as I am fairly certain it conflicts with the client or file server-only version of Samba (the one almost everybody uses).
Error message:
$ sudo apt install -y samba
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
python3-samba samba-common samba-common-bin samba-dsdb-modules samba-libs
samba-vfs-modules
Suggested packages:
bind9 bind9utils ctdb ldb-tools ntp | chrony smbldap-tools ufw winbind
heimdal-clients
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE
Done
Setting up samba (2:4.13.14+dfsg-0ubuntu0.21.10.4) ...
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service masked)
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service.
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.
Job for samba-ad-dc.service failed because the control process exited with error code.
See "systemctl status samba-ad-dc.service" and "journalctl -xeu samba-ad-dc.service" for details.
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.34-0ubuntu3) ...
apt
said See "systemctl status samba-ad-dc.service" and "journalctl -xeu samba-ad-dc.service" for details.
, so...
$ sudo journalctl -xeu samba-ad-dc.service
░░
░░ The job identifier is 4924.
Dec 14 01:48:10 uminefi01 systemd[1]: samba-ad-dc.service: Main process exited,>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit samba-ad-dc.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 14 01:48:10 uminefi01 systemd[1]: samba-ad-dc.service: Failed with result '>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit samba-ad-dc.service has entered the 'failed' state with result 'exi>
Dec 14 01:48:10 uminefi01 systemd[1]: Failed to start Samba AD Daemon.
░░ Subject: A start job for unit samba-ad-dc.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit samba-ad-dc.service has finished with a failure.
░░
░░ The job identifier is 4924 and the job result is failed.
ESCOC
Took your recommendation to create a user nobody
(I don't think was necessary for this particular solution, but seemed like a good idea):
$ sudo smbpasswd -a nobody
New SMB password: [enter on blank line]
Retype new SMB password: [enter on blank line]
Added user nobody.
Masked the samba-ad-dc.service
unit:
systemctl mask samba-ad-dc.service
Created symlink /etc/systemd/system/samba-ad-dc.service → /dev/null.
Ran package management autofixes:
$ sudo dpkg -a --configure && sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Enabled stand-alone Samba services (the 'normal' ones):
systemctl enable --now smbd nmbd
Synchronizing state of smbd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable smbd
Synchronizing state of nmbd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable nmbd
Ran testparm
on generic package-maintainer's smb.conf
, said all good ...
My cockpit-zfs-manager
from 45Drives works again ...