Hi, I have same problem, when running systemctl stop/start from background bash script...
18581 pts/0 S 0:00 \_ su - 18582 pts/0 S 0:00 \_ -bash 18668 pts/0 S 0:00 \_ /usr/bin/bash /sbin/backupninja -d --run /etc/backup.d/30.redis-restore.sh 18760 pts/0 S 0:00 | \_ /usr/bin/bash /sbin/backupninja -d --run /etc/backup.d/30.redis-restore.sh 18762 pts/0 S 0:00 | | \_ /usr/bin/bash /sbin/backupninja -d --run /etc/backup.d/30.redis-restore.sh 18763 pts/0 S 0:00 | | \_ systemctl stop redis_6379 18764 pts/0 S 0:00 | | \_ /usr/bin/systemd-tty-ask-password-agent --watch 18761 pts/0 S 0:00 | \_ /usr/bin/bash /sbin/backupninja -d --run /etc/backup.d/30.redis-restore.sh the process just hangs. I noticed that "systemctl daemon-reexec" just kill somehow last staled process, if I have second staled process. This is the output after daemon-reexec: --- Warning! D-Bus connection terminated. Disconnected from bus. redis_6379.service - SYSV: Redis is a persistent key-value database Loaded: loaded (/etc/rc.d/init.d/redis_6379) Active: deactivating (stop) since Tue 2015-11-24 00:49:05 EET; 8min ago Control: 17618 (redis_6379) CGroup: /system.slice/redis_6379.service ├─17263 /usr/local/bin/redis-server *:6379 └─control ├─17618 /bin/sh /etc/rc.d/init.d/redis_6379 stop └─19422 sleep 1 Nov 24 00:57:53 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:57:54 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:57:55 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:57:56 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:57:57 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:57:58 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:57:59 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:58:00 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:58:01 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:58:02 offmedia-bms-stage.localdomain redis_6379[17618]: Waiting for Redis to shutdown ... Nov 24 00:58:03 offmedia-bms-stage.localdomain systemd[1]: Starting SYSV: Redis is a persistent key-value database... Info: <<<< finished action /etc/backup.d/30.redis-restore.sh: SUCCESS Debug: send report to root Info: FINISHED: 1 actions run. 0 fatal. 0 error. 0 warning. -- 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: Confirmed Status in systemd package in Debian: 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
