Categories
Knowledge Support Support Categories Products exacqVision Hardware

Dirty Cache not allowing OS to boot

If a customer calls with a system not booting and is prompted to hit X to clear the Cache, please see this forum on current suggestions and provide feedback.

https://forum.exacq.com/t/current-issue-dirty-cache/74

Note: This has not been fully root caused yet but recommendations can be found here:

Categories
Video Library Knowledge Support Demo Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Mobile Categories exacqVision Webservice exacqVision Hardware Products

2021-03 March Quarterly Release Training

Feature – Axis Body Worn Cameras

  • Client – Enhancement – Axis body worn camera support. #21843
  • Client – Enhancement – Added support for search only cameras and audio for Axis body worn.
  • Client – Enhancement – Added config options for axis body worn cameras.
  • Server – axisbwpi – Add support for the Axis body worn camera system #21204

Feature – Large Blobs

  • Client – Enhancement – Support Large Blobs. #21842
  • Server – Enhancement – streampi – Support for maps and other blobs of sizes exceeding 2MB #18412

Client

  • Enhancement – Automatically create a system event linkage for source groups in event monitoring. #22396
    • User will be warned if trying to delete an automatically created Event Link
  • Enhancement – Allow selecting multiple files at once in Add Person #21332
  • Enhancement – Updated Immervision libraries for newer camera model support. #22384
  • Enhancement – Upgraded Oncam dewarping library for newer camera support. #21914
  • Enhancement – Added Linux x64 support for Oncam dewarping. #21914
    • Windows and Linux only
    • Mac library not ready
  • Enhancement – Enterprise LDAP: enable local user accounts checkbox if connected as a local user AND local user accounts are disabled #21933
  • Enhancement – For enterprise and system LDAP pages, disable the option to disable local user accounts if current use is local #21933
  • Enhancement – Added timeout message to export log if we timed out waiting for system or audit logs during support export. #22417
    • If cancelled, then the next export wouldn’t include the Server logs.

Server

  • Feature – rtspserverpi – Add support for video search #20747
  • Backend search capabilities without needing to use our API.
    • Primarily for future projects.
  • Enhancement – AxisPI – Support events for Axis Fence Guard #22465
    • Similar to Line Cross.
    • Must be configured in the camera with a browser.
  • Enhancement – AxisPI – Improve performance of downloads from edge storage #22303
    • 5m sub-operations to split up data and better protect against lost video due to network disconnection.
    • Parallel downloads – Off by default, must be configured.
  • Enhancement – AxisPI – change to more efficient log format #22502 §Similar to Onvif/Illustra
  • Enhancement – Illustra3pi – Correctly identify Holis cameras #22222
    • Some were improperly added from the scan as Onvif before.
    • Still using the Illustra3 plugin but will show up in the Client as Hollis.
  • Enhancement – onvifnvcpi – Add Support for Vivotek MA9321/2-EHTV #22373
    • Other json updates for specific cameras as well.
  • Enhancement – onvifnvcpi – Add the Subscription Renew command to pullpoint if MaxNotificationProducers capability is detected. #22165
    • Resolves some of the “Motion not supported” messages.
  • Enhancement – onvifnvcpi – Add override for cameras that prefer GetCapabilities instead of GetServices. #20941
  • Enhancement – plugins – hardened config persistence against unexpected shutdowns #15944
    • Changes in how config file gets edited and saved.
      • *.xml.bak created first
      • Changes saved to *.xml.pending
      • *.xml.pending then renamed to *.xml
    • Changes in how config files are loaded.
      • *.xml.pending is always most recent save. Load it first
      • Then try *.xml
      • Then try *.xml.bak
    • log load/save errors for core.xml.

Web Service

  • Enhancement – Add ability to monitor and remove temporary files. #22276
    • Thumbnails and Search results
    • Now cleaning up after 12 hours.
  • Enhancement – Add RTSP URI to camera endpoint. #22568
    • API feature – no UI
    • Will be utilized by Integrations
  • Enhancement – Sort available update versions, newest first. #18059

Enterprise Manager

  • Enhancement – Made licensing page more responsive #19096
  • Enhancement – Added filter to add user group lists #22528
  • Enhancement – Added extra server fields to server detail and list pages #19153
Categories
Knowledge Support Support Categories Products exacqVision Hardware Uncategorized

SCN-00000020 – G-Series PoE update

SCN #SCN-00000020
Title of SCNG-Series PoE update
TRAC #
Effective VersionLaunched February 15, 2021
Products AffectedLC UNA
Reason for Change (Summary)Now available in 4 – 8 – 16 Ports

Change

The G-Series PoE line, which consolidates/replaces the M-Series and LC UNA, is now available in a 16 Port option.  The existing 4 and 8 Port machines will now come with Professional licenses as well.  LC systems are no longer being manufactured.

Specs:

  • Intel Atom
  • 4GB DDR RAM
  • Dual Gb NICs
  • HDMI and DP monitor outs
  • One 1-12 TB 3.5inch HDD
    • 4 Port – max 4 TB
    • 8 and 16 Port – max 12 TB
  • 16 Port includes OS on SSD
  • 4 USB Ports
    • x2 USB 2.0 on Front
    • x2 USB 3.0 on Back
  • Ubuntu 18.04
    • Includes the standard exacqVision Linux image comparable to Z, S, A and Q Series machines.
  • PoE Power

16 Port

8 Port

4 Port

Additional Documentation

Product Page

Quick Start Guide

Other information

This machine should be troubleshot similar to any machine with the standard exacqVision Linux image.

The Power Supplies between the different versions are NOT interchangeable.

The 16 Port includes OS-on-SSD, the 4 and 8 Port do not.

Both graphics connections can be used simultaneously.  If 2 monitors are connected, the 2nd is automatically configured for Extended Desktop.

PoE budget warning light on front of machine.

Categories
Knowledge Support Support exacqVision Server Categories Products

Firmware Issue Notification and Solution

exacqVision Dealer,

You are receiving this email because we believe you may manage an exacqVision server affected by the issue below.

Exacq has been made aware of a firmware issue affecting 2TB Western Digital drives. This issue manifests itself on our exacqVision servers as a drive in the RAID Array going to ‘Unconfigured Bad.’  While this is a recoverable error, due to the nature of the firmware issue with Western Digital, it will occur again.  The scope of when these drives were used is fairly narrow within Exacq.

<br>

How do I know if my system has the faulty RR02 software?

The only systems Exacq built using drives with this firmware were the A, Z, and S-Series servers with RAID and 2TB drives. Browse to your ‘Configuration’ page and select ‘Storage’ from the tree. Then select the ‘Hardware’ tab on the right. As you select ‘disks’ listed, you will see a firmware version listed. If this is RR02, proceed to the firmware upgrade process below. If not, no action is needed.

<br>

What do I do if I have RR02 firmware?

  • Download the OS-appropriate compressed file (Windows or Linux) to the desktop from below.
  • Uncompress the file using the appropriate method below:
    • Windows: Right click WD_Windows.zip and choose “Extract All…” and put it on the desktop
    • Linux: Open Terminal and type the following in order
      • cd ~/Desktop
      • sudo tar -xvf WD_Linux.tar.gz
  • Stop the exacqVision Server service.
  • Open a Command Prompt or Terminal and navigate to the WD folder you unzipped in step 1.  As per below:
    • In the terminal or Command Prompt type the following in order Case sensitive
      • cd desktop [for Linux cd ~/Desktop]
      • cd WD
      • Then hit the TAB key on the keyboard and it should fill in the rest. If not, type the entire folder name.
  • Next Type:
    • Windows:
      • WD_download.exe RR04.pkg
    • Linux:
      • sudo chmod 775 WD_download.sh
      • sudo ./WD_download.sh RR04.pkg
  • Type all and then press enter to apply the firmware to all drives
    • When the process completes, type the following depending on OS
      • Windows:  WD_download.exe -list and confirm the firmware is now RR04.
      • Linux: sudo ./WD_download.sh -list and confirm the firmware is now RR04.
  • Start the exacqVision Service.  See instruction links in step 3.

<br>

Caution: Do not attempt to use this firmware on other drive families or capacities as it will not resolve the issue and may cause drive failure.

Note: In some instances, there may be a mix of drives that do not have the RR02 firmware. In these cases, you can select the individual drive ports in the command line, i.e. 1,5,17 instead of all.

If you have any problems with these instructions, contact our support team at +1-317-813-3717, or via a web form at www.exacq.com/support/form.

<br>

Firmware-Issue-Notification-and-Solution.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Replacing a Drive in an LSI 3ware RAID Array


To install a replacement drive in an exacqVision system with an LSI 3ware RAID array, complete the following steps.
<br>

NOTE: This procedure requires a Phillips-head screwdriver and approximately 20 minutes to complete.
<br>

If applicable, close the exacqVision Client software, log out of the operating system user account, and log in as an administrator. To log out in Windows, click Start and then Log Off; to log out in Linux, click the power icon and then Yes. Then select the administrator account and enter the admin password to log in.
<br>

Exit exacqVision Client and open 3DM2 so that you can verify the drive that needs to be replaced. To open 3DM2 In Windows, click Start/Programs/3Ware/Connect to 3DM2; to open 3DM2 in Linux, select the Mozilla Firefox icon in the menu bar.
<br>

Select Continue to this Website.
<br>

Select Administrator from the Login drop-down list and type admin256 as the password.
<br>

Select Maintenance from the Management menu.
<br>

Verify the drive to be replaced. Note that the drive numbering begins with zero; thus, if the page indicates that drive 3 is not present, replace the fourth physical drive.
<br>

Remove the drive to be replaced. Unlock the drive bay containing the drive by sliding the latch to release the caddy. It could look like either of the following examples.
<br>

Remove the drive by sliding it toward you.
<br>

Use the screwdriver to remove the four screws from the sides or bottom of the drive caddy.

<br>

  • Remove the drive from the caddy and place the new drive in the caddy. Secure the drive to the caddy using the screws removed earlier.
  • Insert the new drive and caddy into the system and lock the latch down. The drive will provide some resistance when the drive reaches the back of the slot. DO NOT FORCE THE DRIVE INTO THE SLOT.
  • Verify that the power light (white or green) has been activated for that drive slot.
  • Open 3DM2 as instructed previously.

    NOTE: If using Internet Explorer, you might need to enable Compatibility Mode by clicking the broken page icon:
    <br>

Verify that the drive array is rebuilding.
<br>

Close the browser and open exacqVision Client.
<br>

Categories
Knowledge Support Support Categories exacqVision Webservice Products

Manually Configuring HTTPS for Web Service Certificate and Key Path

The following steps are intended for manually setting the certificate and key path for exacqVision Web Service versions 8.4 and higher.

NOTE: Wildcard certificates cannot be uploaded through the exacqVision Web Service administration interface. However, they may be used when manually configured.

<br>

Products

  • exacqVision Web Service version 8.4 and above

<br>

Steps

  1. Find the web service configuration file:
    • Windows:  C:\ProgramData\Webservice\conf\wfe.json
    • Linux:  /etc/webservice/wfe.json<br><br>
  2. Open this JSON configuration file with the text editor of your choice.
    • Windows: Open the text editor choosing, ‘Run as Administrator’
    • Linux: Run with sudo privileges when needed.<br><br>
  3. Within this file, locate the top-level key ‘webserver’.<br><br>
  4. One level underneath the ‘webserver’ key, locate the ‘tls’ key.
    • Note: The ‘tls’ key is optional. If it does not exist, create it as such:
          "webserver": {
              "listen": 80,
              "tls": {
              }<br><br>
  5. Inside the ‘tls’ key, modify the values for the following fields (creating keys for them if they are not already present)
    • “type”:  The literal string “external” (including the quotes)
    • “listen”:  The port on which you want the web service to conduct HTTPS traffic. The default HTTPS port is 443. Provide this value as a literal number without quotes.
    • “cert”:  The absolute path to your HTTPS certificate (surrounded in double-quote markers, e.g. “/home/admin/certificates/webservice.cert”)
    • “key”:  The absolute path to your HTTPS private key (surrounded in double-quote markers as well)

      If you have followed these steps correctly, the contents of webserver key section of the wfe.json should now look something like the following:
          "webserver": {
              "listen": 80,
              "tls": {
                 "listen": 443,
                 "cert": "path/to/your/cert",
                 "key": "path/to/your/key",
                 "type": "none"
              }<br><br>
  6. Save your changes.<br><br>
  7. Restart the exacqVision Web Service.

<br>