Troubleshooting
A number of commands are provided with the Telemetry platform that you can use to troubleshoot the Telemetry platform components. The types of troubleshooting you can perform using the Telemetry platform commands are:
General Troubleshooting
Telemetry commands are provided that enable you to troubleshoot the Telemetry platform components. By default, debug log files are available for all of the Telemetry platform components, which you can view using Telemetry commands. You can also use standard CVP commands to check the status of Telemetry components and applications.
Viewing Debug Log Files
You can view debug log files for all platform components in a single log file, or for a particular platform component.
su cvp.To view debug log files for all platform components in a single log file
Use the cvpi logs all command.
To view the location of debug log files for a particular platform component
Use the cvpi logs <component> command.
You must specify the component using the name of the component as it is specified in the component's yaml file definition.
To create a zip archive (.tgz) containing debugging information
Use the cvpi debug command.
This command creates a .tgz archive on each CVP node that contains debugging information. The archive is automatically saved to the /data/debug directory on each node. Files need to be collected manually.
Checking CVPI Status
You can use commands to check status of the Telemetry components and applications, and to check the status of the entire CVP environment.
To check the status of CVPI
Use the cvpi status all command.
This command checks the status of CVPI, including the Telemetry components and applications.
To check the status of CVP environment
Use the cvpi check allcommand.
This command runs a check to ensure that the CVP environment is setup correctly. In a multi-node setup, it checks to make sure that the nodes can communicate with to each other and have the same environments and configuration.
Troubleshooting the NetDB State Streaming Agent
The Telemetry platform component provides commands you can use to troubleshoot issues you may encounter with the installation or performance of the NetDB State Streaming Agent.
The commands enable you to:
- Inspect the agent's configuration
- Restart the agent
- View the agent's logs
Inspect the agent’s configuration
Run the following commands to view the agent’s configuration:
switch> enable
switch# config
switch (config)# daemon TerminAttr
switch (config-daemon-TerminAttr)# show active
daemon TerminAttr
exec /usr/bin/TerminAttr -ingestgrpcurl=172.28.131.84:9910 -ingestauth=key,ab27cf35f73543d2afe3b4c15c12e6a3 -taillogs
no shutdownRestart the agent
Run the following commands to toggle the shutdown attribute:
switch (config-daemon-TerminAttr)# shutdown
switch (config-daemon-TerminAttr)# no shutdownView the agent’s logs
bash cat /var/log/agents/TerminAttr-`pidof TerminAttr`Checking the Status of the Ingest Port
The Telemetry platform automatically blocks the ingest port for the entire CVP cluster if the disk usage on any node of the cluster exceeds 85%. This feature prevents the potential for telemetry data to consume too much disk space in the CVP cluster.
You can easily check to see if the ingest port is blocked using the cvpi status ingest-port command.
Example
[cvp@cvp109 bin]$ cvpi status ingest-port
[ingest-port:status] Executing...
[ingest-port:status] FAILED
COMPONENTACTION NODESTATUS ERROR
ingest-port statusprimaryNOT RUNNINGcommand: Error running'/cvpi/bin/ingest-port.sh status'...
ingest-port status secondary NOT RUNNING command: Error running '/cvpi/bin/ingest-port.sh status': exit status 1
ingest-port status tertiaryNOT RUNNING command: Error running '/cvpi/bin/ingest-port.sh status': exit status 1
[cvp@cvp109 bin]$