NFSv4 Troubleshooting

Unable to start the service:
If you or the warden is unable to restart the NFS service, do the following:
  1. Review the warden logs (in $MAPR_HOME/logs/warden.log file) to determine when the NFSv4 Service Alarm was raised.
  2. Review the following NFSv4 server logs in $MAPR_HOME/logs/nfs4/nfs4server.log-0 and $MAPR_HOME/logs/nfs4/fsal.log-0, and other logs under $MAPR_HOME/logs/nfs4 on the node where the service went down to determine the cause for the error.

    The following example logs show some common causes for NFSv4 service shutting down such as license not present or an issue in the configuration.

    # tail -f /opt/mapr/logs/nfs4/fsal.log-0
2018-08-10 04:04:20,3058 FATAL FuseOps fs/client/fuse/cc/fuse_ops_ll.c:505 Thread: 1209 No license found. Shutting down
                
2018-08-10 04:04:34,6487 ERROR FuseAPI fc/fuse_api.cc:1384 Thread: 8877 Shmid to be used by fcdebug 1003847690, guts 0
2018-08-10 04:04:34,7749 ERROR Cidcache fc/cidcache.cc:5448 Thread: 8877 License not found. Shutting down
2018-08-10 04:04:34,7749 FATAL FuseOps fs/client/fuse/cc/fuse_ops_ll.c:505 Thread: 8877 No license found. Shutting down
                
2018-08-10 04:04:48,6729 ERROR FuseAPI fc/fuse_api.cc:1384 Thread: 15412 Shmid to be used by fcdebug 1005748236, guts 0
2018-08-10 04:04:48,7412 ERROR Cidcache fc/cidcache.cc:5448 Thread: 15412 License not found. Shutting down
2018-08-10 04:04:48,7413 FATAL FuseOps fs/client/fuse/cc/fuse_ops_ll.c:505 Thread: 15412 No license found. Shutting down
    # tail -f /opt/mapr/logs/nfs4/nfs4server.log-0
10/08/2018 T05:58:06.410328-0700 8163[none] [main] 713 :export_commit_common :Exporting to NFSv4 but not Pseudo path defined
10/08/2018 T05:58:06.410338-0700 8163[none] [main] 2267 :fsal_put :FSAL MAPR now unused
10/08/2018 T05:58:06.410369-0700 8163[none] [main] 1443 :build_default_root :Export 0 (/) successfully created
10/08/2018 T05:58:06.410373-0700 8163[none] [main] 476 :main :No export entries found in configuration file !!!
10/08/2018 T05:58:06.410380-0700 8163[none] [main] 219 :config_errs_to_log :Config File (/opt/mapr/conf/nfs4server.conf:104): Syntax error in statement
10/08/2018 T05:58:06.410384-0700 8163[none] [main] 219 :config_errs_to_log :Config File (/opt/mapr/conf/nfs4server.conf:65): Unknown parameter (nfs_track_memory)
10/08/2018 T05:58:06.410387-0700 8163[none] [main] 219 :config_errs_to_log :Config File (/opt/mapr/conf/nfs4server.conf:68): Unknown parameter (mapr_log_debug_level)
10/08/2018 T05:58:06.410389-0700 8163[none] [main] 219 :config_errs_to_log :Config File (/opt/mapr/conf/nfs4server.conf:95): 1 validation errors in block EXPORT
10/08/2018 T05:58:06.410392-0700 8163[none] [main] 219 :config_errs_to_log :Config File (/opt/mapr/conf/nfs4server.conf:95): Errors processing block (EXPORT)
10/08/2018 T05:58:06.411681-0700 8163[none] [main] 1040 :cache_inode_lru_pkginit :Setting the system-imposed limit on FDs to 65536.
  3. Take corrective action to rectify the cause for the error.