[opensuse] yast lan hangs at "systemd-tty-ask-password-agent --watch"
The system is a xen domu, running 13.2 upgraded from 13.1. When I tried to add a new default route, it ended up hanging: 2150 ? Ss 0:00 /usr/sbin/sshd -D 2305 ? Ss 0:00 \_ sshd: root@pts/0 2315 pts/0 Ss 0:00 | \_ -bash 2521 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast 2536 pts/0 Sl+ 0:07 | \_ /usr/lib/YaST2/bin/y2base menu ncurses 2546 pts/0 S+ 0:00 | \_ sh -c /sbin/yast lan >&2 2547 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast lan 2567 pts/0 Sl+ 0:10 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2624 pts/0 Sl+ 0:00 | \_ /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_udev_persistent 2672 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2673 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2674 pts/0 S+ 0:00 | \_ /bin/systemctl reload-or-try-restart network.service 2675 pts/0 S+ 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch I can still login via ssh, but the above just hangs and hangs. What's the story? thanks Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 02:04 PM, Per Jessen wrote:
The system is a xen domu, running 13.2 upgraded from 13.1. When I tried to add a new default route, it ended up hanging:
2150 ? Ss 0:00 /usr/sbin/sshd -D 2305 ? Ss 0:00 \_ sshd: root@pts/0 2315 pts/0 Ss 0:00 | \_ -bash 2521 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast 2536 pts/0 Sl+ 0:07 | \_ /usr/lib/YaST2/bin/y2base menu ncurses 2546 pts/0 S+ 0:00 | \_ sh -c /sbin/yast lan >&2 2547 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast lan 2567 pts/0 Sl+ 0:10 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2624 pts/0 Sl+ 0:00 | \_ /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_udev_persistent 2672 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2673 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2674 pts/0 S+ 0:00 | \_ /bin/systemctl reload-or-try-restart network.service 2675 pts/0 S+ 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch
I can still login via ssh, but the above just hangs and hangs. What's the story?
Try a 'systemctl status' on that last service entry. Try '/usr/bin/systemd-tty-ask-password-agent --list' Try '/usr/bin/systemd-tty-ask-password-agent --query'
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/10/2016 02:04 PM, Per Jessen wrote:
The system is a xen domu, running 13.2 upgraded from 13.1. When I tried to add a new default route, it ended up hanging:
2150 ? Ss 0:00 /usr/sbin/sshd -D 2305 ? Ss 0:00 \_ sshd: root@pts/0 2315 pts/0 Ss 0:00 | \_ -bash 2521 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast 2536 pts/0 Sl+ 0:07 | \_ /usr/lib/YaST2/bin/y2base menu ncurses 2546 pts/0 S+ 0:00 | \_ sh -c /sbin/yast lan >&2 2547 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast lan 2567 pts/0 Sl+ 0:10 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2624 pts/0 Sl+ 0:00 | \_ /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_udev_persistent 2672 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2673 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2674 pts/0 S+ 0:00 | \_ /bin/systemctl reload-or-try-restart network.service 2675 pts/0 S+ 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch
I can still login via ssh, but the above just hangs and hangs. What's the story?
Try a 'systemctl status' on that last service entry.
# systemctl status network.service wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Thu 2016-03-10 20:35:28 CET; 56min ago Process: 1445 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 1445 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Mar 10 20:35:28 guest54 wicked[1445]: lo up Mar 10 20:35:28 guest54 wicked[1445]: eth0 up Mar 10 20:35:28 guest54 wicked[1445]: eth1 up Mar 10 20:35:28 guest54 systemd[1]: Started wicked managed network interfaces.
Try '/usr/bin/systemd-tty-ask-password-agent --list'
returns nothing.
Try '/usr/bin/systemd-tty-ask-password-agent --query'
Ditto. I dont' get it, I've got another domU with 13.2 just like it, works fine. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-10 21:40, Per Jessen wrote:
Try '/usr/bin/systemd-tty-ask-password-agent --list'
returns nothing.
It should tell you what it is waiting for. Then try killing it.
Try '/usr/bin/systemd-tty-ask-password-agent --query'
Ditto.
I dont' get it, I've got another domU with 13.2 just like it, works fine.
And this one what is it using? Ah, 13.2 upgraded from 13.1. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-03-10 21:40, Per Jessen wrote:
Try '/usr/bin/systemd-tty-ask-password-agent --list'
returns nothing.
It should tell you what it is waiting for.
Then try killing it.
Yep, did that - I can also stop it by hitting Ctrl-C in YaST, but the parent (systemctl reload-or-try-restart network.service) doesn't recognise it. I think that more or less confirms what Andrei said - "Most likely service restart hangs". Anyway, I'm going to re-install, again - I think something gets screwed up during installation+upgrade, I just cannot figure out what it is. To quote a former governor of California - I'll be back. -- Per Jessen, Zürich (2.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-11 08:14, Per Jessen wrote:
Anyway, I'm going to re-install, again - I think something gets screwed up during installation+upgrade, I just cannot figure out what it is.
How did you upgrade? DVD boot, or zypper dup? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-03-11 08:14, Per Jessen wrote:
Anyway, I'm going to re-install, again - I think something gets screwed up during installation+upgrade, I just cannot figure out what it is.
How did you upgrade? DVD boot, or zypper dup?
zypper dup. Difficult with a DVD and a xen DomU :-) -- Per Jessen, Zürich (3.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-11 09:56, Per Jessen wrote:
Carlos E. R. wrote:
On 2016-03-11 08:14, Per Jessen wrote:
Anyway, I'm going to re-install, again - I think something gets screwed up during installation+upgrade, I just cannot figure out what it is.
How did you upgrade? DVD boot, or zypper dup?
zypper dup. Difficult with a DVD and a xen DomU :-)
Ah, ok. I asked because DVD upgrade can not upgrade everything, as the DVD doesn't hold everything. It would explain some problems. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 03/10/2016 03:40 PM, Per Jessen wrote:
Try '/usr/bin/systemd-tty-ask-password-agent --list' returns nothing.
Since it seems to be hanging waiting for input, that makes no sense.
Try '/usr/bin/systemd-tty-ask-password-agent --query' Ditto.
Again, makes no sense. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-10 20:04, Per Jessen wrote:
The system is a xen domu, running 13.2 upgraded from 13.1. When I tried to add a new default route, it ended up hanging:
2150 ? Ss 0:00 /usr/sbin/sshd -D 2305 ? Ss 0:00 \_ sshd: root@pts/0 2315 pts/0 Ss 0:00 | \_ -bash 2521 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast 2536 pts/0 Sl+ 0:07 | \_ /usr/lib/YaST2/bin/y2base menu ncurses 2546 pts/0 S+ 0:00 | \_ sh -c /sbin/yast lan >&2 2547 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast lan 2567 pts/0 Sl+ 0:10 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2624 pts/0 Sl+ 0:00 | \_ /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_udev_persistent 2672 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2673 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2674 pts/0 S+ 0:00 | \_ /bin/systemctl reload-or-try-restart network.service 2675 pts/0 S+ 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch
I can still login via ssh, but the above just hangs and hangs. What's the story?
If it were my machine, I'd say it is waiting for you to enter the password to an encrypted enclosure. But I have never seen it triggered by YaST. It could be the password to the WiFi, but I didn't know it would ask for that. With systemd, the prompt for the password may be many lines above in the terminal, so that you do not know what it is asking for. Try: /usr/bin/systemd-tty-ask-password-agent --list -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
10.03.2016 22:04, Per Jessen пишет:
The system is a xen domu, running 13.2 upgraded from 13.1. When I tried to add a new default route, it ended up hanging:
2150 ? Ss 0:00 /usr/sbin/sshd -D 2305 ? Ss 0:00 \_ sshd: root@pts/0 2315 pts/0 Ss 0:00 | \_ -bash 2521 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast 2536 pts/0 Sl+ 0:07 | \_ /usr/lib/YaST2/bin/y2base menu ncurses 2546 pts/0 S+ 0:00 | \_ sh -c /sbin/yast lan >&2 2547 pts/0 S+ 0:00 | \_ /bin/bash /sbin/yast lan 2567 pts/0 Sl+ 0:10 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2624 pts/0 Sl+ 0:00 | \_ /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_udev_persistent 2672 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2673 pts/0 S+ 0:00 | \_ /usr/lib/YaST2/bin/y2base lan ncurses 2674 pts/0 S+ 0:00 | \_ /bin/systemctl reload-or-try-restart network.service 2675 pts/0 S+ 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch
I can still login via ssh, but the above just hangs and hangs. What's the story?
This is likely red herring. systemctl always spawns tty password agent when called in terminal to handle possible password request. It should not cause any issue. Most likely service restart hangs and systemctl waits for it (by default call is synchronous). What happens if you call the same command (systemctl reload-or-try-restart network.service) manually? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Per Jessen