Am 05.02.20 um 20:29 schrieb Christian Boltz:
Hello,
Am Dienstag, 4. Februar 2020, 19:14:26 CET schrieb Stefan Seyfried:
Am 04.02.20 um 19:06 schrieb Stefan Seyfried:
So what do I need to do to make nscd work again?
OK. Apparmor. Something switched it on again for some reason...
Silly question - why did you switch it off before? ;-)
Because it always™ breaks something ;-) No, apparently I actually did not disable it after the last reinstall on this machine IIRC, I need to improve my documentation for reinstall to not forget this again ;-)
Please check if you have *.rpmnew files in /etc/apparmor.d/ or /etc/apparmor.d/abstractions/ - one of the latest snapshots included updated abstractions for the /usr/etc/ move.
Exactly. I checked the changelog and even rebooted to make sure everything is fine. strolchi:~ # find /etc -name '*.rpm*' /etc/sysconfig/network/scripts/functions.rpm-utils strolchi:~ #
If you don't have any *.rpmnew files and still see problems, please open a bugreport with your /var/log/audit/audit.log (you can grep for "apparmor" if you don't want to attach the whole file).
It boils down to: type=AVC msg=audit(1580924683.326:179): apparmor="DENIED" operation="open" profile="nscd" name="/usr/etc/services" pid=3405 comm="nscd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 And I don't understand why by reading the apparmor config. But "aa-teardown;systemctl disable apparmor" fixed it for me. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org