Categories
exacqVision Enterprise Categories Products

ESM: Spare With Expired or Non-Enterprise License Not Monitored

A server without an Enterprise license enabled for health monitoring can be selected as a spare server. The protected server will fail over to this spare server, but Enterprise System Manager (ESM) will not monitor the spare server. This can also occur if the spare server’s Enterprise license has expired.

<br>

As a workaround, do not designate a spare that does not have a license that allows it to be monitored by ESM.

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

How to reset the ESM admin password

Description

If the ESM administrator has lost or forgotten the ESM admin password, it can be reset by executing shell commands in the operating system of the ESM machine.

Note: root/admin level access to the ESM machine is required for this process.

In Linux:

  1. Open bash shell as root, or provide sudo on command execution
  2. Navigate to the install folder, /usr/local/exacq/esm/
  3. Execute as root, ./enterprisesystemmanager shell
  4. Type the following commands, hit enter after each line.
    from organization.models import EnterpriseUser
    u = EnterpriseUser.objects.filter(username=’admin’).get()
    u.set_password(‘password_goes_here’)
    u.save()
    import sys
    sys.exit()

<br>

In Windows:

  1. Open Command Prompt as administrator
  2. Navigate to the install folder, C:\exacqVisionESM\EnterpriseSystemManager\
  3. Execute, enterprisesystemmanager.exe shell
  4. Type the following commands, hit enter after each line.
    from organization.models import EnterpriseUser
    u = EnterpriseUser.objects.filter(username=’admin’).get()
    u.set_password(‘password_goes_here’)
    u.save()
    import sys
    sys.exit()
Categories
Knowledge Support exacqVision Enterprise Support Categories Products

Disabling or enabling of a camera will cause ESM importer to crash

Affected platforms

ESM version 3.6.1, trunk builds 3.7.3 through 3.7.5

<br>

Symptom

When a camera is enabled or disabled in the exacqVision client, ESM backend will crash. In the UI in the upper right corner, you will notice servers dropping and reconnecting. Inspection of importer log will show the crash.

<br>

Workaround

Do not disable/enable cameras

<br>

Resolution

Update ESM to version 3.6.2 or later (excluding the 3.7.3 – 3.7.5 trunk builds)

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Archiving cannot recover from disconnected state

Affected platforms

exacqVision 7.0 to 7.2 running on Windows

<br>

Symptom

When the archiving job becomes disconnected, it may not automatically recover and remain in a disconnected state.

<br>

Workaround

Perform one of the following actions:
Recreate the archive target

  1. Delete all task schedules for the archive target.
  2. Delete the archive target.
  3. Recreate the archive target.
  4. Recreate the task schedules associated to the archive target.

Restart exacqVision Server service. This will result in a minor interruption of video recording during the restart process.

<br>

Resolution

Update to exacqVision 7.3.3 or later

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM returns error when entering a rule duration using a decimal

Affected platforms

ESM 3.2 or later

<br>

Symptom

If the user enters a value using a decimal (for example, 10.5) for the duration value of a rule, ESM returns an error page when the user attempts to create the rule.

<br>

Workaround

Enter a valid integer (not a decimal number) between 1 second and the number of seconds in a year, which is about 31536000 seconds.

<br>

Resolution

No resolution at this time.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM returns error when converting 31+ character Unmanaged server user to Managed

Affected platforms

ESM 3.0 or later

<br>

Symptom

An attempt to convert an unmanaged server user to a managed server user that contains more than 30 characters in the username will return a red banner displaying the following error: “Value too long for type character varying(30).”

Also note that any usernames greater than 36 characters are truncated to display only 36 characters in ESM.

<br>

Workaround

Create or modify server users on the installed client to use 30 characters or less.

<br>

Resolution

No resolution at this time.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM fails to completely uninstall

Affected platforms

All versions of ESM

<br>

Symptom

It is possible that the ESM uninstall will not correctly stop datarolloff and delete the ESM install folder even though it reports success.
To confirm if this has occurred, after successful uninstall check to see if the install folder is still present and check running processes for datarolloff.exe

<br>

Workaround

The user should manually kill the datarolloff process and then remove the ESM install folder to complete the uninstall.

<br>

Resolution

None at this time

Categories
Knowledge Support Support exacqVision Enterprise 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