000017581 - NFS service does not come up after upgrading the RSA Security Analytics Warehouse to 10.3 SP3

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000017581
Applies ToRSA Security Analytics
RSA Security Analytics 10.3.3
RSA Security Analytics Warehouse
MapR
IssueNFS service does not come up after upgrading the RSA Security Analytics Warehouse to 10.3 SP3.

Errors similar to the following are found in the logs: 

/opt/mapr/logs/nfsserver.log
2014-06-07 13:35:59,3865 INFO nfsserver[7648] fs/nfsd/nfsserver.cc:928 0.0.0.0[0] running the cmd /opt/mapr/server/maprexecute pmapset set 100003 3 6 2049, ret 30464
2014-06-07 13:35:59,3873 INFO nfsserver[7648] fs/nfsd/nfsserver.cc:971 0.0.0.0[0] Use32BitFileId is 1
2014-06-07 13:35:59,3874 INFO nfsserver[7648] fs/nfsd/nfsserver.cc:984 0.0.0.0[0]  AutoRefreshExportsTimeInterval is 0
2014-06-07 13:35:59,3874 ERROR nfsserver[7648] fs/nfsd/main.cc:66 0.0.0.0[0] Error registering NFS program

/opt/mapr/logs/maprexecute.log
Cmd Line: /opt/mapr/server/maprexecute pmapset set 100003 3 6 2049
2014-06-07 13:35:49:ERROR:7586: failed to setgid (0) cmd: pmapset
2014-06-07 13:35:59:INFO:7651: maprexecute pmapset by uid 2147483632 gid 2147483632
Cmd Line: /opt/mapr/server/maprexecute pmapset set 100003 3 6 2049
2014-06-07 13:35:59:ERROR:7651: failed to setgid (0) cmd: pmapset

CauseIn version 3.1.0.x , MapR uses "maprexecute" to execute their command with root privilege. If, the linux volume is mounted with "nosuid" option, then OS will not let maprexecute  to gain the root privilege.  This causes Warehouse cluster to not to be able to run most of its commands such as  disk management or starting some services including  NFS service. 
Resolution

To resolve this issue, open /etc/fstab file and make sure that volumes "/tmp" and "/opt" are mounted with ?suid? option instead of ?nosuid? on all nodes. Then reboot all nodes.

 

If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article ID for further assistance.

WorkaroundUpgrading to RSA Security Analytics Warehouse to 10.3 SP3.
Legacy Article IDa66204

Attachments

    Outcomes