XMA: Error 72 - Mover Deadlock Condition

XMA: Error 72 - Mover Deadlock Condition


To reduce the transaction size in the SLSENDER, follow these steps below:
  1. Volume to the XMA Installation Subvolume (ie. VOLUME $<VOL>.XYGATEMA)
  2. Run XMA INSTALLATION to attach the XYGATEMA segment
  3. Type: XMA_MANAGER to manage the pathway
  4. Select 2:  MOVERS (determines audit file target of a mover)
  5. Select 18: CONFIGURE SYSLOG SEND SERVER This will read records from an input queue and transmit the records to an off-box IP address and port via TCP/IP
  6. Select 7:  MAX NUMBER OF OPEN TRANSACTIONS (default is 100 transactions)
  7. Select 8:  MAX NUMBER OF PENDING IO CALLS (default is 10 IOs)  (Lower that setting to 10 for each different SIEM. Most installations only send to one SIEM.  The setting would be 10.)
  8. Select R:  RUN
  9. Repeat Step 5 to confirm the changes were implemented.
If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.

    • Related Articles

    • XMA: Can't start iTP Webserver Mover - SQL Error

      Probable cause is that the iTP webserver mover is attempting to process a file type that is not yet supported. Several file formats are not currently supported by the iTP mover: HTTPD log support. The format is not CLF format but a hybrid of access ...

    • XMA: The SQLXPress mover fails with error 48 (security Violation).

      Start SQLEXpress with the same user id that started XMA, or re-secure the object shown in the error message for access by the user id that started XMA. If this article did not provide a solution, please open a case with our support team by sending an ...

    • XMA: Saveabend files are not being created by mover abends

      1. Does the security of the XYGATEMA (XMA) installation disk volume or subvolume allow CREATE access to the XMA installation owner? Check for any Safeguard volume or subvolume ACLs or XYGATEOS rules that prevent WRITE or CREATE access for the XMA ...

    • XMA: Measure Mover Keeps Abending

      Is XYPRO SecurityOne installed? The Measure mover is not designed to collect system performance metrics. It is designed to only capture process information for the XYGATE SecurityOne WHO Resolver. The MEASURE mover collects information regarding ...

    • XMA: Mover cannot be started - no saveabends and no EMS errors

      Check to make sure that the name of the object program for the XMA pathmon process, (e.g. $XMA) is PATHMON,usually $SYSTEM.SYSTEM.PATHMON. This is because XMA relies on the program name to identify a process a being a pathway process. Any XMA ...