fcdebug

Dynamically sets the log level to debug a library.

You can modify the core-site.xml file to set the log level of all modules using the fs.mapr.trace property. However, you must restart FUSE for the change to take effect. As an alternative, you can use the fcdebug utility to debug a specific library (at runtime) without restarting FUSE.

Note: You may have to run this command once per library (to debug).

Syntax

/opt/mapr/server/tools/fcdebug [-i] -s <shmid> [-m <module>] [-l <level>] [-o <slowOpsTraceThreshold>]

Parameters

Parameter Description
-i Lists the current debug level of all modules.
-l Specifies the log level. Value can be one of the following: FATAL, ERROR, WARN, INFO, DEBUG.
Note: If you do not specify the log level, the default level is applied for the module.
-m Specifies the module for which the log level is to be set. You can retrieve the list of modules with the fcdebug -i -s <shmid> command.
Note: If you do not specify the module, the log level is set on all modules.
-s Specifies the ID of the shared memory segment of the file client or the FUSE-based POSIX client.

Examples

The following command retrieves the list of modules:
/opt/mapr/server/tools/fcdebug -i -s 196614 
Note: You can run this command after dynamically setting the log level to verify the setting.
The following command dynamically sets the log level to DEBUG on the given module:
/opt/mapr/server/tools/fcdebug -s 196614 -m FuseOps -l DEBUG
Note: It may take up to a minute for the changes to take effect.
The following command sets the log level to DEBUG on all the modules:
/opt/mapr/server/tools/fcdebug -s 196614 -l DEBUG
The following command resets the log level to the default value on all the modules:
/opt/mapr/server/tools/fcdebug -s 196614