Looking For C8 AMD Help

Home » CentOS » Looking For C8 AMD Help
CentOS 2 Comments

I’m migrating from C7 to C8.  I’m currently using autofs, but alas autofs has been dropped in C8 for the AMD automounter. I have some very ancient knowledge of AMD, I used it when it was first introduced many years ago on Solaris and moved to Sun’s automounter when it was introduced. So now it’s back to square one. I used automount2amd to convert one of my existing maps, included it in the amd.conf file and tried it out.  I don’t get any syntax errors so I
guess that the map syntax is correct, but amd fails to mount the remote filesystem and generates these errors  in messages.

Apr 23 16:04:29 localhost.my.domain amd[19389]: matched default selectors “type:=nfs;opts:=rw,grpid,nosuid,utimeout=600”
Apr 23 16:04:29 localhost.my.domain amd[19389]: key new: map selector host (=localhost) did not match remotehost Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts
“rw,grpid,nosuid,utimeout=600” add “fstype=nfs,vers=4,soft,intr” =>
“rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr”
Apr 23 16:04:29 localhost.my.domain amd[19389]: Map entry host==remotehost;type:=link;fs:=/export/data/& for /repo/new did not match Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts
“rw,grpid,nosuid,utimeout=600” add “fstype=nfs,vers=4,soft,intr” =>
“rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr”
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
returning NFS(4,tcp) on host remotehost.my.domain Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
NFS(4,udp) failed for remotehost.my.domain: RPC: Unable to receive Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
NFS(3,udp) failed for remotehost.my.domain: RPC: Unable to receive Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
NFS(2,udp) failed for remotehost.my.domain: RPC: Unable to receive Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
returning NFS(0,udp) on host remotehost.my.domain Apr 23 16:04:29 localhost.my.domain amd[19389]: Using NFS version 4, protocol tcp on host remotehost.my.domain Apr 23 16:04:29 localhost.my.domain amd[19389]: changing remotehost.my.domain’s ping value from 30 to 30
Apr 23 16:04:29 localhost.my.domain amd[19389]: Trying mount of remotehost:/export/data/& on /.automount/remotehost/export/data/& fstype nfs mount_type non-autofs Apr 23 16:04:31 localhost.my.domain amd[19389]: Trying mount of remotehost:/export/data/& on /.automount/remotehost/export/data/& fstype nfs mount_type non-autofs Apr 23 16:04:32 localhost.my.domain amd[19389]: file server remotehost.my.domain, type nfs, state starts down Apr 23 16:04:49 localhost.my.domain amd[19389]: “/repo/new” on //nil//
timed out (flags 0x20)

I’m using firewalld  on both hosts and allow these services mountd nfs rpc-bind and protocols 111/tcp and 111/udp  all of which allow autofs to work flawlessly, I’ve tried turning firewalld off which made no difference.

Here’s my /etc/amd.remote file looks like new \
  -addopts:=fstype=nfs,vers=4,soft,intr \
  host==remotehost;type:=link;fs:=/export/data/& \
  rhost:=remotehost;rfs:=/export/data/&

Any assistance in pointing me in the right direction would be greatly appreciated. Pete


Unencumbered by the thought process.
— Click and Clack the Tappet brothers


This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 thoughts on - Looking For C8 AMD Help

  • Nope, it’s in there! 8/BaseOS/x86_64/os/Packages/autofs-5.1.4-35.el8.x86_64.rpm

    consider removing what I think you have is am-utils.

  • Hmm, I guess that I have something wrong with my kickstart configuration because all that I can find is libsss_autofs-2.2.0-19.el8_1.1.x86_64.

    Thanks for the heads up Pete


    Unencumbered by the thought process.
    — Click and Clack the Tappet brothers


    This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.