Does that happen with any service? Or is that specific to smbd and sssd?
I suppose 'service' is not the culprit here, and it also happens if you
directly call "sudo systemctl restart smbd.service"?
Can you please do
sudo systemd-analyze set-log-level debug
sudo systemctl restart systemd-udevd
sudo systemd-analyze set-log-level debug
sudo journalctl -b > /tmp/journal.txt
and attach /tmp/journal.txt here?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Unable to restart services from scripts
+ restarting services hangs on systemd-tty-ask-password-agent
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1456789
Title:
restarting services hangs on systemd-tty-ask-password-agent
Status in systemd package in Ubuntu:
Incomplete
Bug description:
I have a script run as root from cron that tweaks smb.conf and
restarts smbd and winbind. Problem is, starting today after working
perfectly up till yesterday, this script now hangs on Ubuntu 15.04.
When run from cron, the process tree looks like this:
service smbd restart
\_ systemctl restart smbd.service
\_ /bin/systemd-tty-ask-password-agent --watch
\_ /usr/bin/pkttyagent --notify-fd 5 --fallback
Run from a shell via sudo, same thing except the process tree
(obviously) includes the sudo command. It times out after 5 minutes,
causing the script to fail. If I manually kill the processes, it fails
faster.
The simplest possible scripts that reproduce this, run as root or
through cron or via sudo, are:
#!/bin/sh
service smbd restart
#!/bin/sh
systemctl restart smbd.service
Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and
until this morning worked perfectly on 15.04 as well.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 15.04
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
systemd 219-7ubuntu5
samba 2:4.1.13+dfsg-4ubuntu3
3) What you expected to happen
Services to restart
4) What happened instead
Services didn't restart, 'systemctl' hung
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
