Re: what hath systemd wroght?

2019-01-18 Thread Tom Horsley
On Thu, 17 Jan 2019 10:01:33 -0500 Tom Horsley wrote: > So it looks like systemd is just sometimes speechless (which would > explain the systemctl commands hanging as well). I just did a dnf downgrade systemd to arrive at these old versions: systemd-239-3.fc29.x86_64 systemd-libs-239-3.fc29.x86_

Re: what hath systemd wroght?

2019-01-17 Thread Ted Roche
On Wed, Jan 16, 2019 at 3:03 PM Tom Horsley wrote: > Suddenly (probably after installing systemd updates this morning) > it takes 30 seconds or so for an NIS user to login via ssh and > I see this nonsense show up in the log: It may not be related, but I also did an update Wednesday morning, an

Re: what hath systemd wroght?

2019-01-17 Thread Tom Horsley
On Thu, 17 Jan 2019 15:31:36 +1100 Cameron Simpson wrote: > ISTR that the TCP connection timeout is about 30s. Can you "netstat > -anp | grep SYN" during the delay and see if somethings trying a > TCP connection to something now answering? That didn't detect anything, so I used the big hammer of

Re: what hath systemd wroght?

2019-01-16 Thread Cameron Simpson
On 16Jan2019 19:47, Tom Horsley wrote: On Thu, 17 Jan 2019 09:29:07 +1100 Cameron Simpson wrote: Just to confirm: the NIS user hasn't got a local /etc/passwd entry? Definitely no local /etc/passwd entry. Anyway, installing nscd is trivial and I would be interested to know if it changes the b

Re: what hath systemd wroght?

2019-01-16 Thread Tom Horsley
If I turn on ssh -vvv debugging, it hangs after this output: Authenticated to tomh ([10.134.30.143]:22). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Requesting no-more-sessi...@openssh.com debug

Re: what hath systemd wroght?

2019-01-16 Thread Tom Horsley
On Thu, 17 Jan 2019 09:29:07 +1100 Cameron Simpson wrote: > Just to confirm: the NIS user hasn't got a local /etc/passwd entry? Definitely no local /etc/passwd entry. > Anyway, installing nscd is trivial and I would be interested to know if > it changes the behaviour for you. Nope, same behavi

Re: what hath systemd wroght?

2019-01-16 Thread Cameron Simpson
Just to confirm: the NIS user hasn't got a local /etc/passwd entry? This may not be related to your issue, but I've tripped over systemd failing at NIS recently (not Fedora), and the fix was to make sure nscd was installed. Apparently systemd thinks it can speak NIS, but actually it can't (wel

what hath systemd wroght?

2019-01-16 Thread Tom Horsley
Suddenly (probably after installing systemd updates this morning) it takes 30 seconds or so for an NIS user to login via ssh and I see this nonsense show up in the log: Jan 16 14:53:33 tomh systemd-logind[811]: New session 11 of user tom. Jan 16 14:53:33 tomh systemd[1]: Failed to mount /userland.