Bug 2160898
| Summary: | userdbctl user does not report nis-users | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ralf Corsepius <rc040203> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | fedoraproject, filbranden, lnykryn, msekleta, ryncsn, systemd-maint, yuwatana, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-28 14:02:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This bug persists on fc38 and is a serious PITA to me. Any hint on how to restart systemd-userdbd upon boot? *** This bug has been marked as a duplicate of bug 2152376 *** |
Description of problem: I am using nis hosted accounts "userdbctl user <name>" fails on them, later on causing various malfunctions. Version-Release number of selected component (if applicable): systemd-251.10-588.fc37.x86_64 How reproducible: Always. Steps to Reproduce: 1. Reboot and log in into a local account on a console. 2. Check "userdbctl user <nisuser>" with <name> being a nis-hosted account name. # userdbctl user <nisuser> User <nisuser> does not exist Actual results: Full log: # systemctl status systemd-userdbd ● systemd-userdbd.service - User Database Manager Loaded: loaded (/usr/lib/systemd/system/systemd-userdbd.service; indirect; preset: disabled) Drop-In: /usr/lib/systemd/system/systemd-userdbd.service.d └─nss_nis.conf Active: active (running) since Sat 2023-01-14 07:25:01 CET; 3min 18s ago TriggeredBy: ● systemd-userdbd.socket Docs: man:systemd-userdbd.service(8) Main PID: 1020 (systemd-userdbd) Status: "Processing requests..." Tasks: 4 (limit: 18267) Memory: 4.8M CPU: 43ms CGroup: /system.slice/systemd-userdbd.service ├─1020 /usr/lib/systemd/systemd-userdbd ├─1034 systemd-userwork ├─1035 systemd-userwork └─1036 systemd-userwork Jan 14 07:25:01 morse systemd[1]: Starting systemd-userdbd.service - User Database Manager... Jan 14 07:25:01 morse systemd[1]: Started systemd-userdbd.service - User Database Manager. # id nisuser uid=1002(nisuser) gid=1004(nisgroup) groups=1004(nisgroup),135(mock) # userdbctl user nisuser User nisuser does not exist. => userdbctl fails. Now, restarting systemd-userdbd: # systemctl restart systemd-userdbd # userdbctl user nisuser User name: nisuser Disposition: regular Login OK: yes Password OK: no (none set) UID: 1002 GID: 1004 (nisgroup) Aux. Groups: mock nisgroup Real Name: NISuser Directory: /users/nisuser Storage: classic Shell: /bin/bash Passwords: none Service: io.systemd.NameServiceSwitch => userdbctl works! Expected results: Function. Additional info: - This bug cause various breakdowns and malfunctions, esp. after a login into a DE (I am using xfce + x11). - Due to the fact manually restarting systemd-userdbd after system boot up seems to work-around this issue, I am guessing the cause is a systemd service startup ordering problem.