You are not logged in.
6.0.7-arch1-1
I can login remotely via SSH but direct login on host has issue:
Login prompt displays, accepts user/pass then clears and re-displays prompt. Same behavior for common user and for root login.
Journal shows this
Dec 20 19:19:06 acer systemd-coredump[611]: Process 609 (login) of user 0 dumped core.
Module linux-vdso.so.1 with build-id 56fe61440ed7ebc59c2ac8d0e1e5ca0f2230373b
Module libnss_systemd.so.2 with build-id a9361093f10d028f1d13ac8a2c1e00304afdf3ad
Module pam_warn.so with build-id 5b73faf8abe96fd6b460ef6c703cb127fe8e312b
Module pam_deny.so with build-id 023269774049f20683b13e4304d7e254a1c7a0b2
Module pam_mail.so with build-id 2e76a4a0eb21f3217a766329838b850a7085b16b
Module pam_motd.so with build-id f3ed720bd88c652152737c440039dd0b9589174c
Module pam_limits.so with build-id 904f399db1e3e4b168ab6fcd9152c52a52d41d3f
Module pam_keyinit.so with build-id 6bd2a336d004dc8458f1c4cdf8fcd941d1c4925f
Module pam_loginuid.so with build-id 45bcbb167aef0cae946704ce218c4a8f442393ad
Module pam_time.so with build-id 27045c468605f64203a35fa2d83d7c423220c298
Module pam_access.so with build-id 9e188fc5620336bf5919f51c25952325ff4de10e
Module pam_env.so with build-id e28d502d7e4820f936437d20d459e51036d1a243
Module pam_permit.so with build-id 59f4a785cc0a8400f0438321eac923ff96c34bdd
Module libresolv.so.2 with build-id 2e70cfe9f2972fb13487eeefcb10e4afafed6157
Module libkeyutils.so.1 with build-id ac405ddd17be10ce538da3211415ee50c8f8df79
Module libkrb5support.so.0 with build-id a5f810b57abf4afb41b94bee230a97851d06a279
Module libcom_err.so.2 with build-id 3360a28740ffbbd5a5c0c21d09072445908707e5
Module libk5crypto.so.3 with build-id ab0df0423a058a79962a54ffa8eb7ae47445f91a
Module libkrb5.so.3 with build-id a4e376ba5c58c292059c674e6837811fe3df83ab
Module libgssapi_krb5.so.2 with build-id 38e063da079423ae8073326b5c3368b1277acb6d
Module libtirpc.so.3 with build-id 8f5e329f75d897df033d761ca1f742f90619c1b6
Module libcrypt.so.2 with build-id e9d7d9d97daab17bf5a52dda02a4e821ac4e050f
Module pam_unix.so with build-id 608e03b3693ba42760a2b836763d41d1c079a2bf
Module libgcc_s.so.1 with build-id 85db482c4585a328d95ec41124337a967bb24d8f
Module libm.so.6 with build-id 2c8ff1d29b255da5b7371efd5caf57444d622838
Module libcap.so.2 with build-id 9b38b08de708f439a9d0a4f8b9914151bc8d4b50
Module pam_systemd_home.so with build-id 4d3430a8ce3f33b0d7b62edccf00a32f62bc9731
Module pam_faillock.so with build-id 7e42bd70303fbc079e452d777b6907bb5614df5d
Module pam_shells.so with build-id 827b2de32a5ec108462699009e6e441b42792b26
Module pam_nologin.so with build-id 9f749b8e7bd55bfb75e294bc32aaa56ac353d6c0
Module pam_securetty.so with build-id f50f4594f4bc962c6e9b8d75b3219dfb610f27d1
Module libcap-ng.so.0 with build-id 707f9d3134a43306625e3dab8662899ea368ac91
Module ld-linux-x86-64.so.2 with build-id 22bd7a2c03d8cfc05ef7092bfae5932223189bc1
Module libdl.so.2 with build-id 414d1d630bc04818a150b9c73e4493f3395e8869
Module libaudit.so.1 with build-id 53c797475ffeed05918d78f49f85dbf4127fb174
Module libc.so.6 with build-id 1e94beb079e278ac4f2c8bce1f53091548ea1584
Module libpam_misc.so.0 with build-id 74aaf2951cb6eb6cf89a69339285a6015876bee4
Module libpam.so.0 with build-id bb11b2685fe89555938ffd330ea44d82b0f8701c
Module login with build-id e728883277be09287f00c1c79ba257259e0df7f5
Stack trace of thread 609:
#0 0x00007f6f91df264c n/a (libc.so.6 + 0x8864c)
#1 0x00007f6f91da2958 raise (libc.so.6 + 0x38958)
#2 0x00007f6f91d8c53d abort (libc.so.6 + 0x2253d)
#3 0x00007f6f91ce748c n/a (pam_systemd_home.so + 0x2b48c)
#4 0x00007f6f91ce7b1f n/a (pam_systemd_home.so + 0x2bb1f)
#5 0x00007f6f91cd9200 n/a (pam_systemd_home.so + 0x1d200)
#6 0x00007f6f91cdd7bb n/a (pam_systemd_home.so + 0x217bb)
#7 0x00007f6f91f5947c n/a (libpam.so.0 + 0x347c)
#8 0x00007f6f91f59fe2 pam_end (libpam.so.0 + 0x3fe2)
#9 0x0000564297a7af43 n/a (login + 0x4f43)
#10 0x00007f6f91d8d290 n/a (libc.so.6 + 0x23290)
#11 0x00007f6f91d8d34a __libc_start_main (libc.so.6 + 0x2334a)Last edited by hwallace (2022-12-21 03:29:38)
Offline
One workaround is to login on other tty using ctrl + alt + f2 and then paste journactl -b
Offline
#3 0x00007f6f91ce748c n/a (pam_systemd_home.so + 0x2b48c)
#4 0x00007f6f91ce7b1f n/a (pam_systemd_home.so + 0x2bb1f)
#5 0x00007f6f91cd9200 n/a (pam_systemd_home.so + 0x1d200)
#6 0x00007f6f91cdd7bb n/a (pam_systemd_home.so + 0x217bb)Open a root shell (sic!) and edit /etc/pam.d/system-auth and comment *EVERY* line referencing pam_systemd_home.so - unless you're using homed, there're no drawbacks from this.
Test the result while you still have the root shell open - otherwise, if you screw this, you might lose the ability to login entirely (but since you've an open root shell, you can still fix your mistake
)
Then still post a journal - homed has in the past lost it over certain hostname, but "acer" looks innocent enough, so I've no idea what it doesn't like today…
Online
#3 0x00007f6f91ce748c n/a (pam_systemd_home.so + 0x2b48c) #4 0x00007f6f91ce7b1f n/a (pam_systemd_home.so + 0x2bb1f) #5 0x00007f6f91cd9200 n/a (pam_systemd_home.so + 0x1d200) #6 0x00007f6f91cdd7bb n/a (pam_systemd_home.so + 0x217bb)Open a root shell (sic!) and edit /etc/pam.d/system-auth and comment *EVERY* line referencing pam_systemd_home.so - unless you're using homed, there're no drawbacks from this.
Test the result while you still have the root shell open - otherwise, if you screw this, you might lose the ability to login entirely (but since you've an open root shell, you can still fix your mistake)
Then still post a journal - homed has in the past lost it over certain hostname, but "acer" looks innocent enough, so I've no idea what it doesn't like today…
No problem logging in after your fix.
What part of the journal are you interested in? The whole from boot or just the most recent from the login?
Do I need systemd_homed?
Offline
One workaround is to login on other tty using ctrl + alt + f2 and then paste journactl -b
Cannot login on any tty.
Offline
What part of the journal are you interested in? The whole from boot or just the most recent from the login?
It's best to post the entire journal (or link to a pastebin if it's very long). Try to make the boot as brief as possible though and only include the log from one booted session.
Do I need systemd_homed?
Good grief no.
Jin, Jîyan, Azadî
Offline
hwallace wrote:What part of the journal are you interested in? The whole from boot or just the most recent from the login?
It's best to post the entire journal (or link to a pastebin if it's very long). Try to make the boot as brief as possible though and only include the log from one booted session.
hwallace wrote:Do I need systemd_homed?
Good grief no.
The service is disabled but I can see that the system wants to find it.
Is there any downside to leaving the references disabled. I'm okay with the fix and want to avoid cleaning the log file of keys and IPv6 addresses etc.
Or maybe there is there a simple utility to de-identify logfiles?
Offline
The systemd-homed spam in your journal is normal (though i've not checked whether it's only triggered by the now disableb pam module)
As mentioned, if you don't use homed (attempt to have movable home dirs w/ uid mapping) there's no drawback from disabling the pam module.
The only interesting question is why homed crashes and whether that indicates some configuration issue (but i would not know what to look for before i see it)
Online