Tag: 3.2

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM 3.2 “Importer Processes Died” Warning

While running ESM 3.2 with exacqVision 6.8 servers connected, ESM importer log files could contain warnings stating that “Importer processes died.” If this occurs, upgrade to the following version (or later):


https://exacq.com/evESM/exacqVisionEnterpriseSystemManager-3.2.4.77534.exe

https://exacq.com/evESM/exacqVisionEnterpriseSystemManager-3.2.4.77534.deb

<br>

ESM-3.2-Importer-Processes-Died-Warning.pdf

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM 3.2 Creates Duplicate Events Every Hour

While running ESM 3.2 with exacqVision 6.8 servers connected, duplicate events could be created every hour. If this occurs, upgrade to the following version (or later):

https://crm.exacq.com/release/Vision%20EnterpriseSystemManager/3.3.x/exacqVisionEnterpriseSystemManagerDev-3_3_10_77655.exe

https://crm.exacq.com/release/Vision%20EnterpriseSystemManager/3.3.x/exacqVisionEnterpriseSystemManagerDev-3_3_10_77655.deb

<br>

ESM-3.2-Creates-Duplicate-Events-Every-Hour.pdf

Categories
Knowledge Support Support exacqVision Server Categories Products

Increasing the Number of Connections Allowed in ESM

If an Enterprise System Manager (EM) installation is using the Postgres database with 500 or more servers, you could see the following error in the log file: “OperationalError: FATAL: sorry, too many clients already.”

To increase the number of connections allowed, complete the following steps:

<br>

  1. Stop all ESM services (ExacqVision Enterprise Manager Importer, ExacqVision Enterprise Manager Datarolloff, ExacqVision Enterprise Manager Sendemail, and ExacqVision Enterprise Manager WebService).
  2. Open the Postgre configuration file:

    Linux:     /usr/local/exacq/esm/PostgreSQL/9.2/data/postgresql.conf
    Windows    : C:\Program Files\exacqVision\EnterpriseManager\PostgreSQL\10.17\data\ postgresql.conf
  3. Find the line that contains “max_connections,” change the value to 500, and save the file.

    NOTE:     Each additional connection greater than 100 uses 400 bytes of memory.
  4. Restart the Postgres service.
  5. Restart the ESM services.

<br>

Increasing-the-Number-of-Connections-Allowed-in-ESM.pdf