Backup and scan for updates using NFS fails after upgrading to RSA Authentication Manager 8.4
Originally Published: 2019-05-08
Last Modified: 2023-11-30
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.4
Issue
mount.nfs: Remote I/O error
There was a problem processing your request.
Failed to scan for updates on any configured sources.
The following errors occurred:
• Failed to mount the NFS share.
There was a problem processing your request.
Failed to scan for updates on any configured sources.
The following errors occurred:
• Failed to mount the NFS share.
Current Status
[INFO] Mounting device NFS to /tmp/rsa_update/nfs_root.
[INFO] mount.nfs: Remote I/O error
[ERROR] Mounting failed with exit code 32.
[DEBUG] Failed to mount with default NFS options, Re-trying with NFSv4
Exception:
Unexpected error
[INFO] Mounting device NFS to /tmp/rsa_update/nfs_root.
[INFO] mount.nfs: Remote I/O error
[ERROR] Mounting failed with exit code 32.
Error: Failed to mount: There was an unexpected error while mounting.
Error: There were errors scanning all of the update sources.
[INFO] Mounting device NFS to /tmp/rsa_update/nfs_root.
[INFO] mount.nfs: Remote I/O error
[ERROR] Mounting failed with exit code 32.
[DEBUG] Failed to mount with default NFS options, Re-trying with NFSv4
Exception:
Unexpected error
[INFO] Mounting device NFS to /tmp/rsa_update/nfs_root.
[INFO] mount.nfs: Remote I/O error
[ERROR] Mounting failed with exit code 32.
Error: Failed to mount: There was an unexpected error while mounting.
Error: There were errors scanning all of the update sources.
The following error is seen during the backup process in Operations Console UI while back up job is running:
Validating remote backup location Failed
Please check that your remote connection is accessible, writable,
and has sufficient space, and back up your system again.
Please check that your remote connection is accessible, writable,
and has sufficient space, and back up your system again.
The NFS server is reachable and space and permissions were verified with no issues.
Cause
Resolution
# nfsstat -m
/mnt/share from 10.0.0.1:/mnt/share
Flags: rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.1,mountvers=3,mountport=30924,mountproto=udp,local_lock=none,addr=10.0.0.1
/mnt/share from 10.0.0.1:/mnt/share
Flags: rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.1,mountvers=3,mountport=30924,mountproto=udp,local_lock=none,addr=10.0.0.1
or
# grep nfs /proc/mounts
10.0.0.1:/mnt/share /mnt/share nfs rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.1,mountvers=3,mountport=30924,mountproto=udp,local_lock=none,addr=10.0.0.1
NFS protocol version is determined by checking the values for mountvers and vers on the NFS server.
* * *
If the NFS server is using NFS version 3 protocol, apply the following workaround on the Authentication Manager server:
- Launch an SSH client, such as PuTTY.
- Login to the primary Authentication Manager server as rsaadmin and enter the operating system password.
Note that during Quick Setup another user name may have been selected. Use that user name to login.
- Edit the /etc/nfsmount.conf.
- Change Defaultvers and Nfsvers values to 3 (instead of 4) as shown below:
# Protocol Version [2,3,4]
# This defines the default protocol version which will
# be used to start the negotiation with the server.
Defaultvers=3
#
# Setting this option makes it mandatory the server supports the
# given version. The mount will fail if the given version is
# not support by the server.
Nfsvers=3
# This defines the default protocol version which will
# be used to start the negotiation with the server.
Defaultvers=3
#
# Setting this option makes it mandatory the server supports the
# given version. The mount will fail if the given version is
# not support by the server.
Nfsvers=3
- Save changes
- Repeat steps 1 through 5 on each replica, completing the steps on one before moving to the next.
Related Articles
AFX Server fails to start in a WebSphere deployment after upgrading to 7.0.x or higher of RSA Identity Governance & Lifecycle Number of Views RSA Identity Governance and Lifecycle IDC Unification is slow in "Step 8/10: Post-Processing: Populate Role Metrics" after… Number of Views RSA RADIUS Service stopped after upgrading to AM 8.6 Number of Views Tables embedded in workflow email nodes are malformed after upgrading to version 7.1.1 of RSA Identity Governance & Lifecycle Number of Views Guidelines and resources for upgrading to SecurID Governance & Lifecycle 7.5.2 Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
