Categories
exacqVision Enterprise Products

Vulnerability Update for EM for Apache

IMPORTANT** Please look at the below notes before updating SOLR APACHE.

Starting with December 2021 (20.12 build) we have included an update for the Apache updates via a pop up during installation to update Apache to version 2.4.51.
IMPORTANT**
It is important to note that During the Apache upgrade it will backup the entire apache2 folder creating a folder apache2.old. The install does not modify any added files or folders as it will essentially unpack the new Apache upgrade zipped folder. This means during an Apache upgrade all configuration files will be unpacked and reconfigured according to a normal enterprise manager install. If there was custom modification done to any configuration files it will have to be manually migrated over to the new configuration files from the apache2.old directory.

The Dashboard will not update Existing Solr Apache so it is recommended that you update using the installers found on our site.
https://www.exacq.com/support/downloads.php


In addition 32 bit will no longer be supported for December release.

Ubuntu is not supported by the installer. A manual Upgrade is requires and will need to be performed.

Categories
Knowledge Support exacqVision Enterprise Support Categories

exacqVision Enterprise Manager Domain User Search Fails Even After Authenticating With AD

Searches in EM fail after authenticating to AD. When they do a search to add a new user, it will not search or filter by the users name or says ‘no results found’

Solr Apache is reporting a corruption with the indexed files, so we cleared the indexed data and recreated it.

Linux Steps…
1. Reboot the EM Server
2. Open a command prompt and type the following followed by the <ENTER> key

sudo service enterprise-datarolloff stop
sudo service enterprise-importer stop
sudo service enterprise-webservice stop
sudo service enterprise-sendemail stop

You also need to stop the Solr-Apache services

cd /usr/local/exacq/esm/apache_solr/apache-solr/bin

sudo ./solr stop -p 8983 if it doesn’t work, then try sudo ./solr stop -all

cd/usr/local/exacq/esm/apache_solr/apache-solr/server/solr/collection1/data

sudo mv data data2

Restart Start the EM Services

sudo service enterprise-datarolloff start
sudo service enterprise-importer start
sudo service enterprise-webservice start
sudo service enterprise-sendemail start


You also need to start the Solr-Apache services
cd /usr/local/exacq/esm/apache_solr/apache-solr/bin
sudo ./solr start -force (this forcefully restarts solr)

OR

Windows Steps…

  1. Open up Windows Services
  2. Stop all four EM services, SolrApache and SolrJetty
  3. Browse to C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache-solr\server\solr\collection1
  4. Rename the Data folder to Data2
  5. Restart all four EM services, SolrApache and SolrJetty
  6. Go back in to EM and navigate to Domain and click on Refresh Domain, which will resync the domain
  7. Go to Users and click on Add New User and try to do a search
  8. Verify you can search by name

Categories
Knowledge Support exacqVision Enterprise

exacqVision Enterprise Manager Time Restricted Notifications are not received

If email notifications are not being received as expected check the Rule for any time-based restrictions such as “lasts for at least” or “lasted for at least”.  Then verify the triggering event actually was activated for the specified amount of time.   

For example, say we are using the following rule:
If “Camera disconnected” lasts for at least, 300 seconds IN any group ON any server FOR any camera send email immediately to johndoe@email.com.

We can observe the camera drop in live view, but a notification is not received. By looking at the exacqVision Server logs we find the following sequence of events

2021-06-26 16:55:51 (GMT-0700) SamsungPI Warning ELEVATOR LOBBY: stream timeout.
2021-06-26 16:55:51 (GMT-0700) SamsungPI Verbose ELEVATOR LOBBY Context 0 is NOT connected.
2021-06-26 16:56:57 (GMT-0700) SamsungPI Verbose ELEVATOR LOBBY Context 0 is connected.

In this case, a notification WOULD NOT have been sent because the camera reconnected within 300 seconds.   This would be true if any of the time related restrictions were used with a 300 second setting.

If a notification is desired for future events of this type the duration of the event i.e., 300 seconds would need to be lowered, or the time element could be removed and one of the following used instead “starts”, “stops” or “starts or stops”.

<br>

Categories
Knowledge Support Support exacqVision Enterprise Categories

EM Postgre to SQL Database Move

Although 3rd party instructions may exist for this process, converting from Postgre to MS SQL is currently not recommended or supported.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Stuck Pinned Spare/Data Restore Pending due to firewall blocking vfba process

Exacq Support has identified an issue preventing fail-back due to VFBA.exe being blocked; which uses port 28774.

Windows Versions

It is recommended to create both inbound and outbound Windows firewall rules on the SPARE server to allow communications through port 28774 for the Windows Firewall.

** Due to issues with the Window OS, disabling Windows Firewall does not allow this thru, and the creation of the FIREWALL rule is required. **

On a Windows Machine, do a search for FIREWALL and click on the option for Windows Firewall with Advanced Security.

Click on the inbound/outbound rules and select NEW RULE from the right.

Highlight Port and click NEXT

Select Port 28774 and click next.

Be sure to repeat this for BOTH Inbound and Outbound connections.

In some cases it may be necessary to “whitelist” ExacqVision components (core.exe, edvrclient.exe, including .ps and .psi file types, and ExacqVision Enterprise System Manager components) Enterprise Manager, Server and Client software along with vfba.exe within any used Antivirus configuration.

Categories
Video Library Demo exacqVision Enterprise Categories Products

2017-03-23 ESM Overview

Categories
Knowledge Support Documentation Support exacqVision Enterprise

PostgreSQL 9.6 End of Life

PostgreSQL 9.6 is currently bundle with exacqVision Enterprise Manager.  This version will reach end of life in November 2021. 

The PostgreSQL Global Development Group will release the final update for 9.6 on November 11, 2021.  See their versioning page for details at https://www.postgresql.org/support/versioning/

AWS has announced PostgreSQL 9.6 on will reach end of life on January 31, 2022.  See the forum announcement at https://forums.aws.amazon.com/ann.jspa?annID=8512 for more details.

Preparation and testing for a migration to a newer version of PostgreSQL is ongoing and will be bundled in exacqVision Enterprise Manager.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Enterprise System Manager Shell

To open Enterprise Manager Shell in Windows, run Command Prompt as an administrator and change directories to the installation directory by running the following command:

cd C:\Program Files\exacqvision\enterprisemanager \enterprisesystemmanager\

Then type:

enterprisesystemmanager.exe shell

To open Enterprise Manager Shell in Linux, open a Terminal window and type:

sudo /usr/local/exacq/esm/enterprisesystemmanager shell

<br>

The following commands can be used in the shell:


Exit the Shell.

Exit with ‘Ctrl+Z’


Test SMTP settings

from evemail.models import EmailServer
es = EmailServer.objects.all()[0]
con = es.get_connection()
con.open()


You will see details about any connection errors, or an email connection object that is opened using the information in ESM.


Show the number of emails in the queue

from evemail.models import EventEmail, EventBatchEmail
EventEmail.objects.count()
EventBatchEmail.objects.count()


Delete emails in the queue

from evemail.models import EventEmail, EventBatchEmail
EventEmail.objects.all().delete()
EventBatchEmail.objects.all().delete()


Reset the Enterprise Manager Root Admin user password

*** This should never be given out to a customer ***

Stop all Enterprise Manager services, then enter shell. Once in shell, enter the following commands:

from organization.models import EnterpriseUser
u = EnterpriseUser.objects.get(username="admin")
u.set_password("admin256")
u.save()
import sys
sys.exit()

Start all Enterprise Manager Services

NOTE: It may be necessary to replace the field username=”admin” above with the actual username configured at time of installation, if not using default value. In example: username=”enterpriseadmin”


Deleting a Failover Group 

from failover.models import *
FailoverLog.objects.all().delete() 
FailoverGroup.objects.all() 

This will give you a list of failover groups.
Then you can delete the group at the proper index using 

FailoverGroup.objects.all()[0].delete() 

​Replacing the number with the index of the group to delete, of course 

import sys
sys.exit()

AES-70


Undeleting data removed using the web GUI

from server.models.core import Server
from django.utils import timezone
readd_date = timezone.now() - timezone.timedelta(days=2)
servers = Server.objects.filter(removalDate__gt=readd_date)
for server in servers:
    server.undelete()

Servers deleted through the GUI are flagged for deletion. As long as the datarolloff retention period has not passed, the servers deleted within the last 2 days can be undeleted with the above commands. You can adjust the days needed if the customer needs something from prior to that by adjusting the “days” number in line 3.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Resetting a Password in Enterprise System Manager

**This should NEVER be given out to a customer**

To reset the password for a user in Enterprise Manager, complete the following steps for Windows or Linux.

<br>

Windows

  1. Stop all six Enterprise Manager services.
  2. Open Command Prompt as Administrator.
  3. cd C:\ProgramFiles\exacqvision\enterprisemanager\enterprisesystemmanager
    Note: EnterpriseSystemManager can be in D:\ Make sure to validate where the EM folder is installed.
  4. Run the command enterprisesystemmanager.exe shell
  5. In the shell, type the following:
    from organization.models import EnterpriseUser
    u = EnterpriseUser.objects.get(username=”admin”)
    u.set_password(“Support.1”)
    u.save()
    import sys
    sys.exit()

    NOTE: It may be necessary to replace the field username=”admin” above with the actual username configured at time of installation, if not using default value. In example: username=”enterpriseadmin
  6. Restart Enterprise Manager services and log into EM with the new password.

<br>

Linux

  1. Stop all six Enterprise Manager services.
  2. To open Enterprise Manager Shell in Linux, open a Terminal window and type: sudo /usr/local/exacq/esm/enterprisesystemmanager shell
  3. In the shell, type the following:
    • from organization.models import EnterpriseUser
    • u = EnterpriseUser.objects.get(username="admin")
    • u.set_password("Support.1")
    • u.save()
    • import sys
    • sys.exit()
    • Exit Terminal and start all six Enterprise Manager Services

      NOTE: It may be necessary to replace the field username=”admin” above with the actual username configured at time of installation, if not using default value. In example: username=”enterpriseadmin

**If unable to login to the EM Web Portal on a Linux box after resetting the password, either user a different browser or upgrade repositories

sudo apt update

sudo apt upgrade

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

EM GUI displays red status banner indicating data stopped importing

Issue

The Enterprise Manager browser interface will display red banners indicating that data stopped importing, data stopped rolling off, and sendmail has stopped when the OS time on the client/browser workstation doesn’t match the time on the EM server.  Below are screen shots illustrating the issue.

<br>

Resolution

Ensure that the EM server and client workstation are syncing to a time server or manually adjust client workstation time to match EM server time