IBM Support

I want to capture a slon trace, but I receive the following error message: "Slon start failed!" How to resolve it?

How To


Summary

While performing a deep troubleshooting analysis or looking for the root cause of some issues in Guardium™, one of the key elements used as evidence by the support engineers is the "slon" trace (for short, simply referenced as "slon").

In simple terms, a slon is a file that contains the raw traffic sent by the S-TAP to a Collector. And it can be used to re-create some complex issues at a test lab.

A good example of how a slon is captured can be found at the document called "How to collect a good slon trace for Guardium support to diagnose missing Login Info issues" in the references section below.

One rare, yet non-well-understood issue when trying to capture a slon is presented in the way of an error message like the following:

"Slon start failed!"

This document focuses on explaining in what cases the error messages occur.

Document Location

Worldwide

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Component":"sniffer;inspection core;Collector","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
13 May 2021

UID

ibm10881217

Page Feedback