cancel
Showing results for 
Search instead for 
Did you mean: 

mds-r stops after sometime.

Former Member
0 Kudos

Hi Team,

I have restarted MDM 7.1 SP10, where I see the processes mds-r / mdss-r & mdis -r are running.

But after sometime mds-r stops. Any idea on what could be the problem.

Best Regards,

Avinash

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I found this information from the INSTSTAT file.

START_TIME 2013/11/22 06:58:07

START_PROF /usr/sap/<SID>/SYS/profile/<SID>_MDS10_<hostname>

SYSTEMNAME <SID>

INST_NAME  MDS10

CMD_LINE   pf=/usr/sap/<SID>/SYS/profile/<SID>_MDS10_<hostname>

SHUTDWN_BY NO_MORE_CHILD_PROCESSES

SHUTDWN_AT 2013/11/22 07:08:33

EXIT_TIME  2013/11/22 07:08:35

EXIT_WITH  3 No more child processes

The mds-r process is getting killed within minutes after restart.

Let me know if you have any idea on this.

Regards,

Avinash

gabor_molnar
Advisor
Advisor
0 Kudos

Hi Avinash,

Please make sure that all your MDM Servers are on 7.1 SP10 Patch07 or higher. There is a fix similar to your issue in that build as per the Note 1883681.

Best regards,

Gábor

Former Member
0 Kudos

Hi Gabor,

I have applied SP10 PL 9 & PL 16 below are the details. How can I rectify this issue?

Software Component Version Instantiation Activated Instance File File Description


MDM INSTALLATION MASTER 7.1 HP-UX on IA64 64bit Import Server, Master Data Server, Syndication Server, Layout Server MDMIM71010_9-20004523.TAR MDM 7.1 SP10 Patch9 - Installation Master


MDM SHARED INSTALL CONTENT 7.1 HP-UX on IA64 64bit Import Server, Master Data Server, Syndication Server, Layout Server MDMSIC71010_16-20005054.TAR MDM 7.1 SP10 Patch16 - Shared Installation Content

Regards,

Avinash

Former Member
0 Kudos

Hi Gabor,

These are the details of the MDS.

# System ID

SID = <SID>

# MDM Version e.g 710

Version = 7.1

# Support package Name as in PPMS e.g SP005, SP006, SP007

MDS_SP_NAME = SP010

# hostname where MDS is running

MDS_ComputerName = <hostname>

# instance number of MDS e.g.: 01

MDS_InstanceNumber = 10

# InstallationPath of the system e.g. C:\usr\sap\<SID>

InstallationPath = /usr/sap/<SID>/MDS10/exe

# InstallationPath of the instance e.g. C:\usr\sap\<SID>\MDS<instno>

MDS_RootDirectory = /usr/sap/<SID>/MDS10

# MDM Server build e.g. 7.1.04.137

Build = 7.1.10.248

# Support package Version e.g. 005, 006, 007

MDS_SP_Version = 010

# The Secure TCP/IP port number of the respective MDM Server

MDS_SecPort = 59951

Former Member
0 Kudos

Hi Avinash,

When mds-r stops are there any error messages in the MDS log? is there a core dump? can you provide the core stack trace?

Thanks,

Tal.

Former Member
0 Kudos

Hi Tai,

I'm not familiar with core dump. can u tell me the steps to extract the stack trace from the core file.

Thanks & Regards,

Avinash

Former Member
0 Kudos

Here is the core dump details:

sidadm> /opt/langtools/bin/gdb /usr/sap/<SID>/MDS10/exe/mds-r /usr/sap/<SID>/MDS10/work/core
HP gdb 6.1 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2009 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.1 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Core was generated by `mds-r'.
Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
#0  0xc0000000002125f0:0 in _lwp_kill+0x30 ()
   from /usr/lib/hpux64/libpthread.so.1

(gdb) bt
#0  0xc0000000002125f0:0 in _lwp_kill+0x30 ()
   from /usr/lib/hpux64/libpthread.so.1
#1  0xc000000000178b70:0 in pthread_kill+0x9d0 ()
   from /usr/lib/hpux64/libpthread.so.1
warning: No unwind information found.
Skipping this library /usr/sap/<SID>/MDS10/exe/libicudata.sl.38.

warning: No unwind information found.
Skipping this library /usr/sap/<SID>/MDS10/exe/libbosap_icudata4.2.0.0_64.so.42.

#2  0xc0000000003f9840:0 in raise+0xe0 () from /usr/lib/hpux64/libc.so.1
#3  0xc000000032e5f760:0 in skgesigOSCrash () at skgesig.c:376
#4  0xc0000000335d8160:0 in kpeDbgSignalHandler () at kpedbg.c:1074
#5  0xc000000032e5fc00:0 in skgesig_sigactionHandler () at skgesig.c:799
#6  <signal handler called>
#7  0xc0000000ba3a0b10:0 in _STL::ios_base::~ios_base ()
    at stlport_io/ios.cpp:190
#8  0xc0000000ba48d280:0 in _STL::basic_ostream<unsigned short,_STL::char_traits<unsigned short> >::~basic_ostream ()
    at /sapmnt/depot/tools/src/OpenSource/STLport/4.5.0/stlport/stl/_ios.h:58
#9  0xc0000000ba48d370:0 in _STL::basic_ostream<unsigned short,_STL::char_traits<unsigned short> >::~basic_ostream ()
    at /sapmnt/depot/tools/src/OpenSource/STLport/4.5.0/stlport/stl/_ostream.c:58
#10 0xc0000000ba671570:0 in RfcTrace::getTrace () at nrfctrace.cpp:190
#11 0xc0000000ba497170:0 in RfcRegisterServer () at nrfc.cpp:663
#12 0x400000000a8aed30:0 in Call_ListenOnRfcHandles ()
    at /home/mdmbuild/mdm.build/7.1.10.xx_REL/Cpp/MDM/Servers/MDS/RfcConnector/RfcConnection.cpp:517
#13 0x400000000a8bd8d0:0 in A2i::ThreadedOperationExplicitDataTypePtr<RfcConnection::t_connectionHandle>::ExecuteFunction ()
    at /home/mdmbuild/mdm.build/7.1.10.xx_REL/Cpp/GenericLibs/Base/ThreadedOperationExplicitDataType.h:98
#14 0x40000000029b58f0:0 in A2i::PooledThread::PooledThreadFunction ()
    at /home/mdmbuild/mdm.build/7.1.10.xx_REL/Cpp/GenericLibs/Base/PooledThread.cpp:165
#15 0x40000000029b5340:0 in A2i::PooledThread::PooledThreadFunctionHelper ()
    at /home/mdmbuild/mdm.build/7.1.10.xx_REL/Cpp/GenericLibs/Base/PooledThread.cpp:62
#16 0xc00000000013fe80:0 in __pthread_bound_body+0x190 ()
   from /usr/lib/hpux64/libpthread.so.1

Former Member
0 Kudos

Hi,

The stack trace points to NW RFC SDK, could you please let me know which NW RFC SDK are you using? you could see that in you MDM Server log file after an MDM restart you will see a printed log with the NW RDC SDK ?

Do you have RFC Tracing enabled for the NW RFC SDK Library you could see it in your mds.ini RFC Gateways entry. (you could find the SDK version in the rfc*.trc file in case its enabled.

Regards,

Isaeed Mohanna

Former Member
0 Kudos

Hi Isaeed,

Yes the issue drilled down on the RFC Gateway entry in the mds.ini. I commented the below entries in mds.ini

SAP RFC Gateways=

Trusted SAP Systems=

& restarted MDS. It did not crash after this change. But these entries are required for the ABAP gateway.

During investigation we kept only the entry for the hostname1 on which the MDM is running & removed other remote system (hostname2). MDS is working with this setup too.

SAP RFC Gateways=GWHOST=<hostname1>
GWSERV=3300 TRACE=1 ; GWHOST=<hostname2> GWSERV=3300 TRACE=1

Trusted SAP Systems=<hostname1SID> ; <hostname2SID>

As part of the setup I need to keep the hostname2 in the RFC gateway...but challenge is this system is on NW 7.4 & I'm not sure if the MDM_TECH Component for ABAP API is compatible with NW 7.4. The Add-on that we have on SAP Market Place is for NW 7.31

Please let me know if this is compatible. I already have MDM_TECH 710 700 for SP10 already installed on this system NW 7.4 but for some reason it is not compatible.

Thanks & Regards,

Avinash

Former Member
0 Kudos

Hi

MDM_TECH is compaitable with NW 7.4, however I am not sure if is the same package that you are using or you need to download a new package,  check in the Software Market Place or open an SAP Support ticket on Add-On deployment component.

The entries you mention tell MDM server which ABAP systems it should connect to, there is no need to maintain the MDM server itself there but only hosts of ABAP system that need to communicate with MDM.

I have seen a problem in the past where tracing caused the RFC SDK to crash, remove the TRACE=1 from your configurations in mds.ini, restart your server and see if it work correctly.

Regards,

Isaeed Mohanna

Former Member
0 Kudos

Hi Isaeed,

I have the latest version MDM_TECH 710 731 from SP10.I'm not sure if this will be compatible with NW 7.4.

I will check with SAP.

On the issue with the RFC, it is resolved as the RFC was failing to register a external program from another host.

When I checked the SECINFO & REGINFO files on this gateway they had below entries which means no external program from any outside host can register the program. I made the change as below & reloaded the secinfo & reginfo files on the gateway. The connection started working & MDS is also running fine now.

secinfo entry
P TP=* USER=* USER-HOST=local HOST=local
P TP=* USER=* USER-HOST=internal HOST=internal

Changed to : P TP=* USER=* USER-HOST=* HOST=*


reginfo entry

P TP=* HOST=local
P TP=* HOST=internal

Changed to: P TP=*

Thanks a lot for all the valuable information you all provide.

Best Regards,

Avinash

Former Member
0 Kudos

Hi

Glad to see you worked things out.

Kind Regards,

Isaeed Mohanna

Answers (0)