XMA: SLSENDER fails to start after upgrading to Merged Audit 2.65

XMA: SLSENDER fails to start after upgrading to Merged Audit 2.65

There is a known issue where SLSENDER will not start after upgrading to XMA 2.65.  If the customer cannot start SLSENDER after upgrading, the post upgrade steps below can be used. If we know a customer will be upgrading to XMA 2.65, pre-upgrade steps below can be taken to prevent the issue. **Please note that the pre-upgrade steps are not guaranteed to resolve the problem and additional steps post upgrade may still need to be taken.

Summary: The new version of Merged Audit creates a new local_ipaddress column in the SYSLOGQ. If customers have unsent messages in the SYSLOGQ when upgrading, those entries receive a value of ?NULL? in the new column and SLSENDER cannot process them. As a result, SLSENDER fails to start. Post upgrade, purging the old SYSLOGQ data will resolve the issue, however, if the data must be maintained, the NULL values can manually be updated in SQLCI.

Pre-upgrade steps that can be taken to prevent the issue:
 
  1.  Stop movers individually and leave SLSENDER running. The goal is to get the number of unsent messages to 0 so there are no entries with NULL created in the new SYSLOGQ table. This may or may not be possible.

                A. XMA_MANAGER, 2. Movers, 6. Stop (repeat process for ALL movers)

                B. Check if unsent message is 0:

                                select count (*) from syslogq where alertedgmt = timestamp "1970-01-01:00:00:000000" browse access;

                                If unsent messages = 0  upgrade like normal
                               
                                If unsent messages not 0  stop SLSENDER, wait until SYSLOGQ is no longer open, shutdown pathway, upgrade but see step C before starting pathway.
                               
                C. If data can be purged. BEFORE starting pathway cleanup the SYSLOGQ from XMA_MANAGER.
                               
                   If data cannot be purged, BEFORE starting the pathway modify the value of NULL in SQLCI using below:
                               
                                UPDATE SYSLOGQ SET LOCAL_IPADDRESS="" WHERE LOCAL_IPADDRESS IS NULL and alertedgmt = timestamp "1970-01-01:00:00:00.0000";


Post upgrade:
 
  1. BEFORE starting the pathway you will need to confirm if there are records with NULL value in local_ipaddress column. If there are records, they need to be changed via SQLCI or purged.

                A. Confirm records with NULL value:
                                SQLCI; select count (*) from syslogq where local_ipaddress is null and alertedgmt = timestamp "1970-01-01:00:00:000000" browse access;
                               
                B. If count > 0 the records in the SYSLOGQ need to be updated OR purged via XMA_MANAGER.
               
                C. If the records cannot be purged, use the following command to change value in SQLCI:
               
                                UPDATE SYSLOGQ SET LOCAL_IPADDRESS="" WHERE LOCAL_IPADDRESS IS NULL and alertedgmt = timestamp "1970-01-01:00:00:00.0000";

    • Related Articles

    • XMA: MADELDB Fails due to ERROR 73

      UPGRADE to XYGATE Merged Audit (XMA) 2.60 or higher A change in XMA 2.60 addresses an issue with a SLSENDER performance problem caused by the structure of SYSLOGQ table index. The XMA install and upgrade macros were modified to create or upgrade the ...

    • XMA: Cannot Start $XMA Pathway - Startup attempt fails with no errors

      Check the HOMETERM value in the MACONF file. The MACONF file is found in the XYGATEMA installation subvolume. The HOMETERM value must be a valid / existing home terminal process name. Sample MACONF file: PATHMON_NAME $XMA PRIORITY 030 PERUSE_OBJECT ...

    • XMA: SLSENDER - Steps to follow for SLSENDER When Upgrading to XMA 2.65

      The upgrade to XMA 2.65 makes changes to the SYSLOGQ table. Consequentially, this could cause fatal errors for SLSENDER when it it initially started following the upgrade. This is due to outstanding TMF transactions that remains until they are ...

    • XMA: Procedure to stop XYGATE Merged Audit when changing system time

      The correct procedure is to stop all pathway serverclasses, including XMA movers and admin servers (HKEEPER, SLSENDER, etc.) using XMA_MANAGER. >run xma install >xma_manager XYGATEMA Management Main Menu v2.60 * * * * * * * * * * * * * * * * * * * 1: ...

    • XMA: Steps to edit the Merged Audit FILTERS file using XMA_EDIT_FILTERS

      The XMA_EDIT_FILTERS Macro makes a copy of the FILTERS file called NEWFILT and allows you to edit this. Once editing is complete you can choose to install the edited version. This renames the current FILTERS file to OLDFLTXX, and replace it with ...