Managing circular tracing
NetVault SmartDisk uses circular tracing to control the number and size of trace files generated by NetVault SmartDisk-related processes. Circular tracing, which is based on the maximum number of messages per file and the maximum number of files per thread, is enabled by default for all .trc and monitortrace.*.txt files. The following lists the defaults that are used:
While the defaults that control tracing are hard-coded in NetVault SmartDisk, you can modify some of the settings through the trace.cfg file.
|
Even if you disable circular tracing, the filename contains a sequence number of 0. |
The following table lists the types of trace files that NetVault SmartDisk uses:
Configuration information is read once, when NetVault SmartDisk starts. Unlike the settings for the resourcemanager, changes to the circular-tracing configuration are only applied after the processes are restarted. The information is identified in the trace.cfg file for the relevant module. For example, the trace.cfg file for the diskmanager module contains information similar to the following:
The preceding configuration would result in the following circular-tracing behavior:
|
• |
Each Deduplicator process thread uses circular tracing with up to 2,000,000 messages per file and allows a maximum of five files to be present at any time. |
|
• |
Each superserver process thread uses circular tracing with up to 500,000 messages per file and allows a maximum of 10 files to be present at any time. |
|
• |
Each storageservice process thread, and any other unlisted diskmanager module process, uses circular tracing with the configured Fallback settings. These settings are intentionally excluded in this example, which means that the example uses the hard-coded defaults of allowing up to 500,000 messages per file and a maximum of 10 files to be present at any time. |
The trace.cfg file for the foundation module might look like the following:
The preceding configuration would result in the following circular-tracing behavior:
|
• |
Each servicetool, percolatorslave, and any other unlisted foundation module process thread uses circular tracing with the configured Fallback settings. In this case, the settings allow up to 1,000,000 messages per file and a maximum of four files to be present at any time. |
|
• |
Each logd process thread traces to a single file without any limitation, instead of using circular tracing. |
Modifying values for circular tracing
|
2 |
Using a text editor, open the applicable trace.cfg file. |
|
3 |
In the applicable section, change the values for the MaxMessagesPerFile and MaxFilesToKeep values as appropriate. |
Disabling Circular Tracing
|
2 |
Using a text editor, open the applicable trace.cfg file. |
|
3 |
Installation on Windows succeeds but the Percolator fails to connect
If you install NetVault SmartDisk on Windows and the utility indicates that installation completed successfully, but invoking the smartdisk status command results in a message that indicates that it failed to connect to the percolator slave, it might be because you created a nonprivileged user whose password had to be changed before the installation was attempted.
When you create a nonprivileged user, the User must change password at next login check box is selected by default in some instances; it depends on what method you use to access the feature that lets you create a user. If you forget to clear the check box or if you forget to change the password before installing NetVault SmartDisk, installation appears to succeed.
When this issue occurs, remove NetVault SmartDisk and then reinstall it after completing either of the following options:
|
NOTE: Logging in as the nonprivileged user and changing its password after you have installed NetVault SmartDisk does not clear this issue. |
Another reason this issue might occur is because you entered the wrong user name or password. To update the user name or password after installation, use the smartdisk password command.