Applies to: BLAZE

Summary

Occasionally, an issue may occur in BLAZE. This article provides the essential checks to verify overall system stability and collect baseline information for troubleshooting.

Quick Checklist

Before troubleshooting specific error symptoms, perform these checks:

• Verify overall system health
  
  Client path: Home > Health Monitoring > System Dashboard
  
  Confirm there are no critical warnings/errors and note any alerts around the time the issue occurred.
  
  
   
• Confirm license validity
  
  Path: Settings > Licenses
  
  Verify the expected licenses are present and valid (not expired / not missing).
  
  
   
• Capture a CPU / RAM utilization snapshot
  
  Take a snapshot (screenshot or exported status) of current CPU and memory usage. 
  
  If the issue is intermittent, capture both a “normal state” snapshot, and a snapshot during/near the incident.
  
  
   
• Check recording volume free space
  
  Confirm sufficient free disk space on the recording volume(s).
  
  Record which volume is used for recording and the remaining capacity.
  
  
   
• Confirm network reachability
  
  Verify connectivity between servers, clients, and the affected devices (e.g., cameras).
  
  Record basic reachability evidence (e.g., ping results).
  
  
  
  
  
  
   
• Confirm system time synchronization (NTP)
  
  Ensure all relevant servers are synchronized via NTP and show consistent time.
  
  Time drift can cause misleading log timelines and event/recording mismatches.
  
  

Collecting Baseline Information

Before filing an issue, collect the following information with logs to help speed up triage and reproduction:

• Issue description (required)
  
  What is the issue?
  How often does it happen? Include frequency, when it started, and a specific time window if known. (frequency, since when, specific time window if known)
  What is the expected/normal behavior?
  What is the product version? (Server or Client)
  What is the camera model and/or firmware version? (if applicable)
   
• System environment details 
  
  Recommended for all cases and required for severe failures.
   
• Machine hardware specifications
  
  Processor
  Memory
  Storage / drive details (vendor, model number, size)
  OS name and version
   
• Network 
  
  Network configuration overview (IPs, switches, routers as needed to understand the path) Ping test results from the server to any server/device involved in the problem (especially the affected device)
   
• Appliance product details (if applicable)
  
  Model information (e.g., Servers > General)
  Version (e.g., Help > About: Server and Client)
  
  Storage configuration:
  Number of HDDs
  Vendor / model / size
  RAID usage (Yes/No, and type if applicable)
  
  Monitor setup:
  Clone or Extend mode
  Resolution (include each monitor if using multiple displays)