Automount/autofs
Jump to navigation
Jump to search
I am testing automount/autofs on backstreetboys.desktop.ucsf.bkslab.org. /etc/fstab causes us problems when one of the NFS servers are down. I'd like to move us to autofs mounts for future machines. There have been autofs issues in the past. For now, I'll use this on the desktops and see how they fare.
Issues
Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: Unit autofs.service entered failed state.
Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: autofs.service failed.
Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org dbus[1016]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper)
Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org polkitd[991]: Unregistered Authentication Agent for unix-process:4788:9276046 (system bus name :1.1679, object path /org/freedesktop/PolicyKit1/Authenticati
Aug 07 17:47:03 backstreetboys.desktop.ucsf.bkslab.org dbus[1016]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
Aug 07 17:47:03 backstreetboys.desktop.ucsf.bkslab.org setroubleshoot[4805]: SELinux is preventing /usr/sbin/automount from 'read, write' accesses on the file autofs-running. For complete SELinux messages run: s
Aug 07 17:47:03 backstreetboys.desktop.ucsf.bkslab.org python[4805]: SELinux is preventing /usr/sbin/automount from 'read, write' accesses on the file autofs-running.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that automount should be allowed read write access on the autofs-running file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'automount' --raw | audit2allow -M my-automount
# semodule -i my-automount.pp
[root@backstreetboys nfs]# systemctl restart autofs
Job for autofs.service failed because a configured resource limit was exceeded. See "systemctl status autofs.service" and "journalctl -xe" for details.
[root@backstreetboys nfs]# systemctl status autofs
● autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled; vendor preset: disabled)
Active: failed (Result: resources) since Tue 2018-08-07 17:54:12 PDT; 9s ago
Process: 3608 ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid (code=exited, status=0/SUCCESS)
Aug 07 17:54:12 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: Starting Automounts filesystems on demand... Aug 07 17:54:12 backstreetboys.desktop.ucsf.bkslab.org automount[3608]: /usr/sbin/automount: program is already running. Aug 07 17:54:12 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: PID file /run/autofs.pid not readable (yet?) after start. Aug 07 17:54:12 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: Failed to start Automounts filesystems on demand. Aug 07 17:54:12 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: Unit autofs.service entered failed state. Aug 07 17:54:12 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: autofs.service failed. [root@backstreetboys nfs]# ls -lh /run/autofs autofs.fifo-mnt-nfs autofs-running [root@backstreetboys nfs]# ls -lh /run/autofs-running ----------. 1 root root 6 Aug 7 17:37 /run/autofs-running [root@backstreetboys nfs]# less /run/autofs-running [root@backstreetboys nfs]# ps 26955 PID TTY STAT TIME COMMAND 26955 ? Ssl 0:00 automount -v [root@backstreetboys nfs]# kill 26955 [root@backstreetboys nfs]# ps 26955 PID TTY STAT TIME COMMAND [root@backstreetboys nfs]# less /run/autofs-running /run/autofs-running: No such file or directory [root@backstreetboys nfs]# systemctl restart autofs