systemd stuck at tty-ask-password-agent

[lucabrunox]

11864 13537 13537 11852 pts/0    13537 S+       0   0:00          |           \_ /nix/store/p0vd3ydvxplbpjffkpblwj5dahcmp9ri-bash-4.2-p45/bin/bash -e /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/modules/installer/tools/nixos-rebuild.sh switch --upgrade
13537 14307 13537 11852 pts/0    13537 S+       0   0:00          |               \_ /nix/store/l4sd8xf2q3x5xk5z8ji9dk3hxpb9v8sa-perl-5.16.3/bin/perl -I/nix/store/d63pjxj7pjx3f6w02qw0z25pfvqqybzx-perl-File-Slu /nix/var/nix/profiles/system/bin/switch-to-configuration switch
14307 14541 13537 11852 pts/0    13537 S+       0   0:00          |                   \_ /nix/store/rnacnxxh94z1cfpd2x1a5kl2lsms9ycg-systemd-212/bin/systemctl start -- default.target timers.target sockets.target ip-up.target remote-fs.target getty.target local-fs.target paths.target multi-user.target swap.target network-interfaces.target network.target slices.target
14541 14542 13537 11852 pts/0    13537 S+       0   0:00          |                       \_ /nix/store/rnacnxxh94z1cfpd2x1a5kl2lsms9ycg-systemd-212/bin/systemd-tty-ask-password-agent --watch

Some reference: http://lists.freedesktop.org/archives/systemd-devel/2011-April/002035.html

I have lvm /, /var and swap. Also imported the headless.nix profile. Tracking nixos-unstable.

[edolstra]

The presence of systemd-tty-ask-password-agent means nothing - systemctl always starts it to handle any password queries that might come up. There probably is some systemd service that hangs or is waiting for some device dependency to appear. To see which, run systemctl list-jobs.

[lucabrunox]

Thanks I've seem to have solved it. Ssh was started, but its pid wasn't in
/run. It's like systemd thought it stopped it, but it kept running. So the
next time systemd tried to restart it, it hanged. Had to write the pid by
hand. Thanks a lot.

On Fri, May 9, 2014 at 1:00 AM, Eelco Dolstra notifications@github.comwrote:

The presence of systemd-tty-ask-password-agent means nothing - systemctl
always starts it to handle any password queries that might come up. There
probably is some systemd service that hangs or is waiting for some device
dependency to appear. To see which, run systemctl list-jobs.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2584#issuecomment-42616675
.

www.debian.org - The Universal Operating System