get mesage:
> Could not fulfill the request.
> Server error message:
> Restarting the service samba4 failed:
> ● samba4.service
> Loaded: not-found (Reason: No such file or directory)
> Active: inactive (dead)
Hi,
if you try this from the command line:
systemctl start samba4.service
you will probably get an error, including 2 hints:
- output of journalctl -xn
- and another hint about systemctl - which I can’t remember or reproduce right now.
Those messages might be interesting, so we can actually help.
root@lkdc1:~# systemctl start samba4.service
Failed to start samba4.service: Unit samba4.service failed to load: No such file or directory.
root@lkdc1:~# journalctl -xn
-- Logs begin at Sun 2017-07-23 21:40:46 EEST, end at Wed 2017-07-26 15:38:48 EEST. --
Jul 26 15:38:43 lkdc1 named[1621]: samba_dlz: cancelling transaction on zone ad.samdom
Jul 26 15:38:43 lkdc1 named[1621]: client 192.168.89.103#57947: request has invalid signature: TSIG 1464-ms-7.29-1fcf9f94.35a02684-6d08-11e7-3dbe-d43d7ee53542: tsig verify failure (BADKEY)
Jul 26 15:38:44 lkdc1 named[1621]: samba_dlz: starting transaction on zone ad.samdom
Jul 26 15:38:44 lkdc1 named[1621]: client 192.168.89.143#51006: update 'ad.samdom/IN' denied
Jul 26 15:38:44 lkdc1 named[1621]: samba_dlz: cancelling transaction on zone ad.samdom
Jul 26 15:38:44 lkdc1 named[1621]: client 192.168.89.143#64065: request has invalid signature: TSIG 1372-ms-7.9-2d2ebf57.6f6db317-6ae7-11e7-0f9e-50e54943b04b: tsig verify failure (BADKEY)
Jul 26 15:38:48 lkdc1 named[1621]: samba_dlz: starting transaction on zone ad.samdom
Jul 26 15:38:48 lkdc1 named[1621]: client 192.168.89.161#50149: update 'ad.samdom/IN' denied
Jul 26 15:38:48 lkdc1 named[1621]: samba_dlz: cancelling transaction on zone ad.samdom
Jul 26 15:38:48 lkdc1 named[1621]: client 192.168.89.161#58429: request has invalid signature: TSIG 1280-ms-7.63-3d11b58d.6a29670a-689a-11e7-56a9-c0cb3892d915: tsig verify failure (BADKEY)
That seems to be the root cause.
The entries in journalctl seem to refer to clients trying to access samba services. Correct?
Are all directories configured as samba share still present?
all samba shares are still present. on both dc master and dc backup, but the error
Failed to start samba4.service
are the same on both dc master and dc backup
this is list of all services
root@lkdc1:~# service --status-all
[ + ] acpid
[ + ] apache2
[ + ] atd
[ + ] bind9
[ - ] bind9.debian
[ - ] bootlogs
[ - ] bootmisc.sh
[ - ] cgroupfs-mount
[ - ] checkfs.sh
[ - ] checkroot-bootclean.sh
[ - ] checkroot.sh
[ + ] console-setup
[ + ] cron
[ - ] cron.debian.dpkg-new
[ - ] cryptdisks
[ - ] cryptdisks-early
[ + ] dbus
[ + ] docker
[ + ] freeradius
[ + ] heimdal-kdc
[ - ] heimdal-kdc.debian
[ - ] hostname.sh
[ - ] hwclock.sh
[ - ] ifplugd
[ + ] irqbalance
[ + ] kbd
[ + ] keyboard-setup
[ - ] keymap.sh
[ - ] killprocs
[ + ] kmod
[ - ] lvm2
[ + ] memcached
[ - ] motd
[ - ] mountall-bootclean.sh
[ - ] mountall.sh
[ - ] mountdevsubfs.sh
[ - ] mountkernfs.sh
[ - ] mountnfs-bootclean.sh
[ - ] mountnfs.sh
[ + ] nagios-nrpe-server
[ - ] nagios-nrpe-server.debian
[ + ] networking
[ - ] networking.debian
[ + ] nfs-common
[ + ] nfs-kernel-server
[ + ] nmbd
[ + ] nscd
[ - ] nscd.debian
[ + ] ntp
[ - ] ntp.debian
[ + ] openbsd-inetd
[ - ] openbsd-inetd.debian.dpkg-new
[ - ] plymouth
[ - ] plymouth-log
[ + ] postfix
[ - ] postfix.debian
[ + ] procps
[ + ] quota
[ - ] quotarpc
[ - ] quotarpc.debian
[ + ] rc.local
[ ? ] rdate
[ - ] rmnologin
[ + ] rpcbind
[ - ] rpcbind.debian
[ - ] rpcbind.dpkg-new
[ - ] rsync
[ + ] rsyslog
[ + ] samba
[ + ] samba-ad-dc
[ - ] saned
[ + ] saslauthd
[ - ] screen-cleanup
[ - ] sendsigs
[ + ] slapd
[ - ] slapd.debian
[ + ] smbd
[ + ] ssh
[ - ] stunnel4
[ - ] sudo
[ + ] udev
[ + ] udev-finish
[ - ] umountfs
[ - ] umountnfs.sh
[ - ] umountroot
[ + ] univention-directory-listener
[ + ] univention-directory-notifier
[ + ] univention-directory-policy
[ + ] univention-firewall
[ + ] univention-maintenance
[ + ] univention-management-console-server
[ + ] univention-management-console-web-server
[ + ] univention-network-common
[ + ] univention-runit
[ + ] univention-s4-connector
[ + ] univention-saml
[ + ] univention-system-setup-boot
[ - ] univention-system-setup-boot-prepare
[ + ] urandom
[ + ] vmware-tools
[ + ] winbind
[ - ] x11-common
This seems to be a known bug. As a workaround use samba-ad-dc instead of samba4 for manual restarts via systemctl or service.
Manually creating that symlink /etc/init.d/samba4 will probably not work with systemd, though, so you’ll have to wait for a bugfix from Univention for the UI part.
I need to reopen this bug because after upgrade to UCS 4.4 I have exactly the same problem.
Sorry, I reopen the bug in the right place.
Hi,
starting with UCS 4.2 the recommended way to (re)start all samba components is simply:
/etc/init.d/samba restart
All other ways might fail.
/CV