Tag: Enterprise System Manager

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

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

ESM adds server to root group if user has only one group visible

Description

If a user has only one group visible to them, an attempt to add a server to the group will inadvertently add the server to the root group. And hence be invisible to a user if they are not root user.

<br>

Tested version

5.1.9.115770

<br>

Platform

All

<br>

Steps to reproduce

  1. Add a sub group to root group (testGroup)
  2. Add a user to that group (testUser)
  3. Log out of ESM, and sign in as testUser
  4. Attempt to add a server to your group (testGroup)

<br>

Expected result

Server should be added and displayed on server list page

<br>

Actual result

Server is added but will not be displayed on testUser’s server list page.

This server will be displayed on the root group’s server list page.

<br>

Workaround

Only Add a server through ESM UI if you have multiple groups visible to you.

You can also add a server through the ESM API no matter how many groups you have visible to you.

<br>

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Enterprise user names length check on long names fails

Description

Even though the default max user name length on Django base classes is set to 30, ESM code attempts to override it with a max length of 255. However, while actually trying to create user names longer than 30, ESM fails with the database save length check error. For example, this error can be recreated when attempting to login with a LDAP, with ESM trying to create long user name ‘abcdefghijklmno@cfsad.com (domain)’ in the database

<br>

Tested version

4.9.23

<br>

Platform

All

<br>

Steps to reproduce

Attempt to login into ESM from the client’s ‘Synchronize with ESM’ page using a LDAP name that is longer than 25 (will be > 30 by the time ESM appends ‘(domain)’ to the user name).

<br>

Expected result

User login succeeds

<br>

Actual result

User login fails with a client pop up “Please check your URL”.

<br>

Workaround

None

<br>

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Filtering Dialog Errors

Description

If an error occurs on the filtering dialog, the dialog still closes and user is unaware of the error

<br>

Tested version

4.9.22

<br>

Platforms

All

<br>

Steps to reproduce

  1. Navigate to server list view
  2. Open filtering dialog
  3. For SSA Date, enter older than 200 months
  4. Click Apply

<br>

Expected result

Dialog remains open and displays the error

<br>

Actual result

Dialog closes and user is unaware that there is an error

<br>

Work around

Open the dialog again to view the error

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM server edit form displays “DDNS request error 428: No changes to be made”

Description

When enabling dynamic dns without supplying a hostname on server edit form, “DDNS request error 428: No changes to be made” will be displayed below the hostname field.
This will only happen on outbound server connections, if the server already has an address and mac.

<br>

Version introduced

4.7.12.109795

<br>

Platforms

All Platforms

<br>

Steps to reproduce

  • Add outbound server to ESM
  • Edit server enabling dynamic DNS without providing a hostname (this will attempt to create an A name on exacqio)

<br>

Expected result

  • If the server has a mac and IP addresses, hostname should be requested from exacqio (defaulting to e + Mac), and server edit form apply should succeed.
  • I server doesn’t have a mac and IP addresses, server dynamic DNS should show to be enabled, but hostname will be requested when server connects.

<br>

Actual result

  • If server has mac and ip address DDNS request error 428: No changes to be made is displayed and server edit form submit fails
    • NOTE: if hostname is provided, this error will not be displayed. but the requested hostname will not work, at least until the server connection is reset.
  • If server does not have mac and IP address, there is no attempt to request for a hostname from exacqio, hence no error

<br>

Work around

There is no feasible workaround for exacq cloud. Otherwise enable dynamic DNS when adding a server

<br>

Version fixed

4.7.13.110078

<br>