Tag: Enterprise

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

ESM does not uniquely display multiple groups with the same name in rules engine

ESM does not uniquely display multiple groups with the same name in rules engine

Effected platforms

ESM 2.6 or greater

<br>

Symptom

When multiple groups with the same name exist, the user may not be able to discern the individual groups when creating rules.

On ESM versions before 3.6, all the servers that are on groups with the same name would be listed under a single displayed group on the server dropdown.

On ESM 3.6 or greater, if the number of servers on ESM are less than 500, the behavior is the same as above. If there are more than 500 servers on that ESM, the user has to click on the group in order to see the servers belonging to it, and clicking on this group shows only servers in one of the groups with that name. It doesn’t show servers in the other group that shares the same name.

<br>

Workaround

Rename groups to have unique names.

<br>

Resolution

None at this time.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM fails to process events due to server disconnect stop alert rule crashing the importer

Affected platforms

exacqVision ESM 3.7.6 or later

<br>

Symptom

If a rule is created to display an alert when the server disconnected state stops (that is, the server reconnects), the ESM importer will crash when that alert rule fires. To confirm, check the following logs:

Open the log file logfile-importer and look for an entry like the following:
[23/Sep/2015 15:06:45] WARNING [importer:101] Importer processes died for following importer ids: [2]

Next, open the log file corresponding to the importer id, in this case logfile-Importer2. Look for the following error in the log file:

Exception: Error saving

 ‘DisconnectEvent’ object

If this error is found then the ESM importer has failed due to the disconnect stop rule.

<br>

Workaround

Edit the rule to only trigger on a server disconnect state starting, or remove the rule.

<br>

Resolution

Update to exacqVision ESM version 3.8.0.89234 or higher

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

How to Reduce the ESM Importer Count

Symptom:

High CPU Usage seen on the ESM machine. CPU increases every 10-15 seconds to 99%. 

<br>

Problem:

ESM utilizes an environmental variable named ‘_ESM_NUM_IMPORTERS’. Lowering this value will limit the number of sub importers that talk to the servers. 

An example application for this use would be when there are a low number of servers for ESM to talk to but the ESM machine has a high number of CPU cores.

If you have 10 servers but 4 cores on your ESM machine, it doesn’t necessarily make sense to run an importer service on each core. But if you have 100 servers and 4 cores, it may make more sense to allow an importer to run on each core. 

Solution:

Windows:

Run CMD as an administrator, and enter the following:   setx _ESM_NUM_IMPORTERS "X" , where X is the number of importers to run.

Restart the ESM Importer service.

Linux:

You must edit the ESMImporter.conf file. On 16.04 and higher systems this is located in /etc/init.d/, on systems lower than 16.04 this is located in /etc/init/

At the top of the file add the following lines:

_ESM_ENUM_IMPORTERS="X"
export _ESM_ENUM_IMPORTERS

Replace ‘X’ above with the number of importers to run.

Save the file and restart the ESM Importer daemon. 

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

exacqCloud dashboard search for server name returns error page

There are occasions when a server name search on the dashboard on ESM returns an error page with “contact administrator” message.

<br>

If this happens

  • get the esm logfiles.
  • open logfile-websevice file
  • verify that this log file has the messages “ProtocolError: (‘Connection aborted.’, error(111, ‘Connection refused’))”

If the message above is in the log file, restart the solr service.

<br>

Restarting solr service on Windows

  • open up the windows task manager
  • click services tab
  • find solr Jetty service
  • restart solr Jetty service

<br>

Restating solr service on Linux

  • Open linux terminal application
  • Type “sudo restart ESMWebservice”, OR “sudo /etc/init.d/ESMWebservice restart”, which will restart webservice and sorl service.

Once solr has restarted, verify that you can search for a server name on the ESM dashboard.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM attempts to install postgresql even if it’s already installed

The installer for the following specific version has an option to install postgresql even if it detects a postgresql installation on the machine, however it does not work. It throws an error as it is not able to set the install path correctly.

Tested Version

3.6.0

Platform

Windows

Steps to reproduce

  • Install postgresql by hand
  • Run ESM installer, select install postgresql on dialogue popup

Expected result

Installation completes of postgresql

Actual result

Error in trying to install

Introduced Version

r82419

Work Around

Do not attempt to install postgresql if it is already installed.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Changing/Testing advanced ESM settings manually

For some more advanced settings/options on ESM, navigate to ESM installer directory/folder. Here on the commandline as an admin user, you can use the installer.exe (windows), or installer executable for different actions.

<br>

Check/Change database settings

Commands to run:

Linux:

  • sudo ./installer decrypt (will generate EnterpriseManager.tmp – View or change settings here)
  • sudo ./installer encrypt (do this only if you changed settings)

<br>

Windows:

  • installer.exe decrypt (will generate EnterpriseManager.tmp – View or change settings here)
  • installer.exe encrypt (do this only if you changed settings)

<br>

Encrypt Results:

  • -3: EnterpriseManager.tmp does not exist in the current directory
  • -2: The tmp file could not be opened
  • -1: EnterpriseManager.ini could not be opened
  • 0: EnterpriseManager.ini has been created in the current directory

<br>

Delete the EngerpriseManager.tmp file.

Note: If you have changed database settings. Restart all esm services. Preferably, starting with the importer Verify ESM is functioning as expected.

<br>

Test Migrations 

(checks conditions for running a migration and returns an integer value)

Commands to run:

  • sudo ./instaler testmigration (Linux)
  • instaler testmigration (Windows)

<br>

Results:

  • -3: no default database connectivity
  • -2: nolegacy database connectivity
  • -1: migration has already ran
  • -0: it is okay to run a migration if wanted

<br>

Run database migrations 

(runs the actual migration and returns an integer value)

Commands to run:

  • sudo ./installer runmigration (Linux)
  • sudo ./installer runmigration (Windows)

<br>

Results:

  • -1: migration succeeded

<br>

Run ESM diagnostics

Currently this will run diagnostics for Email and Domain server connectivity

Commands to run:

  • sudo installer diagnostic (Linux)
  • installer.exe diagnostic (Windows)

<br>

Update the haystack search indexes 

(adds missing entries)

Commands to run:

  • sudo ./installer update_index (Linux)
  • sudo ./installer update_index (Linux)

<br>

Test connectivity to the given database

Commands to run:

  • sudo ./installer testconnection (Linux)
  • installer.exe testconnection (Windows)

<br>

Test the given port for availability

Commands to run:

  • sudo ./installer testport [port] (Linux)
  • installer.exe testport [port] (Windows)

<br>

Results:

  • -1: no connectivity
  • 0: in use

<br>

Test the given SSL port for availability

Commands to run:

  • sudo ./installer testsslport [port] (Linux)
  • installer.exe testsslport [port] (Windows)

<br>

Results:

  • -1: no connectivity
  • 0: in use

<br>

Get an available port starting at startport

Commands to run:

  • sudo ./installer getfreeport [startport] (Linux)
  • installer getfreeport [startport] (Windows)

<br>

Get an available SSL port starting at startport

Commands to run:

  • sudo ./installer getfreesslport [startport] (Linux)
  • installer getfreesslport [startport] (Windows)

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

License expiration may show a day off in ESM

Depending on the timezone offset of the ESM server and the date of the license, it may show the expiration off by a day.

There is no way to work around this short of applying a license with the date adjusted.

The server will still function properly, though ESM may stop monitoring the server a day early.

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

How to delete a large amount of camera events from ESM

Description

Perform the following steps to remove a large amount of camera events from the ESM Postgre database:

<br>

Removing Events:

  1. Shutdown all ESM services
  2. Start command prompt as admininistrator (do not use powershell)

    Change directories to exacqVisionEsm\PostgreSQL\9.2\bin and run the following:

    pg_dump -U postgres –schema-only ESM > ESM.sql#
    psql -U postgres -d ESM
    DROP TABLE camera_cameraevent CASCADE;
    DROP TABLE report_eventid CASCADE;
    DROP TABLE event_alertid CASCADE;
    \q
    psql -U postgres -d ESM -f ESM.sql

    Note: There maybe many errors that some things already exist, which is okay
  3. Start all services

<br>

Recover the Schema (assumes current schema not intact):

  1. Shutdown all services
  2. Open pgAdmin
  3. Go to localhost > Databases
  4. Right click on “Databases” and select “New Database”
  5. Enter the name ESM2
  6. Open command prompt as admin
  7. Change directory to C:\exacqVisionEsm\EnterpriseSystemManager
  8. Enter the following commands:
    a. Installer.exe decrypt
    b. notepad EnterpriseSystemManager.tmp
    c. Change DefaultName to ESM2
    d. installer.exe encrypt
    e. installer.exe new_migrations
  9. Change directories to exacqVisionEsm\PostgreSQL\9.2\bin and run the following:
    a. pg_dump -U postgres –schema-only ESM2 > ESM.sql
    b. psql -U postgres -d ESM
    – 1. DROP TABLE camera_cameraevent CASCADE;
    c.psql -U postgres -d ESM -f ESM.sql

    Note: There may be many errors that something already exists which is okay
  10. Change directory to C:\exacqVisionEsm\EnterpriseSystemManager
    • Enter the following commands:
    • installer.exe decrypt
    • notepad EnterpriseSystemManager.tmp
    • Change DefaultName to ESM
    • installer.exe encrypt
    • Start all services
Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM downgrade fails with newly added users

Description

Downgrading ESM from 4.5.10 or newer down to 4.5.9 or earlier can cause the following error. Also the installer fails not able to communicate with database.

ERROR [installer:74] Exception in run_backward_migrations: Traceback (most recent call last):

File "", line 40, in run_migration_command

File "south_utils\run_migrations.py", line 127, in run_backward_migrations

File "south_utils\run_migrations.py", line 45, in run_migration_command

File "site-packages\django\core\management\__init__.py", line 120, in call_command

File "site-packages\django\core\management\base.py", line 445, in execute

File "site-packages\django\core\management\commands\migrate.py", line 222, in handle

File "site-packages\django\db\migrations\executor.py", line 112, in migrate

File "site-packages\django\db\migrations\executor.py", line 168, in unapply_migration

File "site-packages\django\db\migrations\migration.py", line 162, in unapply

File "site-packages\django\db\migrations\operations\fields.py", line 206, in database_backwards

File "site-packages\django\db\migrations\operations\fields.py", line 201, in database_forwards

File "site-packages\django\db\backends\base\schema.py", line 484, in alter_field

File "site-packages\django\db\backends\postgresql_psycopg2\schema.py", line 113, in _alter_field

File "site-packages\django\db\backends\base\schema.py", line 656, in _alter_field

File "site-packages\django\db\backends\base\schema.py", line 111, in execute

File "site-packages\django\db\backends\utils.py", line 64, in execute

File "site-packages\django\db\utils.py", line 98, in __exit__

File "site-packages\django\db\backends\utils.py", line 64, in execute

OperationalError: cannot ALTER TABLE "organization_enterpriseuser" because it has pending trigger events

<br>

Version Introduced

4.5.10

<br>

Platform

ESM with Postgres 9.2

<br>

Steps to reproduce

  • Setup ESM with Postgres 9.2
  • Install 4.5.10 or later
  • Add a new user to ESM
  • Downgrade ESM to 4.5.9 or earlier

<br>

Expected result

Successful downgrade.

<br>

Actual result

Failed downgrade with the error above

<br>

Work Around

  • Connect to db
  • Set ‘last_login’ for all users in table ‘organization_enterpriseuser’

<br>

Version Fixed

4.5.17

Categories
Knowledge Support Support exacqVision Server Categories Products

Adding web service using server credentials does not enter password

Description

When adding a server, the user can select to use the same credentials and address of the server when adding a web service with the server. The single server add form will not correctly capture the password. Thus, the web service will not be able to be reached.

<br>

Version introduced

4.3.13.102215

<br>

Platform

All

<br>

Steps to reproduce

  1. Add a web service by editing a server
  2. Select same server and credentials

<br>

Expected result

Able to stream video from a camera detail page or from camera inspection page

<br>

Actual result

Error text specifying the authentication has failed

<br>

Workaround

  • Go to web services (left menu in ESM)
  • Click on the web service from the list having this issue
  • Update the password, click apply

<br>

Version fixed

Unknown