Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Root administrators in ESM using self update undo does not always work correctly

Description

If scheduling an ESM update that is not the recommended version; if you delete the update, undo it, the scheduled update will be the recommended version which is not what was intended.

User should delete the update and instead of hitting undo, go do another scheduled update.

<br>

Tested Version

exacqVision ESM 4.1

<br>

Platform

All

<br>

Steps to reproduce

  1. Schedule an ESM self update for May, 2020
  2. Unschedule it
  3. Schedule another ESM self update for May 2019
  4. Unschedule it
  5. Click Undo on the green banner

<br>

Expected result

Update for May 2019 is rescheduled

<br>

Actual result

Update for May 2020 is rescheduled

<br>

Work Around

Do not undo a deleted update. Instead, schedule a new one with a correct date.

<br>

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

No license server in ESM will show bad SSA date

Description

ESM will show a date Dec. 31 1969 for a server with no license file. It should show None for the SSA.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

High CPU utilization for large ESM deploys on server 2008 in windows

Description

On a customer site, we have seen high CPU utilization in the 85% or more range with multiple cores (more than 20 cores). ESM will spin up a sub importer per core, so there could be 20+ sub importers in this scenario. Each using CPU, the total can be very high. On newer windows operating systems, this seems to balance correctly and not using high CPU.

If a customer is seeing this, you can configure the ESM importer to spin up a lower number of sub importers. By setting the _ESM_NUM_IMPORTERS=X where X is the number you want to use, in system environment variables, you can limit the number it spins up. Thus reducing the CPU load.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Fallback daylight savings event may have incorrect time in ESM

Description

During the 1 hour time of falling back for daylight savings, if an event is created in this time frame it can cause the importer to not record a correct time zone time.

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

ESM spare server can’t be removed from failover group unless designation as spare is removed

Description

ESM spare failover server can not be removed from failover group on server edit form, unless the “Spare” designation is removed first.

<br>

Version Introduced

v3.0.2.72327

<br>

Platform

ALL

<br>

Steps to reproduce

Create ESM failover group

Add server to group as spare server. CAUTION: This will change server configuation.

On the server detail page. Click edit server icon to go to server edit form.

Attempt to remove spare from failover group by Clicking failover group dropdown

<br>

Expected result

Failover Group dropdown should have “No Failover Group” option.

<br>

Actual result

Failover Group dropdown does not have “No Failover Group” option.

<br>

Work Around

Click “Designate As Spare” dropdown and select “No”.

Click “Failover Group” dropdown, and “No Failover Group” option will be available.

<br>

Version Fixed

none

<br>

Keywords

ESM, failover

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

ESM page does not load and displays an error

Affected platforms

All versions of of ESM

<br>

Symptom

If a page takes a long time to load (> 30 seconds) and an error is displayed that says: “We’re sorry. Something went wrong. Please try again or contact the System Administrator.” this indicates that the page is timing out.

This is usually due to a large number events in the database relative to the capabilities of the ESM machine.

<br>

Workaround

To increase the timeout update the following Apache configuration:
On Windows:
1) Open the file C:\exacqVisionEsm\apache_solr\apache2\conf\httpd.conf as admin
2) Find the the line that says “FastCGIExternalServer htdocs/mysite.fcgi -host 127.0.0.1:8113”
3) Change it to: “FastCGIExternalServer htdocs/mysite.fcgi -host 127.0.0.1:8113 -idle-timeout 600”
4) Open Services and restart the solrApache, solrJetty and ESMWebservice services

On Linux:
1) Open the file /usr/local/exacq/esm/apache_solr/apache2/conf/httpd.conf as admin
2) Find the the line that says “FastCGIExternalServer htdocs/mysite.fcgi -host 127.0.0.1:8113”
3) Change it to: “FastCGIExternalServer htdocs/mysite.fcgi -host 127.0.0.1:8113 -idle-timeout 600”
4) Run the command: service ESMWebservice restart

<br>

Resolution

None at this time: The timeout will be extended from a default of 30 seconds to a larger value in a future version of ESM.

<br>

Keywords

esm, timeout, apache

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

Bulk delete server actions on ESM on MySQL database fails

Description

Attempting to bulk delete server actions on ESM on MySQL database fails

<br>

Version Introduced

not provided

<br>

Platform

All

<br>

Steps to reproduce

Attempt to bulk delete server actions on ESM on MySQL database

<br>

Expected result

Server actions are successfully deleted

<br>

Actual result

Error page is returned and server actions are not deleted

<br>

Work Around

Deleted server actions individually

<br>

Version Fixed

none

<br>

Keywords

ESM MySql

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