SAP Knowledge Base Article - Preview

1932555 - Dispatcher startup issue in Kernel 740/741/742

Symptom

An SAP ABAP instance is not starting (it can be the shadow instance of an upgrade process / procedure). The kernel release in use by the affected instance is 740.

The “dev_disp” trace file is not being created/updated. However, you notice that a “dev_disp.new” trace file is. When you open the “dev_disp.new” file, the following trace entries can be observed:

  • Case 1:
    (...)
    *** ERROR => NiHLGetNodeAddr: NiPGetHostByName failed (rc=-1) [nixxhl.cpp   278]
    MtxInit: 30000 0 0
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    ***LOG Q0I=> NiISetSockOpt: setsockopt (227: Can't assign requested address) [/bas/740_REL/src/base/ni/nixxi.cpp 9121]
    *** ERROR => NiISetSockOpt: SiSetSockOpt failed for hdl 1/sock 7
        (SI_EADDR_NAVAIL/227; I4; DG; IPPROTO_IP-IP_ADD_MEMBERSHIP) [nixxi.cpp    9121]
    *** ERROR => NiIDgHdlGroupAdm: failed to join 224.0.0.136 on interface 0.0.0.0 [nixxi.cpp    9536]
    *** ERROR => RqQInit: NiDgHdlJoinGroup failed (rc=-10) [dpQueue.c    1481]
    *** ERROR => DpIPCInit2: RqQInit [dpxxtool2.c  508]
    *** DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2
    *** DISPATCHER EMERGENCY SHUTDOWN ***
    (...)

 

  •  Case 2:
    (...)
    *** ERROR => NiHLGetNodeAddr: NiPGetHostByName failed (rc=-1) [nixxhl.cpp   279]
    *** ERROR => NiHLGetHostName: NiPGetHostByAddr failed (rc=-1) [nixxhl.cpp   495]
    MtxInit: 30000 0 0
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    ***LOG Q0I=> NiISetSockOpt: setsockopt (19: No such device)
    /bas/740_REL/src/base/ni/nixxi.cpp 9121]
    *** ERROR => NiISetSockOpt: SiSetSockOpt failed for hdl 1/sock 6
        (SI_EADDR_NAVAIL/19; I4; DG; IPPROTO_IP-IP_ADD_MEMBERSHIP) [nixxi.cpp    9121]
    *** ERROR => NiIDgHdlGroupAdm: failed to join 224.0.0.130 on interface 0.0.0.0 [nixxi.cpp    9539]
    *** ERROR => RqQInit: NiDgHdlJoinGroup failed (rc=-10) [dpQueue.c    1488]
    *** ERROR => DpIPCInit2: RqQInit [dpxxtool2.c  508]
    *** DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2
    *** DISPATCHER EMERGENCY SHUTDOWN ***
    (...)


Read more...

Environment

  • Product independent
  • SAP Kernel 7.40 (any patch level)
  • SAP Kernel 7.41 (any patch level)
  • SAP Kernel 7.42 (up to patch level 13)
  • Client/Server Technology
  • SAP running on UNIX/Linux servers

Product

SAP NetWeaver all versions

Keywords

Setsockopt, Multicast, Dispatcher, Does not start, Not start, Not starting, Instance, System, Yellow, Request handling without progress , KBA , BC-CST-DP , Dispatcher, Task Handler , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-CST , Client/Server Technology , BC-UPG , Upgrade - general , BC-UPG-OCS-SPA , Support package tools for ABAP , BC-CST-STS , Startup Service , BC-UPG-PRP , Upgrade Preparation , BC-UPG-OCS-ZDM , Near Zero Downtime Maintenance , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.