Controls/gitea-pages
0
2
Fork 0
Code Pull Requests Actions Activity

login errors

Browse Source
This commit is contained in:
buchel_k
2024-07-18 11:42:53 +02:00
parent 4c2d1720f3
commit 28f1835952
1 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
admin-guide/troubleshooting/login.md
View File

@@ -18,12 +18,37 @@ because the PSI firewall only allows connections from a certain gateway, eg
## Known Errors
### Problematic `.bashrc`/`.bash_profile`
Some people load a pmodule or a conda environment when bash is started. This can easily break the Gnome Startup as this can bring in incompatible tools and libraries. Suspicous is also setting the `LD_LIBRARY_PATH` environment variable. Once even `PATH` was the culprit because an incompatible `kinit` was used after.
### pam_sss System Error
```
pam_sss(sshd:account): Access denied for user xxxxxx_y: 4 (System error)
```
Here the AD join might be broken. The machine can be rejoined by deleting/moving away `/etc/krb5.keytab` and then running Puppet (`puppet agent -t`).
### KioskWithKeyboard Error
```
gnome-session[31143]: gnome-session-binary[31143]: dconf-WARNING: unable to open named profile (redhatkiosk): using the null configuration.
gnome-session-binary[31143]: dconf-WARNING: unable to open named profile (redhatkiosk): using the null configuration.
gnome-session[31143]: gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.KioskWithKeyboard.WindowManager'
gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.KioskWithKeyboard.WindowManager'
gnome-session[31143]: gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.Kiosk.Script'
gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.Kiosk.Script'
gnome-session-binary[31143]: Entering running state
gnome-session[31214]: Unable to init server: Could not connect: Connection refused
gnome-session-f[31214]: Cannot open display:
```
For some reason the user got the first instead of the default desktop session. This can be fixed with
```
USER_WITH_BROKEN_LOGIN=...
systemctl stop accounts-daemon.service
rm /var/lib/AccountsService/users/$USER_WITH_BROKEN_LOGIN
systemctl start accounts-daemon.service
```
## Notes
For normal users there will be a [`pam_access(8)`](https://linux.die.net/man/8/pam_access) error even for