Univention Bugzilla – Bug 36544
nmbd not running on DC Backup after join of univention-samba4
Last modified: 2014-11-26 07:21:14 CET
Created attachment 6334 [details] join.log The nmbd did not run on a DC Backup after installation+join of univention-samba4. Details: First joined without Samba4 and then installed it as app and called univention-run-join-scripts via CLI. I checked: nmbd/autostart was not set, no idea yet why it didn't start. Observation #1: On the master two nmbds are running and on the slave one. On both systems Samba4 had been installed directly during installation. Observation #2:On an Slave setup as Samba4 RODC, where Samba4 was installed later via app as well, the situation is the same, nmbd was not running. After a invoke-rc.d samba restart the nmbd was started on DC Backup and RODC Slave.
The joinscript was using /etc/init.d/samba-ad-dc stop/start/restart which doesn't control nmbd. Fixed by using /etc/init.d/samba stop/start/restart instead in joinscript, postinst and prerm.
Yes, it works.
UCS 4.0-0 has been released: http://docs.univention.de/release-notes-4.0-0-en.html http://docs.univention.de/release-notes-4.0-0-de.html If this error occurs again, please use "Clone This Bug".