I'm still facing the old problem with crypto devices. If crypto failed to activate on startup, it is attempted to be activated later on shutdown causing delays (default timeouts).
Here is full log from start to poweroff: http://pastebin.com/xLDpMHch First time on start: systemd[1]: Installed new job secrets.mount/start as 23 systemd[1]: Installed new job [email protected]/start as 24 systemd[1]: Installed new job dev-mapper-secrets.device/start as 25 systemd[1]: Installed new job [email protected]/start as 26 systemd[1]: About to execute: /lib/systemd/systemd-cryptsetup attach secrets /de v/disk/by-uuid/9cb97898-8892-41fc-92d3-a655805addc3 none noauto systemd[1]: [email protected] changed dead -> start systemd[1]: Child 602 belongs to [email protected] systemd[1]: [email protected]: main process exited, code=exited, status =1 systemd[1]: [email protected] changed start -> failed systemd[1]: Job [email protected]/start finished, result=failed systemd[1]: Job dev-mapper-secrets.device/start finished, result=dependency systemd[1]: Job secrets.mount/start finished, result=dependency systemd[1]: Job [email protected]/start finished, result=dependenc y systemd[1]: Unit [email protected] entered failed state. This is OK and expected. Then it is triggered second time systemd[1]: Installed new job dev-mapper-secrets.device/start as 211 systemd[1]: Installed new job [email protected]/start as 212 systemd[1]: Enqueued job console-kit-daemon.service/start as 188 systemd[1]: About to execute: /lib/systemd/systemd-cryptsetup attach secrets /dev/disk/by-uuid/9cb97898-8892-41fc-92d3-a655805addc3 none noauto ... systemd[1]: [email protected]: main process exited, code=exited, status=1 systemd[1]: [email protected] changed start -> failed systemd[1]: Job [email protected]/start finished, result=failed systemd[1]: Job dev-mapper-secrets.device/start finished, result=dependency systemd[1]: Startup finished in 20s 72ms 654us (kernel) + 10s 612ms 898us (initrd) + 3min 8s 756ms 424us (userspace) = 3min 39s 441ms 976us. systemd[1]: Unit [email protected] entered failed state. and finally during shutdown systemd[1]: Installed new job poweroff.target/start as 468 [...] systemd[1]: Installed new job dev-mapper-secrets.device/start as 492 systemd[1]: Installed new job [email protected]/start as 493 Oops. Why? During shutdown all password agents are dead already anyway ... _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
