The udm_manager process is going down daily and turns red

book

Article ID: 8163

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES CA Unified Infrastructure Management for z Systems CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

The udm_manager process is stopping daily and does not always start.

The following errors are shown in udm_manager.log:

Sep 02 02:22:32:680 ERROR [main, udm_manager] Transaction failed. Retrying: clojure.lang.ExceptionInfo: :db.error/transactor-unavailable Transactor not available {:db/error :db.error/transactor-unavailable} 

Sep 02 02:22:34:680 FATAL [main, udm_manager] Max retries reached during UDM schema transaction. 

Sep 02 02:22:34:680 DEBUG [main, udm_manager] Shutting down the peer. 

Sep 02 02:22:34:684 FATAL [main, udm_manager] Error initializing probe: (1) error, Max retries reached during UDM schema transaction.

Cause

The udm_manager probe will try 10 times to connect to datomic.  In a busy environment, that may not be enough. After some time, the probe goes red.

Environment

UIM - 8.51 or later
Hub - 7.92HF6 or later
Robot - 7.92HF3 or later
udm_manager - 8.51 or later

Resolution

In the " Raw Configure" GUI of the udm_manager, add the following key under the setup section:

"schema_transact_retries" and set the value to 5000.

Also increase the "schema_connection_timeout_minutes" value to 30. 

You may need to edit this parameter under "setup" > datomic > "memory_index_max". 

Out of the box this is set to 256 MB.  You may need to increase this to '512m' or higher.

Additional Information

https://community.broadcom.com/communities/community-home/librarydocuments/viewdocument?DocumentKey=f528aed3-2487-4655-afb2-daaed646be9d