EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB33470: Ownership of cache and inbox files are set to 'nobody' when using a centralized cache location with MicroStrategy Intelligence Server Universal 10.x


Community Admin

• Strategy


Ownership of cache and inbox files are set to 'nobody' when using a centralized cache location with MicroStrategy Intelligence Server Universal 10.x

SYMPTOM:
In a clustered or non-clustered configuration, it is possible to set up a remote location for centralized cache or inbox storage. The following Strategy Knowledge Base technical note details the steps on how to configure a remote cache/inbox storage location:
KB441125: How to configure Cache, Cube, Inbox, and Session Recovery file sharing for a MicroStrategy Intelligence Server cluster
If the Strategy Intelligence Server(s) are running as root and the remote location is shared via NFS, it may be noticed that the cache/inbox directories and files are created with an ownership set to the 'nobody' user. This can cause issues if not all files are owned by 'nobody', for example if the central file location resides on the same machine as one of the cluster nodes.
CAUSE:
This behavior is due to the Strategy Intelligence Server(s) running as root and accessing the NFS share as the root user. By default for security purposes, NFS will mask all read and write operations by a remote root user as the 'nobody' user. This prevents a user with root access on one machine from accessing the files on the NFS server machine as root when they may not have root access normally. This feature is called in NFS 'root squashing'.
 
ACTION:
Discuss with the system administrator(s) how to address any issues which may arise from NFS root squashing. Two possible scenarios are:

  • Disable NFS root squashing on the share to allow processes running as root on remote machines to access the NFS share as root.
  • Move the NFS share to another location so that all Intelligence Server cluster nodes are masked to the 'nobody' user by NFS.

 
WARNING
Third-party Software
The third-party  product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 
 
 
KB33470


Comment

0 comments

Details

Knowledge Article

Published:

June 7, 2017

Last Updated:

June 7, 2017