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.

Or a specific libcurl error may look like:


For more information, click the links below:

In general, all providers provide the same error status code.