How to Collect Data for Server Issues
7817
Created On 05/24/21 09:07 AM - Last Modified 12/15/22 11:17 AM
Objective
In order to diagnose and fix server issues, it's recommended that you collect the necessary data for each server issue.
IMPORTANT: For all server issues, you first need to collect the log bundle
Environment
- Cortex XSOAR
- Version 6.x
Procedure
Issue: Unreponsive UI
Collection procedure: Collect the HAR file in Chrome and check for high CPU or memory usage.
Issue: Service restarted unexpectedly
Collection procedure: Collect the journalctl log and check CPU and memory usage.
Issue: Docker errors
Collection procedure:
1. Collect the journalctl log.
2. Collect Docker stats: sudo docker stats --no-stream
3. Collect Docker info: sudo docker info
4. Check for high CPU or memory usage.
Issue: High CPU usage
Collection procedure: Perform a CPU profile dump when requested by the Cortex XSOAR engineering team..
Issue: High memory usage
Collection procedure:
1. Collect the database stats.
2. Run the Linux top command to gather additional data on memory usage.
3. Perform a server memory dump when directed to do so by the Cortex XSOAR engineering team.