Managing the FUSE-Based POSIX Client

This section describes how to start and manage the POSIX client.

Starting and Stopping the POSIX Client

To allow a non-root user to start this service, as administrator or root user, run the following command:

chmod u+s /opt/mapr/bin/fusermount

Verify that permissions have been set for non-root user to start the service. For example:

ll /opt/mapr/bin/fusermount

Your output should look similar to the following:

-rwsr-xr-x 1 root root 39704 Feb 16 19:41 /opt/mapr/bin/fusermount

Ensure that the non-root user has full permissions on the mount point and log files.

To manually start or stop the service:

service mapr-posix-client-* [start|stop|status]

When you run the command, replace * with basic or platinum, which corresponds with the package that is installed on the system.

Note: The POSIX client service cannot be stopped or restarted if any other process is accessing the mount point. With systemd (on CentOS/RH 7.x and Suse 12), the service will enter failed state (if you tried to stop) or activating state (if you tried to restart) and you must manually kill the client processes.

Running the POSIX Client in Secure Mode

The POSIX client reads the mapr-clusters.conf file to determine whether the process must start in secure or non-secure mode. If security is configured, the mapr superuser's ticket file or the servicewithimpersonation ticket file must be present in the default /tmp directory. If the ticket file is not in the default /tmp directory, specify the location of the ticket file using the fuse.ticketfile.location configuration parameter in the fuse.conf file

If the ticket expires after a connection has been established between the POSIX client and the cluster, the connection can stay alive for up to an hour. No new connections will be allowed. If the ticket was blacklisted, restart POSIX client to refresh the ticket.

Setting up a Ticket for the POSIX Client

The POSIX client can be accessed using user and service tickets. The service tickets have long lifetimes, by default, for ease of administration. This is useful for running application processes that should not be bounded by the CLDB duration (cldb.security.user.ticket.duration.seconds) and renewal (cldb.security.user.ticket.max.duration.seconds) properties, which limit the lifetime of user tickets. If you plan to use a user ticket, ensure that the user has read permissions on the ticket file.

Irrespective of the ticket type, after generating the ticket, set the fuse.ticketfile.location parameter value in the fuse.conf file to point to the ticket file to use.

For more information, see:

Monitoring the POSIX Client

To determine whether the POSIX client is running, run the following command:

service mapr-posix-client-* status
Note: When you run the command, replace * with basic or platinum, which corresponds with the package that is installed on the system.

Adding and Removing Users

Before you add and/or remove users using the POSIX client, make a note of the following:

  • Invalid UID/GID cannot perform operations on the system.
  • When you add or remove users, it may take up to 30 minutes for the changes to take effect.

Unmounting the FUSE Mount

To unmount the mountpoint andkill the FUSE process, run the following command:

service mapr-posix-client-* stop
Note: When you run the command, replace * with basic or platinum, which corresponds with the package that is installed on the system.