Collect troubleshooting logs for secure event connector

The troubleshooting command simplifies the diagnosis of issues by collecting logs, configurations, and limited system information into a single compressed archive.

If you already have a TAC case open, the compressed archive can also be sent directly to your TAC representative.

Before you begin

Follow these steps to collect troubleshooting logs for Secure Event Connector:

Procedure

Step 1

SSH to your host using the admin account, typically cdo.

Step 2

Switch to the SDC user using the command sudo su - SDC

Step 3

Run the appropriate troubleshoot command based on whether you have a TAC case open.


If...	Then...
You do not have a TAC case open	Run the command to gather and compress the troubleshooting bundle: `SDC eventing troubleshoot`
You already have a TAC case open	Request an upload token from your TAC representative and use the command: `SDC eventing troubleshoot --case-number [your-TAC-case-number] --token [the-token-TAC-provided]`

Step 4

If you prefer to retrieve the troubleshooting bundle manually, use SCP or SFTP.

Locate the absolute path to the bundle provided in the last log entry after running the troubleshoot command. Then, use the following SCP command to download the bundle to your local machine:

scp -P [22 or whichever port you SSH on]
        cdo@your-vm-ip:/opt/cdo/.cdo/troubleshooting/cdo_[tenant-name-here]
        -troubleshooting-[timestamp-here].tar.gz ./sec-troubleshooting-bundle.tar.gz

Note	Replace `/opt/cdo/.cdo/troubleshooting/cdo_\[tenant-name-here\]-troubleshooting-\[timestamp-here\].tar.gz` with the actual path displayed in the log output.

If you want to decompress the archive to review the logs and system configurations, use the command: tar xvf ./[sec-troubleshooting-bundle-filename].tar.gz

The troubleshooting bundle is created as a compressed archive file containing logs, configurations, and system information ready for analysis or TAC submission.