Troubleshooting

Troubleshooting

This topic lists the known issues and provides the workaround solutions.

Nytro Profiler Feature

*

Possible causes if the Nytro Profiler exits with the following error message:

*

Check if I/O is occurring on the device.

This means, in the Automatic mode, the blktrace or Xperf mechanism generated an empty trace, which could be because of the following reasons:

The device passed is invalid.

No I/Os on the device.

Inherent blktrace or Xperf issues.

No write permissions on the folder from where the Nytro Profiler is started.

*

The trace collection might be in process.

*

This message means that another Nytro Profiler instance is already collecting the I/O traces on the same device.

*

A previous run of the Nytro Profiler instance on this device was shut down abruptly.

Restart the machine to be able to run the Nytro Profiler on the same device again.

Nytro Predictor Feature

*

If the Nytro Predictor GUI fails to start with the DLL missing error message, check if the 64-bit DLL or .so file is in the same folder.

On Linux, run export LD_LIBRARY_PATH=. from the location where the .so file is stored.

*

If the Nytro Predictor GUI does not display any .qt file even after you select the directory containing the .qt files, the files might be corrupt or there could be a mismatch between the Nytro Profiler and the trace file versions.

*

If the Nytro Predictor GUI fails to start, try these work around solutions:

*

Use JRE 64-bit version 1.6.0_30 or later.

*

You must have a Java Runtime Environment (JRE) installed. See the documentation accompanying your JRE or JDK to find out into which location the JRE or JDK is installed. Make sure that the PATH and JAVA_HOME variables are correctly set.