Categories
Cloudvue Knowledge Support Cloudvue Gateway Support Categories

Manually Updating Smartvue Software on a Cloudvue Gateway

Description 

At times it may be advantageous to manually apply production versions of Smartvue on a Cloudvue Gateway.  Here are the instructions for obtaining, transferring, deploying, and verifying that software.

Product

  • Cloudvue Gateway

Solution

  • Download the latest smartvue production software version from the support portal HERE
  • Transfer  the file to the Cloudvue Gateway
    • Note: Typically MobaXterm is used to transfer the smartvue software package to a Cloudvue Gateway but rsync can also be used, see KB #18254 for more details.
  • Rename the file to SmartvueCurrent.tar.bz2
  • Extract the tar ball to root using the command sudo tar -xf SmartvueCurrent.tar.bz2 -C /
  • Change directory to /smartvue and run the update script ./update.sh
  • Reboot
  • Verify version

Example

Categories
Cloudvue Cameras Knowledge Support Cloudvue Support Categories Products

0 KB File When Downloading Archived Video

Description 

Typically end users will access archived video via Cloudvue Web or Cloudvue Mobile. They can search for a specific date/time on a camera and then use Save Clip to export the video in one, five, fifteen or custom increments up to 2 hours. 

In certain cases this can fail and will result in a 0 KB MP4 file. 

Product

  • C2C

Steps to Reproduce 

  • Navigate to the Archive Page
  • Set the Start Point
    • Use the Date/Time fields to set the starting point or
    • Drag the green indicator bar in the timeline
  • Save Clip
    • Choose one of the preset lengths one, five, fifteen or create a custom increment up to 2 hours
    • Click Save

Expected Results 

  • An MP4 file of the video is downloaded

Actual Results

  • An MP4 is downloaded but has no video and the files size is 0 KB

Solution

If the video can be viewed in Cloudvue then it should exist either on the device or in the cloud. To determine the source you will need to open Chrome’s Dev Tool (F12 or Ctrl+Shift+J) and locate the download url being used.

  • Open the Chrome Dev Tools (F12 or Ctrl+Shift+J)
  • Use the Steps to Reproduce above but stop after setting a Start Point
  • In the Dev Tools Window
    • Select the Network Tab
    • Click the clear network log icon
  • In Cloudvue Save the desired Clip
    • Items will begin to appear in the Dev Tools network log
  • Hover over each Network Log entry to reveal the full url
  • You want the one that begins with “https://archive.cloudvue.com/camera”
    • Right click the log entry
    • Expand Copy
    • Choose copy link address
  • Open a new tab in Chrome
    • Paste the copied url into the address bar
    • It will look similar to this
      • https://archive.cloudvue.com/camera/0050f9635b40/streaming?start=1698753630603&stop=1698753660603&location=c2c
      • Note the ending, if it is =c2c then change it to =cloud or vice versa
    • Launch the modified url
    • An mp4 video file should download

URL Explained

https://archive.cloudvue.com/camera/[CAMERAS_MAC]/[ACTION]start=[EPOCH_START_TIME]&stop=[EPOCH_STOP_TIME]&location=[SOURCE]

Where

[CAMERAS_MAC] = Cameras MAC address

[Action] =

  • streaming? = playback/stream the video
  • download? = download the video
[EPOCH_START_TIME] = Epoch start time in milliseconds

[EPOCH_STOP_TIME] =  Epoch stop time milliseconds

[SOURCE] =

  • C2C = Cameras microSD card
  • Cloud = Cloud Storage
Categories
User Guides Documentation exacqVision EDGE exacqVision Server Categories Products

Edge Plus Archive Options

exacqVision Edge Plus Archiving currently supports SMB archiving targets.

Edge Plus does not currently support Cloud Drive or Amazon S3 archiving.

<br>

Categories
Knowledge Support Cloudvue exacqVision EDGE Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Webservice Categories exacqVision Hardware Products exacqVision Integrations

PortCheck Utility

When troubleshooting TCP/IP connectivity issues, it is often helpful to confirm that the network path is open over a specified port and that there is no interference from a firewall or antivirus. This also rules out software level problems that may be causing a failure to connect.

While there exists many utilities to accomplish this task (telnet, putty, nmap, etc…), often these utilities aren’t previously isntalled and can’t be accessed when troubleshooting.

This utility will attempt to make a TCP connection to a specified IP Address or hostname over a specified port and return either success or failure.

PortCheck – Windows

PortCheck.bat

If you are unable to transfer the file, the contents can be copy and pasted into a file manually and run from command line.

::PortCheck.bat
::This utility will check the network path to the specified IP address/Hostname.
::It will accept the first argument as the IP Address/Hostname, and the second argument as the port.
::Author - Isaac Penrod

@echo off

set $IP=%1
set $PORT=%2

IF "%~1" == "" set /p $IP="Enter the IP Address or Hostname: "
IF "%~2" == "" set /p $PORT="What TCP Port: "
set $COMMAND="^(New-Object System.Net.Sockets.TcpClient^).ConnectAsync^('%$IP%', '%$PORT%'^).Wait^(800^)"
echo.
echo Checking connectivity to %$IP%:%$PORT%
echo If the network path is open and something is listening at that location, the result will be "True"
echo.
powershell -command " %$COMMAND% "
echo.
pause

PortCheck – Linux

portcheck.sh

If you are unable to transfer the file, the contents can be copy and pasted into a file manually and run from terminal.

You will also need to make the file executable with – chmod +x portcheck.sh

#!/bin/bash
#This utility will check the network path to the specified IP address/Hostname.
#It will accept the first argument as the IP Address/Hostname, and the second argument as the port.
#Author Isaac Penrod

IP=$1
PORT=$2

if test -z "$IP"
then
read -p "Enter the IP Address or Hostname: " IP
fi

if test -z "$PORT"
then
read -p "What TCP Port: " PORT
fi

echo
echo Checking connectivity to $IP:$PORT
echo If the network path is open and something is listening at that location, the result will be "success"
echo
timeout 2 bash -c 'if > /dev/tcp/'$IP'/'$PORT'; then echo success; fi'
if [ $? != "0" ]; then
echo failure
fi
echo

Arguments

This utility will also accept command line arguments.
$1 – IP Address/Hostname
$2 – Port

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories

Dropping and Creating the smartvuedb Database

Description 

At times it may be necessary to drop (delete) and create the smartvuedb database.  WARNING VIDEO LOSS is expected, and except for rare occasions this should only be performed on newly deployed NVRs.

Product 

Cloudvue Gateway

Prerequisite

  • ssh access to the Cloudvue Gateway
  • see KB #13051 “Cloudvue SSH Tunneling” or KB #13667 “Tunneling to a Cloudvue Gateway From a Local Windows Machine”

Solution

Issue the following commands from terminal

** WARNING ** WILL RESULT IN VIDEO LOSS

<code>sudo service cron stop <br>mysqldump -u root -p smartvuedb camera camera_setting camera_view nvr_setting schedule user user_setting user_Status User_view view > /home/smartvue/smartvuedb_backup.sql <br>sudo mysql smartvuedb -s -e “drop database smartvuedb;”<br>sudo mysql -s -e “create database smartvuedb;”<br>sudo -i <br> bash /opt/smartvue/services/nvr-database-migrate/installer.sh<br>bash /smartvue/updater.sh<br>mysql -u root smartvuedb -p < /smartvue/mysql/multi-tables_smartvuedb_backup_file.sql<br>exit<br>sudo service cron start</code>


Command Explanation

cron stop – Stops scripts from being launched by cron during this process

msyqldump – (Optional) can be used to create a backup of specified tables within the existing smartvuedb database

drop database smartvuedb – Removes the existing smartvuedb database

create database smartvuedb – creates an empty smartvuedb database

sudo -i – switch to root user

installer.sh – runs the installer script which sets permissions for smartvuedb and will return the following lines if successful

++ pwd -P <br>+ SERVICE_DIR=/root <br>SERVICE_DIR=/root <br>SMV_NVR_DB_USER=root <br>/root/node_modules/db-migrate/bin/db-migrate up <br> /opt/smartvue/services/nvr-database-migrate/installer.sh: line 4: /root/node_modules/db-migrate/bin/db-migrate: No such file or directory <br>exit 127

updater.sh – runs the updater script which populates default values in certain tables within smartvuedb database and takes several minutes to complete.

mysql -u root smartvuedb -p – (Optional) can be used to import tables previously backed up with the mysqldump

cron start – Starts cron service

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Support Categories

Remote Port Forwarding using the Reverse Tunneling Script

Description 

At times you may need to remotely access the web interface of either a Cloudvue Gateway or camera.  The following instructions can be used to establish a tunnel, gain ssh access and setup remote port forwarding via the reverse tunnel script.  Once setup you will be able to access the terminal (ssh) or the Web Interface of equipment local to the video device, such as Cloudvue Local or C2C cameras (reverse port forwarding).

Product 

  • C2C
  • Cloudvue Gateway

Solution

From Cloudvue Manager

  • Setup a Tunneling port, see “Cloudvue SSH Tunneling” KB# 13051

From your Tunneling Machine

Terminal Window #1 – Establish a Tunnel

./createTunnel.sh -t PNUM

Note: PNUM is the port number created in Cloudvue Manager


Terminal Window #2 – Establish SSH Connection

./sshTunnel.sh -p PNUM

$ watch -n 30 ls -alh

Note: PNUM is the port number created in Cloudvue Manager and the watch command is used to keep the connection from timing out use Ctrl+c to stop the watch command.

In the event the following warning appears run the full “ssh-keygen” command found in the message to clear the /root/.ssh/known_hosts file, then try establishing the ssh connection again.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@


Terminal Window #3 Establish Port Forwarding via Reverse Tunnel

./reverseTunnel.sh -p 80 -l 80

NOTE: it may be necessary to manually configure the correct tunneling port by changing ./config/tunnelInfo.txt

Categories
Knowledge Support Cloudvue exacqVision EDGE Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Mobile exacqVision Webservice Categories exacqVision Hardware Products exacqVision Integrations

Creating Documentation Tickets in Jira

New Documentation Request workflow. This applies to User Manuals, QSG’s, Integration Guides, etc…

In Jira, we can create a new ticket and set Project to Technical Communications (TCOM).

Required Fields:

  • Issue type will normally be “Enhancement”
  • Under Description:
    • Product – leave default option
    • Set Component to “Exacq”
    • Summary – as needed
    • Description – as needed
    • Set Priority – as needed
  • Under Resolution:
    • Set Label to “Documentation”

After creation assign it to Jack Murphy if it doesn’t happen automatically.

Categories
Cloudvue Cameras Knowledge Support Cloudvue Support Categories Products

Adding an Authorized Public SSH Key to a C2C

Description 

SSH access to Cloudvue C2C devices  depends  on  RSA public/private key pairs.  Public keys for L3 Cloudvue support were added into the Cloudvue production software with the release of 22.9.0 in January of 2023.   The following instructions can be used to temporarily add a public ssh key to a C2C device.  SSH public keys added in this fashion will not survive a normal Cloudvue software update.

Product 

  • Cloudvue C2C

Solution

Prerequisites

  • If one does not already exist you will need to generate an ssh key pair, see Knowledge Base Article #13051 “Cloudvue SSH Tunneling” for details
  • A copy of your public key, the contents of (~/.ssh/id_rsa.pub)

Find a Buddy

You will need to get the assistance of someone who already has ssh access to the camera to SSH into the camera and make the necessary changes

Extract Cloudvue Software

Run the following command on the C2C to extract the contents of the Cloudvue software tarball into a temporary folder for editing:

mkdir -p /tmp/tBall && tar -xf smartvue.tar.gz -C /tmp/tBall

Add Public Key

Edit the authorized_keys file and add the new public key using vi

NOTE: vi is the only text editor available

vi /tmp/tBall/home/smartvue/.ssh/authorized_keys
  • Each authorized users will be listed along with their public ssh-rsa key (see example)
  • Insert your information at the bottom of this file beginning with a comment “#” and your name then followed by a line with your public key
  • How you paste will depend  on the program you are using to SSH. In PuTTY it’s just right clicking on the window, in other terminals you may need to right-click and then choose paste in the menu that pops up.
  • vi commands
    • G – Uppercase letter “G” goes to the bottom of the file
    • o – lowercase letter “o” inserts a line below the current line and goes into editing mode
    • ⏎ – Enter key creates a new line below the current one (just putting this here to be thorough)
    • ␛ – Escape key exits “insert mode” in vi
    • :wq⏎ – colon opens up a prompt to type a command, the w  stands for “write” and will save the changes, the q stands for “quit” and will exit vi, Enter key runs the command
    • q!⏎ – If you ever need to quit without saving, leave out the w and add an ! after the q (that tells it to force quit ignoring any changes), Enter key runs the command

Recreate Tarball

Use the following command to recreate the cloudvue software tarball and cleanup temporary files

cd /tmp/tBall && tar -czf ~/smartvue.tar.gz * && cd ~ && rm -rf /tmp/tBall

Install the Cloudvue Software

This will apply the new changes.  A reboot is not necessary since we aren’t modifying any running services

tar -xf ~/smartvue.tar.gz -C /
Categories
Knowledge Support Support exacqVision Server Categories Products

CD/DVD Recorders and Disc Types

Many users have moved to transporting files via portable USB devices or cloud services. CD/DVDs are still often desired by those working with legal evidence or those in insurance and law enforcement due to their low cost and ability to be mailed or stored in flat file folders. Users with systems that do not have on-board DVD drives, or users with third-party hardware, can still utilize external DVD drives to record exported video files if needed. Article 2678 explains this. The following article provides additional information regarding drive types and media use.

When examining optical disc drives as well as the CD or DVD media used in them you will note the presence, or lack of, + and – symbols as well as various acronyms used.

Disc Formats and Capacities

The initial two or three letters inform you about the disc format.

  • CD (Compact Disc) is the older of the formats and has a capacity of around 700 MB. Originally created for music, but can be used to store data or video files if used with a compatible reader.
  • DVD (Digital Video Disc) created to provide increased capacity for video, these discs typically hold around 4.7 GB.
  • BD (Blu-Ray) created to provide even more capacity for high-definition video that requires more space, these typically store up to 25 GB.

A caveat to the capacities listed above, are DL discs, these are mentioned below with the additional acronyms.

Disc Standards (+/-)

There are two standards used for recordable DVDs, indicated by + and – symbols. DVD-R is and older format that was improved upon by DVD+R. The two formats hold similar amounts of data but the DVD+R standard provides some error checking during recording resulting in fewer opportunities for write errors.

You will only see the ± symbol on drives, not on discs, and this tells you that the drive can burn to both + and – discs. This was more important in the past, as many drives today are ±, though this should be noted if you are experiencing issues burning discs since older DVD+R and DVD+RW drives were unable to record to DVD-R and DVD-RW media and vice versa.

Disc Capabilities

The acronyms following the + or – inform you what the disc is capable of, as follows:

  • ROM (Read-Only Memory), as the name implies these are read-only and come from a production facility with the data already on them. Many users simply drop the ROM altogether and refer to these as simply, CDs, DVDs, or Blu-rays.
  • R (Recordable) indicates that the disc is recordable a single time. Once written to, it cannot be recorded to again.
  • RW (Rewritable). In a compatible drive, these discs can be written to more than once.
  • RE (Recordable Erasable), this is essentially the same as RW but used for rewritable Blu-ray discs.
  • DL (Dual Layer), usually appearing last, you may note some discs that display DL, which stands for Dual Layer. These discs will hold twice as much data, DVDs 8.5 GB and BDs 50 GB. Note, however that dual layer DVDs are NOT the same as double-sided DVDs that are flipped over to record on both sides of the disc.

Disc and Drive Compatibilities

The chart below aligns the drive type along the left-hand side with the optical media type listed across the top.

Drive Type Disc Type
CD-R CD-RW DVD-R DVD-RW DVD+R DVD+RW DVD+R DL BD-R BD-RE BD-R DL
CD-ROM Read Read
CD-R Read/Write Read
CD-RW Read/Write Read/Write
DVD-ROM Read Read Read Read Read Read Read
DVD-R Read/Write Read/Write Read/Write Read Read Read Read
DVD-RW Read/Write Read/Write Read/Write Read/Write Read Read Read
DVD+R Read/Write Read/Write Read Read Read/Write Read Read
DVD+RW Read/Write Read/Write Read Read Read/Write Read/Write Read
DVD+R DL Read/Write Read/Write Read Read Read/Write Read/Write Read/Write
BD-ROM Read Read Read Read Read Read Read Read Read Read
BD-R Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read Read
BD-RE Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read
BD-R DL Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write

<br>

Troubleshooting

If experiencing problems burning discs, as mentioned above, be sure that the optical media being used is compatible with the drive being used.

Check that any external and/or third-party drives are recognized by the system and have any necessary drivers installed.

Article 2619 discusses the quality of the media.

<br>

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