Comment 3 for bug 1856771

I'm afraid that provided information here is not enough for us to know why samba couldn't be started during upgrade time.

From:

https://launchpadlibrarian.net/456135925/DpkgTerminalLog.txt

Setting up samba (2:4.3.11+dfsg-0ubuntu0.16.04.24) ...
Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript smbd, action "start" failed.
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Qua 2019-12-11 20:36:29 -03; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 12042 ExecStart=/etc/init.d/smbd start (code=exited, status=1/FAILURE)

Dez 11 20:36:28 edutec systemd[1]: Starting LSB: start Samba SMB/CIFS daemo.....
Dez 11 20:36:29 edutec smbd[12042]: * Starting SMB/CIFS daemon smbd
Dez 11 20:36:29 edutec smbd[12042]: ...fail!
Dez 11 20:36:29 edutec systemd[1]: smbd.service: Control process exited, co...=1
Dez 11 20:36:29 edutec systemd[1]: Failed to start LSB: start Samba SMB/CIF...).
Dez 11 20:36:29 edutec systemd[1]: smbd.service: Unit entered failed state.
Dez 11 20:36:29 edutec systemd[1]: smbd.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package samba (--configure):
 subprocess installed post-installation script returned error exit status 1

We dont have the exact reason why the daemon couldn't be started. Since this is an upgrade, I doubt Eduardo has a way to reproduce this again... but, if you do, please try checking journal logs for smbd.service and see what was the reason it couldn't start.

I'm marking this as incomplete. If anyone else ever face this again, please provide more information on the exact error for the daemon not to have started.

Thank you.