Hi, the logs you attached ar only partial - e.g. the journal is only from after the try to upgrade. And the upgrade log ends premature.
But never the less it seems like: May 31 11:51:20 hostname systemd[1]: nmbd.service: Failed with result 'exit-code'. May 31 11:51:20 hostname systemd[1]: Failed to start LSB: start Winbind daemon. May 31 11:51:20 hostname systemd[1]: winbind.service: Failed with result 'exit-code'. May 31 11:51:21 hostname systemd[1]: Failed to start LSB: start Samba SMB/CIFS daemon (smbd). May 31 11:51:21 hostname systemd[1]: smbd.service: Failed with result 'exit-code'. That is after the failed upgrade (so not upgraded yet), and usually indicated that the samba config is broken. That in turn kills the upgrade, as on upgrade services are restarted - and if failing considered failed and aborted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694746 Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1694746/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
