Re: Weird delay in ssh login

From	<tomas@tuxteam.de>
Newsgroups	linux.debian.user
Subject	Re: Weird delay in ssh login
Date	2022-02-22 20:40 +0100
Message-ID	<DTJaV-3DCb-15@gated-at.bofh.it> (permalink)
References	<DTr4l-3sej-1@gated-at.bofh.it> <DTv7X-3uGY-3@gated-at.bofh.it> <DTDId-3AaI-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, Feb 22, 2022 at 08:47:59AM -0500, Stefan Monnier wrote:
> >> The connection looks like:

[...]

> > This smells like your VM's ssh server is trying to reverse-resolve
> > the client's IP address [...]

> My intuition also suggests this possibility but I tried to put `UseDNS
> no` in /etc/ssh/sshd_config and it made no difference.

Darn :-(

> But this prompted me to try and increase sshd's logging to `DEBUG3` and
> now I do something apparently related in the log: right when the delay
> ends I get:
> 
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: start operation timed out. Terminating.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Main process exited, code=exited, status=1/FAILURE
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Killing process 3659208 (gpgconf) with signal SIGKILL.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Killing process 3659209 (awk) with signal SIGKILL.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Killing process 3659214 (dirmngr) with signal SIGKILL.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Failed with result 'timeout'.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Unit process 3659208 (gpgconf) remains running after unit stopped.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Unit process 3659209 (awk) remains running after unit stopped.
>     Feb 22 08:43:20 ... systemd[1]: user@1001.service: Unit process 3659214 (dirmngr) remains running after unit stopped.
>     Feb 22 08:43:20 ... systemd[1]: Failed to start User Manager for UID 1001.
>     Feb 22 08:43:20 ... systemd[1]: Started Session 50020 of user <USERNAME>.
> 
> Any idea what that systemd's "start operation timed out" might be about
> or how to track it down?

I'm totally out of my depth on this one, sorry. My search engine says it
looks a bit like

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877985;msg=7

which points to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841740

which suggests that something with the systemd user session for your
user 1001 went sour. I know, handwaving...

Perhaps some systemd buff around here?

Cheers
-- 
t

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Weird delay in ssh login Stefan Monnier <monnier@iro.umontreal.ca> - 2022-02-22 01:20 +0100
  Re: Weird delay in ssh login <tomas@tuxteam.de> - 2022-02-22 05:40 +0100
    Re: Weird delay in ssh login Stefan Monnier <monnier@iro.umontreal.ca> - 2022-02-22 14:50 +0100
      Re: Weird delay in ssh login <tomas@tuxteam.de> - 2022-02-22 20:40 +0100

csiph-web