-
Bug
-
Resolution: Done
-
Undefined
-
None
-
rhel-9.2.0
-
None
-
None
-
rhel-sst-filesystems
-
ssg_filesystems_storage_and_HA
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
'systemctl reload autofs' causes autofs service to fail.
journal log:
systemd[1]: autofs.service: Main process exited, code=dumped, status=11/SEGV
systemd[1]: autofs.service: Failed with result 'core-dump'.
After failure, 'systemctl restart autofs' fails to start:
systemd[1]: Starting Automounts filesystems on demand...
systemd[1]: autofs.service: Main process exited, code=dumped, status=11/SEGV
systemd[1]: autofs.service: Failed with result 'core-dump'.
systemd[1]: Failed to start Automounts filesystems on demand.
After failure, according to /etc/mtab, the autofs mounts persist; in order to restart autofs must issue
umount -a -t autofs
systemctl restart autofs
Version-Release number of selected component (if applicable):
autofs-5.1.7-36.el9.x86_64
libsss_autofs-2.8.2-2.el9.x86_64
kernel-5.14.0-284.11.1.el9_2.x86_64
glibc-2.34-60.el9.x86_64
Additional info:
/etc/nsswitch.conf contains
automount: files
auto.master.d/MYCONF configures a direct map with many (~90) NFS mounts
I have locally rebuilt the autofs package from source
autofs-5.1.7-36.el9.src.rpm
and removed patch
Patch113: autofs-5.1.8-fix-incorrect-path-for-is_mounted-in-try_remount.patch
... and the problem doesn't occur
- external trackers