Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#58262 - [glibc] gpasswd: nscd did not terminate normally (signal 11)

Attached to Project: Arch Linux
Opened by Curtis Lee Bolin (curtisleebolin) - Wednesday, 18 April 2018, 21:57 GMT
Last edited by Dave Reisner (falconindy) - Monday, 07 January 2019, 11:34 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No

Details

Description:
gpasswd fails to add user to group.


Additional info:
* package versions:
* core/shadow 4.5-4
* usr/bin/gpasswd
* core/glibc 2.26-11
* usr/bin/nscd


Steps to reproduce:
$ sudo gpasswd -a lee kvm
Adding user lee to group kvm
gpasswd: nscd did not terminate normally (signal 11)
gpasswd: nscd did not terminate normally (signal 11)
gpasswd: nscd did not terminate normally (signal 11)


Thankfully usermod worked
$ sudo usermod -a -G kvm lee
This task depends upon

Comment by Tommy Schmitt (spinka) - Sunday, 29 April 2018, 14:28 GMT
I've seen same message "gpasswd: nscd did not terminate normally (signal 11)" but "sudo gpasswd -a lee kvm" works successfully. I guess in your case it worked also.
Comment by Curtis Lee Bolin (curtisleebolin) - Monday, 30 April 2018, 14:28 GMT
Tommy, that day I was convinced `gpasswd` wasn't changing `/etc/group`, but today after testing, it does seem to be working even with the signal 11 errors.


$ sudo useradd testuser

$ grep testuser /etc/group
testuser:x:1003:

$ sudo gpasswd -a testuser kvm
Adding user testuser to group kvm
gpasswd: nscd did not terminate normally (signal 11)
gpasswd: nscd did not terminate normally (signal 11)
gpasswd: nscd did not terminate normally (signal 11)

$ grep testuser /etc/group
kvm:x:78:testuser
testuser:x:1003:
Comment by N.T. (NikTo) - Thursday, 04 February 2021, 21:37 GMT
Description:
passwd: nscd did not terminate normally (signal 11)

Package versions:
* core/shadow 4.8.1-4
* usr/bin/passwd
* core/glibc 2.32-5
* usr/bin/nscd

Steps to reproduce:
1. Install Arch Linux (including sudo package) from latest installation image (2021.02.01);
2. Login as root;
3. % useradd -m someuser && passwd someuser && echo 'someuser ALL=(ALL) ALL' > /etc/sudoers.d/01_something && chmod 400 /etc/sudoers.d/01_something
4. Login as someuser;
5. $ sudo passwd -l root
passwd: nscd did not terminate normally (signal 11)
passwd: nscd did not terminate normally (signal 11)
passwd: nscd did not terminate normally (signal 11)
passwd: nscd did not terminate normally (signal 11)
Passwd: password expiry information changed.
6. $ logout

After these actions, I can no longer login as a user (and as root). I added a new user using arch-chroot, but he can't login too.

Then I reinstalled the system and repeated the same steps with the same result. Complete lockdown of all.

How do I unblock everyone/someone? I don't want to reinstall the system again.
Comment by N.T. (NikTo) - Thursday, 11 March 2021, 11:55 GMT
Fresh system installation (glibc 2.33-4):

$ sudo passwd -l root
passwd: nscd did not terminate normally (signal 11)
passwd: nscd did not terminate normally (signal 11)
passwd: nscd did not terminate normally (signal 11)
passwd: nscd did not terminate normally (signal 11)
Passwd: password expiry information changed.

But I was able to log in. That's progress! :)

nscd is a separate package in Debian (https://packages.debian.org/sid/nscd).
From the package description: "You should install this package only if you use slow services like LDAP, NIS or NIS+".

Is it possible and necessary to separate glibc and nscd in Arch Linux?
Comment by Toolybird (Toolybird) - Thursday, 11 March 2021, 22:03 GMT
The error message comes from shadow pkg.

AFAICT nscd is not enabled by default in Arch. Did you manually enable it? Please show the output of:

systemctl status nscd

FWIW, Fedora are actively deprecating nscd (then planning to remove it entirely) [1]

[1]: https://fedoraproject.org/wiki/Changes/RemoveNSCD
Comment by N.T. (NikTo) - Friday, 12 March 2021, 06:55 GMT
No. I never enabled nscd.service manually.

$ systemctl status nscd
● nscd.service - Name Service Cache Daemon
Loaded: loaded (/usr/lib/systemd/system/nscd.service; disabled; vendor preset: disabled)
Active: inactive (dead)

journalctl doesn't say anything about nscd.

Fedora is already using sssd by default.
Debian does not use nscd and sssd (these packages are not installed) by default.
I don't know how it works in Debian yet.

Loading...