Public bug reported:
If smbd and nmbd are started and running but their service is disabled,
and an apt-get upgrade is performed which updates samba/samba-common, at
the end of the upgrade the smbd and nmbd daemons will not be running
anymore.
Distribution: Ubuntu 16.04
Pre-upgrade version: 4.3.8+dfsg-0ubuntu1
Post-upgrade version: 4.3.11+dfsg-0ubuntu0.16.04.12
What I expected to happen:
After the dist-upgrade, since smbd and nmbd services were running, they should
have been started again
What happened instead:
smbd and nmbd services are inactive.
The problem doesn't arise if the service is enabled; I suppose that somewhere
after the upgrade, the samba package queries for the global unit enablement
status rather than the unit status before the upgrade; this is especially
problematic with unattended-upgrades, there're reasons for which I don't start
samba at boot (it gets started by an ansible task after a disk is checked,
decrypted and mounted), and it has happened to me to have a machine with samba
properly running and then dead after an automated upgrade.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "full upgrade log transcript"
https://bugs.launchpad.net/bugs/1737534/+attachment/5021329/+files/smb-upgrade-norestart.txt
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to samba in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1737534
Title:
smbd/nmbd don't restart after upgrade if started but disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1737534/+subscriptions
--
Mailing list: https://launchpad.net/~enterprise-support
Post to : [email protected]
Unsubscribe : https://launchpad.net/~enterprise-support
More help : https://help.launchpad.net/ListHelp
