Debugging StorNext for Object Storage Systems and Cloud Providers

When an error is detected, StorNext generates as much error information as possible to describe the action and the error encountered. Errors may originate internally within StorNext or be generated by one of the StorNext components, including libcurl, SSL, or the HTTP server.

For example, an error in the log file may look like:

... rc=412, error: HTTP status 404: 404 Not Found ..

where, 412 is the unique error formed by StorNext and 404 is an HTTP error.

Debugging Steps to Determine the Source of the Error

What operation are you doing when the error occurred?

Find the error message in:

/usr/adic/TSM/tac/tac_00

/usr/adic/TSM/trace/trace_04 or trace_05

Look at the extended error message. Not all messages have extended
verbose error messages from the server, but most do. These extended
messages are very useful. An extended error message looks like:
.. <Error><Code>SignatureDoesNotMatch</Code> ..