SAP Manager crashes when attempting to retrieve the SAP system log
Article ID: 87343
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message :
In the RFC trace (level 3 enabled) file following error messages appears at incident time:
Extract from the RFC trace:
RfcGetChars(MESSAGE) buffer:
000000 | 0049006E 00740065 0072006E 0061006C |.I.n.t.e.r.n.a.l|
000010 | 00200070 0072006F 0062006C 0065006D |. .p.r.o.b.l.e.m|
000020 | 00200028 00660075 006E0063 00740069 |. .(.f.u.n.c.t.i|
000030 | 006F006E 00200042 00410050 0049005F |.o.n. .B.A.P.I._|
000040 | 00580042 0050005F 004A004F 0042005F |.X.B.P._.J.O.B._|
000050 | 00410044 0044005F 00410042 00410050 |.A.D.D._.A.B.A.P|
000060 | 005F0053 00540045 00500029 00200020 |._.S.T.E.P.). . |
Then SXMI_XMB_SYSLOG_READ crashes.
In the universe.log
ERROR|S|sap|pid=17367146.1| read_new_network_message | Network error -2: Connection closed
The dbx analysis of the core file returns similar output:
dbx) where
global_lock_ppc_mp() at 0x90000000056d024
_mutex_lock(??, ??, ??) at 0x90000000054f210
ThrMtxILock@AF43_3(??) at 0x9000000056b3d04
ThrMtxLock(??) at 0x9000000056b1a34
NISIMPL_LINEAR::getServNo(const unsigned short*,unsigned short*,unsigned int,FILE**)(??, ??, ??, ??, ??) at 0x9000000058bfdc8
NiIGetServNo(const unsigned short*,unsigned short*,unsigned int,FILE**)(??, ??, ??, ??) at 0x9000000058bcfe8
NiServToNo(??, ??) at 0x900000005886798
LgIGroupX(??, ??, ??, ??, ??, ??, ??, ??) at 0x9000000058fecb4
LgIGroup(??, ??, ??, ??, ??, ??, ??, ??) at 0x9000000058fc798
LgGroupSec(??, ??, ??, ??, ??, ??, ??, ??) at 0x90000000590fbac
CpicConnection::getASfromMS(RfcOptions&)(??, ??) at 0x9000000058223a0
CpicConnection::parseConnParameters(RfcOptions&)(??, ??) at 0x9000000058244ac
CpicConnection::connectAsClient(RfcOptions&)(??, ??) at 0x900000005825a54
RfcConnection::connect(RfcOptions&,_RFC_PROGRAM_TYPE)(??, ??, ??) at 0x900000005605534
RfcConnection::openNew(RfcOptions&,_RFC_PROGRAM_TYPE)(??, ??) at 0x900000005604d84
RfcOpenConnection(??, ??, ??) at 0x90000000557aedc
uxsap_open_comm(??, ??, ??) at 0x1002fc18c
uxsap_connect_with_error_code(??, ??, ??, ??) at 0x1002fa45c
uxsap_connect_with_retry(??, ??, ??) at 0x1002fa228
uxsap_bapi_connect(??, ??, ??) at 0x10030f924
uxsap_jobsap_create(??, ??, ??, ??, ??) at 0x1002f955c
owls_sap_job_handler.process_launch(??, ??, ??) at 0x1004efc48
owls_sap_handle_sap_job(??, ??, ??) at 0x1004f042c
uxsap_process_client_request(??, ??) at 0x1004d9f1c
uxsap_thread_trt(??) at 0x1004da740
The SAP Manager crashes randomly on an AIX server when trying to retrieve the syslog via the API SXMI_XMB_SYSLOG_READ of the SAP Netweaver RFC library.
It happens when a SAP job with incorrect parameters is submitted (non existing report, wrong user, incorrect variant name).
In the RFC trace (level 3 enabled) file following error messages appears at incident time:
Extract from the RFC trace:
RfcGetChars(MESSAGE) buffer:
000000 | 0049006E 00740065 0072006E 0061006C |.I.n.t.e.r.n.a.l|
000010 | 00200070 0072006F 0062006C 0065006D |. .p.r.o.b.l.e.m|
000020 | 00200028 00660075 006E0063 00740069 |. .(.f.u.n.c.t.i|
000030 | 006F006E 00200042 00410050 0049005F |.o.n. .B.A.P.I._|
000040 | 00580042 0050005F 004A004F 0042005F |.X.B.P._.J.O.B._|
000050 | 00410044 0044005F 00410042 00410050 |.A.D.D._.A.B.A.P|
000060 | 005F0053 00540045 00500029 00200020 |._.S.T.E.P.). . |
Then SXMI_XMB_SYSLOG_READ crashes.
In the universe.log
ERROR|S|sap|pid=17367146.1| read_new_network_message | Network error -2: Connection closed
The dbx analysis of the core file returns similar output:
dbx) where
global_lock_ppc_mp() at 0x90000000056d024
_mutex_lock(??, ??, ??) at 0x90000000054f210
ThrMtxILock@AF43_3(??) at 0x9000000056b3d04
ThrMtxLock(??) at 0x9000000056b1a34
NISIMPL_LINEAR::getServNo(const unsigned short*,unsigned short*,unsigned int,FILE**)(??, ??, ??, ??, ??) at 0x9000000058bfdc8
NiIGetServNo(const unsigned short*,unsigned short*,unsigned int,FILE**)(??, ??, ??, ??) at 0x9000000058bcfe8
NiServToNo(??, ??) at 0x900000005886798
LgIGroupX(??, ??, ??, ??, ??, ??, ??, ??) at 0x9000000058fecb4
LgIGroup(??, ??, ??, ??, ??, ??, ??, ??) at 0x9000000058fc798
LgGroupSec(??, ??, ??, ??, ??, ??, ??, ??) at 0x90000000590fbac
CpicConnection::getASfromMS(RfcOptions&)(??, ??) at 0x9000000058223a0
CpicConnection::parseConnParameters(RfcOptions&)(??, ??) at 0x9000000058244ac
CpicConnection::connectAsClient(RfcOptions&)(??, ??) at 0x900000005825a54
RfcConnection::connect(RfcOptions&,_RFC_PROGRAM_TYPE)(??, ??, ??) at 0x900000005605534
RfcConnection::openNew(RfcOptions&,_RFC_PROGRAM_TYPE)(??, ??) at 0x900000005604d84
RfcOpenConnection(??, ??, ??) at 0x90000000557aedc
uxsap_open_comm(??, ??, ??) at 0x1002fc18c
uxsap_connect_with_error_code(??, ??, ??, ??) at 0x1002fa45c
uxsap_connect_with_retry(??, ??, ??) at 0x1002fa228
uxsap_bapi_connect(??, ??, ??) at 0x10030f924
uxsap_jobsap_create(??, ??, ??, ??, ??) at 0x1002f955c
owls_sap_job_handler.process_launch(??, ??, ??) at 0x1004efc48
owls_sap_handle_sap_job(??, ??, ??) at 0x1004f042c
uxsap_process_client_request(??, ??) at 0x1004d9f1c
uxsap_thread_trt(??) at 0x1004da740
The SAP Manager crashes randomly on an AIX server when trying to retrieve the syslog via the API SXMI_XMB_SYSLOG_READ of the SAP Netweaver RFC library.
It happens when a SAP job with incorrect parameters is submitted (non existing report, wrong user, incorrect variant name).
Environment
Manager for SAP on all supported OS
Cause
The root cause has not been clearly identified as the issue cannot be reproduced at will, but is certainly linked to the call of the SXMI_XMB_SYSLOG_READ function.
For deeper analysis it is recommended to open a support call at SAP.
For deeper analysis it is recommended to open a support call at SAP.
Resolution
No workaround except avoiding executing ABAP jobs that contain invalid settings like non exist users, missing variants, wrong client, etc.
The solution is to update to Dollar Universe version 6.8.21 or greater which provides a new setting which allows to bypass the call of the SXMI_XMB_SYSLOG_READ BAPI function.
In order to do this edit the node settings of the impacted node and modify as follows:
Node Settings >> Manager for SAP Solutions >> Log SAP system errors inside the job log >> No
Fix Status: Released
Fix Version(s):
Dollar Universe version 6.8.21 -- Available
The solution is to update to Dollar Universe version 6.8.21 or greater which provides a new setting which allows to bypass the call of the SXMI_XMB_SYSLOG_READ BAPI function.
In order to do this edit the node settings of the impacted node and modify as follows:
Node Settings >> Manager for SAP Solutions >> Log SAP system errors inside the job log >> No
Fix Status: Released
Fix Version(s):
Dollar Universe version 6.8.21 -- Available
Feedback
Yes
No
Powered by
