syslog-ng Store Box (SSB) automatically generates core files if an important software component (for example, syslog-ng, or the indexer) of the system crashes for some reason. These core files can be of great help to the One Identity Support Team to identify problems. To display a list of alerts, navigate to Search > Log Alerts.
To list and download the generated core files, navigate to Basic Settings > Troubleshooting > Core files.
By default, core files are deleted after 14 days. To change the deletion timeframe, navigate to Basic Settings > Management > Core files.
The Troubleshooting menu provides an interface to view the logs generated by the various components of syslog-ng Store Box (SSB). For details on how to browse the log messages received by SSB from its peers, see Searching log messages.
For performance considerations, log files larger than 2 Megabytes are not displayed in the web interface. To access these logs, download the file instead.
To view logs on SSB
Navigate to Basic Settings > Troubleshooting > View log files.
Use the Logtype roll-down menu to select the message type.
SSB: Logs of the SSB web interface.
syslog: All system logs of the SSB host.
syslog-ng: Internal log messages of the built-in syslog-ng server. These logs do not contain messages received from the peers.
To download the log file, click Download.
To follow the current log messages real-time, click Tail.
To display the log messages, click View.
To display log messages of the last seven days, select the desired day from the Day: field and click View.
To display only the messages of a selected host or process, enter the name of the host or process into the Message: field.
The Message: field acts as a generic filter: enter a keyword or a POSIX (basic) regular expression to display only messages that contain the keyword or match the expression.
To track down support requests, the One Identity Support Team might request you to collect system-state and debugging information. This information is collected automatically, and contains log files, the configuration file of syslog-ng Store Box(SSB), and various system-statistics.
Sensitive data like key files and passwords are automatically removed from the files.
The Basic Settings > Management > Debug logging > Enable debug logs option is not related to the verbosity of log messages: it adds the commands executed by the SSB web interface to the log.
To collect system-state information, navigate to Basic Settings > Troubleshooting > System debug and click Collect and save current system state info, then save the created zip file. The name of the file uses the debug_info-<hostname>YYYYMMDDHHMM format.
To collect information for a specific error
Navigate to Basic Settings > Troubleshooting > System debug.
Figure 174: Basic Settings > Troubleshooting > System debug — Collecting debug information
Starting debug mode increases the log level of SSB, and might cause performance problems if the system is under a high load.
Reproduce the event that causes the error, for example send a log message from a client.
Click Save the collected debug info and save the created zip file. The name of the file uses the debug_info-<hostname>YYYYMMDDHHMM format.
Attach the file to your support ticket.
The following sections help you to solve problems related to high availability clusters.
For a description of the possible statuses of the syslog-ng Store Box (SSB) cluster and its nodes, the DRBD data storage system, and the heartbeat interfaces (if configured), see Understanding SSB cluster statuses.
To recover a cluster that has broken down, see Recovering SSB if both nodes broke down.
To resolve a split-bran situation when the nodes of the cluster were simultaneously active for a time, see Recovering from a split brain situation.
To replace a broken node with a new appliance, see Replacing a node in an SSB HA cluster.