SLSENDER getting error 1120. CPU spikes are also noticed

SLSENDER getting error 1120. CPU spikes are also noticed

A couple of things may help this issue:

1. Update statistics
   
     a. Logon as the XMA owner
     b. Attach to the XMA segment file
   
          RUN $<vol>.XYGATEMA.XMA INSTALL   (where $<vol> is the disk where XMA is installed)
           
     d. XMA_MANAGER
     d. Option 3, Database
     e. Option 1, Update Statistics

2.  Run SQLCOMP for SLSENDER

     a. Volume to the  XMA installation subvolume:

         VOLUME $<vol>.XYGATEMA   ($<vol> is the disk volume where XMA is installed)
     
     b.  Load the defines for the database tables.  From a TACL:

          XMA_LOAD_DEFINES

     c. Run SQLCOMP for SLSENDER

          RUN $SYSTEM.SYSTEM.SQLCOMP/IN SLSENDER, OUT $S.#SQLCOMP/CATALOG =XMA_CAT

3.  Increase the Auto Transaction Timeout from 300 to 600.  From the XMA_MANAGER main menu:

      a. Option 2, Movers
      b. Option 18, Configure SysLog Sender
      c.  Option 1, Auto Transaction Timeout.  Change this value from 300 to 600

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: SLSENDER Error unable to send messages to host.

      The SYSLOGQ database table in the XMADAT subvolume has 2 columns that can be used to determine if messages are being sent to the SIEM. ENTRYGMT is the timestamp when the message was inserted into the queue by a mover. ALERTEDGMT is the timestamp when ...

    • 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 ...

    • XS1: Error creating Keystore Password

      The error in question appears when opening the XS1 Installation file located at: xs1\libraries\scripts\run.installer.bat An example of the error is below: Upon getting this error choose Option 3: Configure XTR Connection The errors below should ...

    • XMA: SLSENDER is busy

      Use the XMA_SQLCOMPALL macro to generate a new optimized query plan, which will then be used when compiling the objects. TACL> VOLUME $SYSTEM.XYGATEMA TACL> RUN XMA INSTALL TACL> XMA_PWSTOP TACL> XMA_SQLCOMPALL TACL> XMA_PWCOOL The XMA_SQLCOMPALL ...

    • XMA: How to uninstall SLSENDER.

      As the SLSENDER is configured and added to the XMA pathway when the customer follows the installation process in the XMA manual. The following procedure can be used to manually stop the SLSENDER , remove any records that have been generated, and stop ...