You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nscd should start on boot like it was before the upgrade.
Additional context
On NixOS 21.11.334027.e34c5379866 (with systemd 249.5) nscd started normally.
On NixOS 21.11.335119.79c7b6a353e (with systemd 249.7), the service does not start on boot anymore.
On my NixOS desktop with an up to date version, nscd starts normally but I don't use LDAP.
I am not really familiar with systemd details but a difference I see is that commit ec0131d
by Arian van Putten talks about removing nss-lookup.target and nss-user-lookup.target from multi-user.target.wants.
I can see on the working server that /etc/systemd/system/multi-user.target.wants/nss-user-lookup.target is present
but not on the problematic one. When I search in journalctl -b to see any trace of nscd, I don't see any on the problematic server.
I see Starting Name Service Cache Daemon... and Reached target User and Group Name Lookups. on the working server.
It is like nss-user-lookup.target is nerver reached on the problematic server and so nscd.service is not started.
I added systemd.services.nscd.wantedBy = ["multi-user.target"]; in my configuration.nix as a temporary fix and it now starts on boot.
Describe the bug
The nscd.service is not started on boot.
Steps To Reproduce
Steps to reproduce the behavior:
id user_in_ldap
and getid: ‘user_in_ldap’: no such user
Active: inactive (dead)
My LDAP configuration:
Expected behavior
nscd
should start on boot like it was before the upgrade.Additional context
On NixOS 21.11.334027.e34c5379866 (with systemd 249.5)
nscd
started normally.On NixOS 21.11.335119.79c7b6a353e (with systemd 249.7), the service does not start on boot anymore.
On my NixOS desktop with an up to date version,
nscd
starts normally but I don't use LDAP.I am not really familiar with
systemd
details but a difference I see is that commit ec0131dby Arian van Putten talks about removing
nss-lookup.target
andnss-user-lookup.target
frommulti-user.target.wants
.I can see on the working server that
/etc/systemd/system/multi-user.target.wants/nss-user-lookup.target
is presentbut not on the problematic one. When I search in
journalctl -b
to see any trace ofnscd
, I don't see any on the problematic server.I see
Starting Name Service Cache Daemon...
andReached target User and Group Name Lookups.
on the working server.It is like
nss-user-lookup.target
is nerver reached on the problematic server and sonscd.service
is not started.I added
systemd.services.nscd.wantedBy = ["multi-user.target"];
in myconfiguration.nix
as a temporary fix and it now starts on boot.Notify maintainers
@arianvp
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: