Category: Uncategorized

Categories
Knowledge Support exacqVision Server Products Uncategorized

False Drive Offline status on some Q-series models

Description 

Some drives may show an “offline” status on the hardware tab in ExacqVision Client when Server Version 23.03.1.0 is installed on Q-series models, though data can be read from and written to the drive.

Note: This issue manifests itself cosmetically by appearing as if the drive is offline but has no bearing on functionality for video searching.

Product 

ExacqVision Server Version 23.03.1.0

Steps to Reproduce 

Update to Server Version 23.03.1.0 from a previous server software version.

Expected Results

Drives should populate hardware tab with a healthy status.

Actual Results 

One or more drives may appear as “Offline” on the hardware tab.

Solution

Update to ExacqVision Server 23.03.2.0 if SSA is current and up to date, or alternatively rollback to ExacqVision Server 20.12.8.0 as a workaround.

AES-457


Categories
Knowledge Support Support exacqVision Server Categories Uncategorized

Moving Eventpi.DB file to New Drive

*** INTERNAL USE ***

Description 

We have found that event links based on triggers from AI Object Classification events flood the eventPI database resulting in the OS drive being filled in a short amount of time. Periodic unexpected crashes, system reboots and increased memory usage have resulted. This happens when the amount of AI metadata captured in the eventPI database exceeds the available free space on the drive.

Product 

  • exacqVision Server [All versions]

Prerequisites

  1. Follow Best Practice recommendations as outlined in Analytic Metadata Best Practices
  2. If your license allows, update the exacqVision Server and Client instances to 23.09 or higher to take advantage of the Maximum Days to Keep Bounding Box Metadata control. Try this solution prior to moving the eventpi.db.
    Maximum Days to Keep Bounding Box Metadata Explained
  3. Moving the eventpi.db should be considered an extreme final effort reserved for those that insist on long term retention of large amounts of metadata.
  4. When moving eventpi.db, you should only do so onto a newly installed NVMe or SSD drive designed for frequent writes. We strongly advise selecting drives with specs of 2500 TBW (Terabytes Written) or higher. Systems without available NVMe slots, such as the 4U A-Series, will need to rely on Internal NAND SSD.
    • Recommended WD Red options:
      • NVMe – WDS200T1R0C
      • NVMe – WDS400T1R0C
      • SATA SSD – WDS400T1R0A

WARNING: We DO NOT recommend by any means, moving the database onto a video recording drive.

Solution

NOTE: If your license allows, update the exacqVision Server and Client instances to 23.09 or higher to take advantage of the Maximum Days to Keep Bounding Box Metadata control. Try this solution prior to moving the eventpi.db.
Maximum Days to Keep Bounding Box Metadata Explained

Move the eventpi.db database according to the following procedure:

  1. Stop Server Service
  2. Go to C: > Program Files > exacqVision > Server > eventpi (there is a Database File and XML Document named “eventpi”; you want Database File)
  3. Copy eventpi.db to new Volume location
  4. Modify eventpi.xml ‘DatabaseName’ attribute to new db path (If no “DatabaseName” attribute inside the <Events…> node then add it to the Events node
  5. Restart Server Service
  6. Conduct a search to make sure its working,
  7. Monitor/View new eventpi.db size and make sure it is growing
  8. The eventpi.db in the original location can now be removed

eventpi.db File

eventpi.xml (Modify Database Name)

Related Articles

AESW-5987

Categories
Sales Materials Cloudvue Documentation Cloudvue Access Control Categories Products Uncategorized

ioSmart Cloud Access Control Opens More Than Doors

ioSmartMorethanDoors-1.pdf
Categories
Knowledge Support Support Uncategorized

How to capture the traffic from the terminal via Tshark

How to capture the traffic from the terminal via Tshark

Discription

The following steps will show you how to capture the traffic data via the terminal using Tshark

Steps

  • Updating the repositories and installing tshark.
sudo apt update
sudo apt upgrade


sudo apt install tshark
  • You can check the NIC on your machine via the following command. 
sudo tshark -D
  • To run the tshark via terminal capturing from all NICs and saving the captured data to the PCAP file extension.
sudo tshark -w /tmp/tshark.pcap -i any
  • You can capture the traffic for a specific host from a specific NIC
sudo tshark -w /tmp/tshark.pcap -i INTERFACE host IPADDRESS

Where INTERFACE is the specific Interface found earlier with tshark -D and IPADDRESS is the  IP address of interest

  • Keep it running for 10 mins “More/Less”, then Press Ctrl-C
  • You can check the captured file info via the following command line.
sudo ls -lha /tmp/tshark.pcap
  • You can check the data inside your PCAP file via terminal 
sudo tshark -r /tmp/tshark.pcap
  • Download the file, and then you can check it from your machine via Wireshark
Categories
Knowledge Support Support Categories exacqVision Hardware Products Uncategorized

Windows 10 Hostname

Description

From the June 2022 release to the March 2023 release, the Windows 10 hostname will be the default randomized/generated one by Windows, usually something like “DESKTOP-XXXXXXX” instead of the serial number, which either “ERXXXXXXXX” or “CCPXXXXXXXX”.  The fix is planned for the March release of 2023.

This issue affects images for the following release cycles:
June ’22
Sept ’22
Dec ’22

Production begins shipping with the new image about a month after the initial release. So this issue effects machines built between July 15th 2022 through April 14th of 2023.

This only affects/affected Windows 10 and not Windows Server.

Solution

There are several ways to update the hostname in Windows. Below are steps to change the hostname using Powershell.

  1. Open Start menu.
  2. Type Powershell, then right-click on Windows Powershell and select Run as administrator.
  3. Locate the Serial Number of your machine using the sticker on the side, then type the following to update the hostname (replacing <SerialNumber> with your actual Serial Number):
    Rename-Computer -NewName "<SerialNumber>"
  4. Type the following to restart the machine:
    Restart-Computer
Categories
Uncategorized

EM failover is not moving the security integration list to the spare server.

Description 

When the protected server goes down, and the EM server moves the configs to the Spare server, it will not move the Security integration list to the Spare server.

Product 

ExacqVision Server 32bit

Steps to Reproduce 

Installing ExacqVision 32bit version and trying to failover to it

Solution

Installing ExacqVision server 64bit version

Categories
Uncategorized

Exacq Server is not booting after the windows update reboot.

Description

-When updating Windows 10 and rebooting the Exacq unit, it will not come back to boot up again and has to power off manually and power on the unit again on Motherboard “ASRock H110E1” with Firmware version 1.50

Solution

The Motherboard BIOS Firmware needs to be updated to version 1.60A

The instructions to update the Firmware will be found on KB 12490

Categories
Exclude from Global Search Uncategorized

Log Reference Template

Actual log example (Title of KB and first line should match)

Description

Describe

Notes

Notes, suggestions, KB’s, examples, etc…

REMOVE THIS SECTION

Categories Selections:
Exclude from Global Search
Categories
__Products
____%product%
Logs
__Plugin
____%plugin% (use ‘GerericCameraPI’ for things that apply to all/many camera plugins
__Log Level
%loglevel%
Tags are optional but we may use the Internal/Level2/Guest in the future to hide some from public

Categories
Knowledge Support Release Notes Support Other exacqVision Client Categories Products Uncategorized

exacqVision Client Development Release Notes

Public

Categories
Knowledge Support Release Notes Support Other exacqVision Server Categories Products Uncategorized

exacqVision Server Release Notes