Univention Bugzilla – Bug 37022
nmbd not running on DC Backup after join of univention-samba4
Last modified: 2023-03-25 06:44:04 CET
Please check if a test case is possible. The directory 00_checks could be used for such a check, see Bug #37010. +++ This bug was initially created as a clone of Bug #36544 +++ 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.
(In reply to Stefan Gohmann from comment #0) > Please check if a test case is possible. I assume, the test can only check whether the nmbd is running.
(In reply to Dmitry Galkin from comment #1) > I assume, the test can only check whether the nmbd is running. r56301: * 00_checks/20_pgrep_samba_nmbd: check that nmbd process exists (Bug #37022).
For this bug is no separate QA needed.