Skip to main content

Troubleshooting Scans

Common issues and solutions for scan execution problems in DeepTraq.

Accessing Scan Diagnostics​

When scans fail or encounter errors, use the Actions menu (three-dot icon) in the History tab to access diagnostic information.

Actions Menu Options​

Download: Export scan results and reports for offline analysis and documentation.

Output: View detailed technical output and logs from the scan execution.

Error: Access comprehensive error information for failed scans.

Viewing Scan Output​

The Output option provides access to complete technical evidence and logs generated during scan execution.

Output Modal Window​

Display: Terminal-style interface showing raw scan output with formatting

Content Structure:

  • Vulnerability descriptions and findings
  • Error codes and HTTP responses
  • Security check results
  • Configuration findings
  • Technical metadata

Additional Information:

  • CPE (Common Platform Enumeration): Platform identifiers
  • QOD (Quality of Detection): Numerical reliability score
  • Technical parameters and values

Features:

  • Expandable sections for better readability
  • Code-style formatting with monospace font
  • Collapsible vulnerability outputs
  • Status indicators with checkmarks
  • Raw unfiltered scan engine output

Understanding Scan Errors​

For scans with "Scan Submit Error" status, the Error option provides detailed diagnostic information.

Error Modal Window​

Header: "History scan errors"

Job Identifier: Unique job ID with execution timestamp

Error Information Includes:

  • Error Type: Specific classification (e.g., ECONNRESET, network errors, authentication failures)
  • Error Message: Human-readable description
  • Scanner Information: Which scanning engine encountered the error
  • Technical Details: Complete error payload with connector information, service accounts, authentication endpoints, and configuration parameters

Features:

  • Expandable sections for easier navigation
  • Complete technical stack trace
  • Raw error logs for detailed troubleshooting

Common Scan Issues​

Scan Submit Errors​

Symptoms: Status shows "Scan Submit Error" with red badge

Causes:

  • Network connectivity issues
  • Invalid credentials or expired tokens
  • Insufficient permissions
  • Target hosts unreachable
  • Configuration problems

Resolution Steps:

  1. Click three-dot menu and select "Error"
  2. Review error message for specific failure reason
  3. Check network connectivity to target hosts
  4. Verify credentials and permissions
  5. Ensure scan configuration is correct
  6. Re-run scan after addressing issues

Scan Not Started​

Symptoms: Status shows "Scan not started" with yellow badge

Causes:

  • Scan scheduled for future time
  • System resource constraints
  • Queue backlog

Resolution Steps:

  1. Check scan scheduling settings
  2. Verify scan is not waiting for scheduled time
  3. Manually trigger scan using play button
  4. Contact support if issue persists

Network Errors​

Symptoms: ECONNRESET or network timeout errors in logs

Causes:

  • Firewall blocking scan traffic
  • Target hosts offline or unreachable
  • Network latency or instability
  • DNS resolution failures

Resolution Steps:

  1. Review error output for specific network errors
  2. Verify target hosts are online and accessible
  3. Check firewall rules allow scanning traffic
  4. Test network connectivity manually
  5. Verify DNS resolution for target hostnames

Authentication Failures​

Symptoms: Authentication or credential errors in scan output

Causes:

  • Expired or invalid credentials
  • Insufficient IAM permissions
  • Service account configuration issues
  • API token problems

Resolution Steps:

  1. Check error details for authentication specifics
  2. Verify credentials are current and valid
  3. Review IAM permissions for scan requirements
  4. Update service account configuration
  5. Regenerate API tokens if needed

Incomplete Scan Results​

Symptoms: Scan completes but missing expected findings

Causes:

  • Partial scan execution
  • Target scope too narrow
  • Services not responding
  • Scan timeout issues

Resolution Steps:

  1. Review scan output for completion status
  2. Check duration to ensure scan finished
  3. Verify all target hosts were scanned
  4. Expand scan timeout settings if needed
  5. Re-run scan with adjusted parameters

Using Diagnostic Information​

For Internal Troubleshooting​

Review Output Logs: Check complete scan output to understand what was scanned and any issues encountered

Analyze Error Messages: Read error details to identify root cause of failures

Check Technical Details: Review CPE, QOD, and other metadata to verify scan accuracy

Compare Historical Scans: Use previous successful scans as baseline to identify what changed

For Support Requests​

Collect Error Information: Export or screenshot error details from Error modal

Include Job ID: Provide unique job identifier from error logs

Document Symptoms: Describe what you expected vs. what occurred

Attach Output Logs: Include relevant portions of scan output

Note Configuration: Share scan settings and target information

Prevention Best Practices​

Regular Validation​

  • Test scan configurations on non-production systems first
  • Verify credentials before scheduling production scans
  • Check network connectivity to targets periodically
  • Monitor scan history for patterns of failures

Configuration Management​

  • Document scan configurations and requirements
  • Keep credentials updated and rotated regularly
  • Review and update firewall rules as needed
  • Maintain current IAM permissions

Monitoring​

  • Check scan status regularly in History tab
  • Set up notifications for scan failures
  • Review error logs promptly
  • Track resolution of recurring issues