Dispatcher Yellow SMDAgent Disconnected Solman

[former_member217353]

Dear Experts,

My SOLUTION MANAGER system was working fine but after a restart DISPATCHER remaining Yellow and SMDAgent is in DISCONNECTED state:

1. Entries in HOST file are right 

2. Network and Database working fine.

3. I don't have the parameter PHYS_MEMSIZE in my instance profile

4. J2ee_admin, SMDAgent UNLOCKED

What might be the problem guys.

Regards,

Domnic.

[divyanshu_srivastava3]

You have tried with a server reboot option ?

Please share dev_w0 and share/ook into SMD agent logs, there might be some network conflict causing this.

[former_member217353]

Dear Srivastava,

Yes i restarted it two/Three times, Kindly check the attached dev_wo LOG.

Regards,

Domnic.

dev_wo.txt.zip

[former_member217353]

Dear Behlau,

Yes we are on VM, Please find the attached LOG for Dispatcher and SMD error.

There was an error with network but that is fixed and i restarted system after that  Network Error.

Dear Freitas,

You can check the attached screens for DISPATCHER and SMDAGENT status.

Regards,

Domnic.

dev_smdagent.txt.zip

dev_disp.txt.zip

[behlau_carlos]

Hello Domnic,

what I can see from the log:

***LOG Q0I=> NiIRead: P=127.0.0.1:64886; L=127.0.0.1:3200: recv (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 5082]

*** ERROR => NiIRead: SiRecv failed for hdl 33/sock 1416

    (SI_ECONN_BROKEN/10053; I4; ST; P=127.0.0.1:64886; L=127.0.0.1:3200) [nixxi.cpp    5082]

If network is running again from technical side (ping to loop back adapter 127.0.0.1) is working, I would try to cross check, if port query is working.

In case your system is running on Microsoft OS, you can check with the port query tool of Microsoft:

https://www.microsoft.com/en-us/download/details.aspx?id=24009

if you can reach the port 3200.

Command would be: portqry -n 127.0.0.1 -e 3200

If you are getting a LISTING back, you could state, "...yes we can reach the port ...".

If not, it might be the case, for example Microsoft Firewall or a other security product is blocking the port.

For WSAECONNABORTED failure you can also cross check SAP Note 1139285

Best regards

Carlos Behlau

[former_member217353]

Dear Behlau,

Portquery is here :

Starting portqry.exe -n 127.0.0.1 -e 3200 -p TCP ...

Querying target system called:

127.0.0.1

Attempting to resolve IP address to a name...

IP address resolved to *******SOL

querying...

TCP port 3200 (sapdp00 service): LISTENING

portqry.exe -n 127.0.0.1 -e 3200 -p TCP exits with return code 0x00000000.

TCP port 3200 (sapdp00 service): LISTENING

UDP port 3200 (unknown service): LISTENING or FILTERED

portqry.exe -n 127.0.0.1 -e 3200 -p BOTH exits with return code 0x00000002.

Message was edited by: domnic domnic

[behlau_carlos]

Hello Domnic,

that looks OK.

Can you cross check your %WINDIR%\system32\drivers\etc\services files and make sure, the listed ports are only there once.

Example:

sapdp00     3200/tcp

should be only once in the file.

Also cross check SAP Note 1139285 and check if the effected kernel components are higher.

It might be also a kernel bug, that as been fixed in a higher kernel stack.

Best regards

Carlos Behlau

[isaias_freitas]

The ABAP-stack is running fine.

The issue is with the Java-stack...

Check the "Java processes" at the SAP MMC.

[isaias_freitas]

Can you attach a screenshot showing the SAP MMC?

Or what is the text for the Dispatcher component, "status" column?

Regards,

Isaías

[former_member217353]

Dev_Disp log :

---------------------------------------------------

trc file: "dev_disp", trc level: 1, release: "721"

---------------------------------------------------

sysno      00

sid        SOL

systemid   562 (PC with Windows NT)

relno      7210

patchlevel 0

patchno    300

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\MOBEERPSOL\sapmnt\SOL\SYS\profile\SOL_DVEBMGS00_MOBEERPSOL

pid        8480

kernel runs with dp version 139000(ext=121000) (@(#) DPLIB-INT-VERSION-139000-UC)

length of sys_adm_ext is 592 bytes

*** SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 8480) [dpxxdisp.c   1321]

  shared lib "dw_xml.dll" version 300 successfully loaded

  shared lib "dw_xtc.dll" version 300 successfully loaded

  shared lib "dw_stl.dll" version 300 successfully loaded

  shared lib "dw_gui.dll" version 300 successfully loaded

  shared lib "dw_mdm.dll" version 300 successfully loaded

  shared lib "dw_rndrt.dll" version 300 successfully loaded

  shared lib "dw_abp.dll" version 300 successfully loaded

  shared lib "dw_sym.dll" version 300 successfully loaded

  shared lib "dw_aci.dll" version 300 successfully loaded

rdisp/softcancel_sequence :  -> 0,5,-1

use internal message server connection to port 3900

rdisp/dynamic_wp_check : 1

rdisp/calculateLoadAverage : 1

Mon Jun 15 17:05:39 2015

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6485]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

display_tcp_ip: 0

DpIPCInit2: write dp-profile-values into sys_adm_ext

DpIPCInit2: start server >MOBEERPSOL_SOL_00                       <

DpShMCreate: sizeof(wp_adm) 42864 (2256)

DpShMCreate: sizeof(tm_adm) 5517056 (27448)

DpShMCreate: sizeof(wp_ca_adm) 64000 (64)

DpShMCreate: sizeof(appc_ca_adm) 64000 (64)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080

DpShMCreate: sizeof(comm_adm) 1384080 (2744)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (296)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (80)

DpShMCreate: sizeof(vmc_adm) 0 (2160)

DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: sizeof(j2ee_adm) 3952

DpShMCreate: SHM_DP_ADM_KEY (addr: 0000000007AC0050, size: 7174832)

DpShMCreate: allocated sys_adm at 0000000007AC0060

DpShMCreate: allocated wp_adm_list at 0000000007AC30B0

DpShMCreate: allocated wp_adm at 0000000007AC32A0

DpShMCreate: allocated tm_adm_list at 0000000007ACDA20

DpShMCreate: allocated tm_adm at 0000000007ACDA70

DpShMCreate: allocated wp_ca_adm at 0000000008010980

DpShMCreate: allocated appc_ca_adm at 0000000008020390

DpShMCreate: allocated comm_adm at 000000000802FDA0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 0000000008181C40

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated gw_adm at 0000000008181CF0

DpShMCreate: allocated j2ee_adm at 0000000008181D30

DpShMCreate: allocated ca_info at 0000000008182CB0

DpShMCreate: allocated wall_adm at 0000000008182D40

DpCommAttachTable: attached comm table (header=000000000802FDA0/ft=000000000802FDB0)

DpSysAdmIntInit: initialize sys_adm

rdisp/test_roll : roll strategy is DP_NORMAL_ROLL

dia token check not active (10 token)

MBUF state OFF

DpCommInitTable: init table for 500 entries

Mon Jun 15 17:05:40 2015

DpRqQInit: keep protect_queue / slots_per_queue 0 / 4001 in sys_adm

rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> EsILock: use Mutex for locking

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 32767MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 32768MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 8191 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 192 MB

mm.dump: set global maximum dump mem to 192 MB

EsRegisterEmCheck: Register EmGetEsHandles at 000000014197AAC0

DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

MPI: dynamic quotas disabled.

MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

Mon Jun 15 17:05:42 2015

J2EE server info

  start = TRUE

  state = STARTED

  pid = 8476

  argv[0] = D:\usr\sap\SOL\DVEBMGS00\exe\jcontrol.EXE

  argv[1] = D:\usr\sap\SOL\DVEBMGS00\exe\jcontrol.EXE

  argv[2] = pf=\\MOBEERPSOL\sapmnt\SOL\SYS\profile\SOL_DVEBMGS00_MOBEERPSOL

  argv[3] = -DSAPSTART=1

  argv[4] = -DCONNECT_PORT=65000

  argv[5] = -DSAPSYSTEM=00

  argv[6] = -DSAPSYSTEMNAME=SOL

  argv[7] = -DSAPMYNAME=MOBEERPSOL_SOL_00

  argv[8] = -DSAPPROFILE=\\MOBEERPSOL\sapmnt\SOL\SYS\profile\SOL_DVEBMGS00_MOBEERPSOL

  argv[9] = -DFRFC_FALLBACK=ON

  argv[10] = -DFRFC_FALLBACK_HOST=localhost

  start_lazy = 0

  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Mon Jun 15 17:06:03 2015

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.4 3.4 4.1) [dpxxdisp.c   1707]

***LOG Q0K=> DpMsAttach, mscon ( MOBEERPSOL) [dpxxdisp.c   12808]

MBUF state LOADING

DpStartStopMsg: send start message (myname is >MOBEERPSOL_SOL_00                       <)

DpStartStopMsg: start msg sent

CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

Mon Jun 15 17:06:04 2015

DpJ2eeLogin: j2ee state = CONNECTED

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]

MBUF state ACTIVE

DpWpBlksLow: max wp blocks in queue is 800 (80 %)

MBUF component UP

DpMsgProcess: 1 server in MBUF

DpAppcBlksLow: max appc blocks in queue is 500 (50 %)

***LOG Q0I=> NiIRead: P=127.0.0.1:64886; L=127.0.0.1:3200: recv (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 5082]

*** ERROR => NiIRead: SiRecv failed for hdl 33/sock 1416

    (SI_ECONN_BROKEN/10053; I4; ST; P=127.0.0.1:64886; L=127.0.0.1:3200) [nixxi.cpp    5082]

DpModState: change server state from STARTING to ACTIVE

[behlau_carlos]

Hello Domnic,

there seems to be a network issue, if I read the log correctly.

Why is the instance communicating with internal IP 127.0.0.1?

Is it running on a virtual landscape?

Best regards

Carlos Behlau

[behlau_carlos]

Hello Domnic,

start the SAP Management Console (MMC) and on the dispatcher task, click with right mouse button => Developer Trace

Browse down. In the last lines, you are finding the reason why the dispatcher is turning yellow.

Best regards

Carlos Behlau