Contents
You have the same share defined twice i.e. auto.misc and auto.Jackknife. You should not have to explicitly mount the share using autofs. If the share was being mounted via autofs the mount point should be /home/user/Jackknife/Exports and not /home/user/Jackknife. When you access the mount point, autofs should automatically mount the share.
Is there a problem with autofs on CentOS?
Dez 17 15:50:58 localhost.localdomain automount [8384]: setautomntent: lookup (sss): setautomntent: No such file or directory Dez 17 15:50:58 localhost.localdomain systemd [1]: Started Automounts filesystems on demand. Any hints?
Why is autofs looking for automount maps in SSSD?
Focusing on the ‘setautomntent: lookup (sss): setautomntent: No such file or directory’ errors, autofs is apparently looking for automount maps in sssd. Based on this Red Hat reference (specifically Section 7.5.3. Configuring Services: autofs), I’m speculating that you may have SSSD enabled…
What to know before moving up to autofs?
Before moving up to autofs make sure you can manually mount anything from the command line directly! If this works then you know 2 things which aren’t causing you an issue. If you have any issue then work them out first with mount. Is nfsd running on forth? Did you run exportfs -a on forth? Is portmap running? (Needed for NFS v3, not for NFS v4)
Why does Redhat CentOS 7 autofs Mount not work?
Jul 21 10:34:38 localhost.localdomain automount [1385]: setautomntent: lookup (sss): setautomntent: No such file or directory Jul 21 10:34:38 localhost.localdomain systemd [1]: Started Automounts filesystems on demand. I suspect for similar reasons, when mysql starts after reboot, it has an error saying it can’t ‘cd’ into /san/mysql_db/.
What to do if autofs Mount doesn’t work?
That is, logins of users with automounted home directories hung right after reboot, until such time as I manually started rpcbind with “systemctl start rpcbind”. This is with all the most recent Cent7 updates as of today.