Hi Joe,
the initial bug contains no journal log or systemctl status of the failing service after install.
On the initial report per TerminalLog it seems smb itself failed:
Aug 15 09:11:35 Thinkpad smbd[17311]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Aug 15 09:11:37 Thinkpad systemd[1]: smbd.service: Failed with result 'timeout
This is odd to me, it first reports to be started and happy, to then fail with a timeout.
The latter update in comment #3 with the failing samba-ad-dc.service seems to be the service that fails after downgrade right?
I've so far seen this particular issue on e.g. [1], but other than retrying there was nothing there that could be reused here.
@Andreas - do you have a better samba-idea what to look for?
@Joe - is this reproducible? If so can you after upgrade show the "systemctl status" of the failed smbd service and also add the "journalctl -xe" output including other things happening around that time?
Hi Joe,
the initial bug contains no journal log or systemctl status of the failing service after install.
On the initial report per TerminalLog it seems smb itself failed:
Aug 15 09:11:35 Thinkpad smbd[17311]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Aug 15 09:11:37 Thinkpad systemd[1]: smbd.service: Failed with result 'timeout
This is odd to me, it first reports to be started and happy, to then fail with a timeout.
The latter update in comment #3 with the failing samba-ad-dc.service seems to be the service that fails after downgrade right?
I've so far seen this particular issue on e.g. [1], but other than retrying there was nothing there that could be reused here.
@Andreas - do you have a better samba-idea what to look for?
@Joe - is this reproducible? If so can you after upgrade show the "systemctl status" of the failed smbd service and also add the "journalctl -xe" output including other things happening around that time?
[1]: https:/ /bugs.launchpad .net/ubuntu/ +source/ samba/+ bug/1677329/ comments/ 21