• Status New
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Packages
  • Assigned To No-one
  • Operating System pentium4
  • Severity Low
  • Priority Medium
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Arch Linux 32
Opened by Andreas Baumann - 26.02.2021
Last edited by Andreas Baumann - 26.02.2021

FS#164 - pam_systemd.so hangs openssh 2 out of 3 times

Effect: you can not log in.
The SSHd child runs on 100% CPU doing something.
This happens on i486, i686 and pentium4 equally.

Admin
Andreas Baumann commented on 26.02.2021 07:46

starting systemd-homed stops this from happenning, I bet it's some broken timeout handling
in pam_systemd.

That or the minus in front of the PAM rule '-session optional pam_systemd.so' is
simply buggy.

Admin
Erich Eckner commented on 06.03.2021 08:05

maybe we should deviate from upstream and ship pam.d files without systemd-homed? (I'm doing this on my machines, anyways)

Admin
Andreas Baumann commented on 06.03.2021 09:36

I think it is now pretty much required by all window managers?

Admin
Erich Eckner commented on 06.03.2021 09:42

huh? systemd-homed is optional AFAIK. I never had trouble with my modified pambase-no-systemd-home

Admin
Andreas Baumann commented on 10.03.2021 16:02

%Cpu(s): 99.0 us, 0.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 1.0 hi, 0.0 si, 0.0 st
MiB Mem : 996.4 total, 754.4 free, 47.5 used, 194.6 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 923.7 avail Mem

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                            

6911 root 20 0 10392 6664 5820 R 49.5 0.7 5:14.58 sshd
7586 root 20 0 10524 6820 5988 R 49.5 0.7 0:10.97 sshd

neither ltrace nor strace show any activity.

Admin
Andreas Baumann commented on 10.03.2021 16:04

optional with -session … optional pam_systemd.so

but something is clearly not programmed right, either in PAM itself or more likely
in PAM systemd. I'm suspecting some races while waiting for connections to not-
running systemd daemons.

The sad thing is that almost all window manager now require systemd to be able
to log in. So you have to choose here.. :-(

Admin
Andreas Baumann commented on 04.04.2023 17:37

a variation of the pattern is a 2 out of 3 "invalid free()" glibc error when
logging in..

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing