cancel
Showing results for 
Search instead for 
Did you mean: 

SAP not running, disp+work, Dispatcher, GRAY, Stopped, , , 7670

Former Member
0 Kudos

Hi,

I'm trying to install an ABAP AS environment on OpenSuSE 42.3 as per this link: https://blogs.sap.com/2017/09/04/newbies-guide-installing-abap-as-751-sp02-on-linux/.

When i try to start SAP with the npladm account i receive the following output:

Checking syb Database Database is running ------------------------------------------- Starting Startup Agent sapstartsrv OK Instance Service on host vhcalnplci started ------------------------------------------- starting SAP Instance ASCS01 Startup-Log is written to /home/npladm/startsap_ASCS01.log ------------------------------------------- /usr/sap/NPL/ASCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function Start Instance on host vhcalnplci started Starting Startup Agent sapstartsrv OK Instance Service on host vhcalnplci started ------------------------------------------- starting SAP Instance D00 Startup-Log is written to /home/npladm/startsap_D00.log ------------------------------------------- /usr/sap/NPL/D00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start Instance on host vhcalnplci started

Which looks good i think. However, when i run ss -nlp | grep 3300 or ss -nlp | grep 3200, nothing shows up.

When i run sapcontrol -nr 00 -function GetProcessList i get this:

08.04.2018 19:57:12 GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid igswd_mt, IGS Watchdog, GREEN, Running, 2018 04 08 19:30:32, 0:26:40, 7671 disp+work, Dispatcher, GRAY, Stopped, , , 7670

I assume this is why I can't access SAP. How can I start disp+work or find out why it is not starting?

Kind regards,

Sven.

BJarkowski
Active Contributor

Please provide your dev_disp and dev_w0 log files. They are located somewhere in /usr/sap/NPL/DXX/work

Accepted Solutions (0)

Answers (6)

Answers (6)

RolandKramer
Product and Topic Expert
Product and Topic Expert

Check the work directory of the Instance, either there are missing files like /etc/services or /usr/sap/sapcontrol

or additional hints in the following Notes

Note 2533003 - sapcontrol webmethods end with FAIL: NIECONN_REFUSED

Note 2631116 - Enqueue Server status: Running but not responding

typically with the new SAP Kernel there is also a Memory Problem at startup, as several Parameter are calculated dynamically now. You should combine at least the four Parameters together with the start of the SAP Instance and check the Instance Profile with

sappfpar pf=<SID>_D<nr>_server check

PHYS_MEMSIZE = 128000
ipc/shm_psize_10 = 198000000
ipc/shm_psize_40 = 1978000000
abap/buffersize = 1400000

this is the most common error with the developer or CAL images provided by SAP. Adapt the values to your system ressources

Best Regards Roland

former_member601011
Discoverer
0 Kudos

I have the sane problem like SVEN

When I enter "sapcontrol -nr 00 -function GetProcessList" I get

vhcalnplci:npladm 58> sapcontrol -nr 00 -function GetProcessList

20.01.2019 13:17:10 GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid disp+work,

Dispatcher, GRAY, Stopped, , , 24689

igswd_mt, IGS Watchdog, GREEN, Running, 2019 01 20 12:42:01, 0:35:09, 24690

"sapcontrol -nr 01 -function GetProcessList" shows

vhcalnplci:npladm 58> sapcontrol -nr 01 -function GetProcessList 20.01.2019 13:28:25 GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid msg_server, MessageServer, GREEN, Running, 2019 01 20 12:41:47, 0:46:38, 23139 enserver, EnqueueServer, GREEN, Running, 2019 01 20 12:41:47, 0:46:38, 23140

Here is my dev_disp file is attached

Many thanks for your help

former_member190849
Participant
0 Kudos

I am suffering from the same situation, after having successfully installed NPL on openSUSE within VirtualBox on Windows 10 Pro. Is there any help around?

former_member230159
Contributor
0 Kudos

Hello Heiner,

What is the output of command: sapcontrol -nr XX -function GetProcessList ?

Is the dispatcher in stopped status?

If yes please attach dev_disp + dev_disp.old trace file here.

Regards,

Manjunath Hanmantgad

former_member190849
Participant
0 Kudos

Hello Manjunath Hanmantgad,

the problem came up with nw abap trial version 751 on openSUSE Leap 15.0 within VirtualBox 5.2.14. Since then I uninstalled that and installed on openSUSE Leap 42.3. With this, the problem did not come up.

Sorry that I cannot attach the trace file any more (that might have given some insight of the internals).

Kind regards, Heiner

LinkinP
Explorer
0 Kudos

Hello Heiner,

I am having the same issue, so I plan to uninstall openSUSE Leap 15.0 and move to 42.3. But can you tell me the uninstall process that you followed ? Did you uninstall SAP and then openSUSE or you just uninstalled OpenSUSE Leap 15.0 and install 42.3 and SAP started working on 42.3 ?

raquel_gomez
Employee
Employee
0 Kudos

Hi Sven,
How are you starting the system? Note that scripts startsap and stopsap are deprecated, you can either use SAP Management Console (SAP MC) or the SAP command sapcontrol.
See Note #1763593 - Starting and stopping SAP system instances - startsap/stopsap are deprecated

Based on the command output you provided, ASCS01 and D00 servers (both running on host vhcalnplci) were correctly started.
Command "sapcontrol -nr 00 -function GetProcessList" shows Dispatcher stopped, please provide here complete dev_disp trace, so that I can check why it didn't start.
What does command "sapcontrol -nr 01 -function GetProcessList" show? Is ASCS correctly started?

Regards,
Raquel Gómez
SAP Product Support

JPReyes
Active Contributor
0 Kudos
former_member233657
Active Participant
0 Kudos

Hi Sven,

is your DB running (run R3trans -d)? Did you check dev_w0?

Kind regards,

Martin