SUM is failing "Service for instance on host is not started after 240 seconds"

[former_member186587]

I am on execution phase, current step: Restart System for Java-Only.

I get below error:

***********************************************************************

An error occurred during the execution of Restart System for Java-Only of action execute.

Service com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService failed with the following message:

Service for instance 00 on host servername is not started after 240 seconds.

For more information, see the log file /install/BJD/SUM/sdt/log/SUM/RESTART-SYSTEM-JAVAONLY_02.LOG.

Use the provided information to troubleshoot the problem. There might be a SAP note providing a solution to this problem. Search the SAP notes using the following search terms:

SUM,execute,component-deploy-710,restart-system-javaonly,com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService,class com.sap.sdt.j2ee.tools.controlservice.ServiceControllerException

***********************************************************************

Why SUM is ONLY using 240 seconds to restart system. My Portal system does start successfully, but takes around 5 min (more then 240 sec) to start. What is the workaround to pass this error?

SUM version: SUM10SP16_10-20006540.SAR

Bhavin

[former_member186587 · Accepted solution]

Solution:

Based on SAP Note # 1642340, our finding/resolution was to disable environment variable "SECUDIR" from sidadm profiles in its home directory (.sapenv_servername.csh & .sapenv_servername.sh). We did not changed/disabled  Instance profile parameters for SSL configuration.

We used same SUM tools in our Sandbox System where we had enabled SSL using SHA256 Certs. We did not ran into any issues.

It is strange that some how SUM is looking for environment variable of sidadm, and its forcing to use SSL connection to communicate to sapcontrol.

[former_member186587]

Sriam:

1. Snippet of requested logs file.

May 27, 2016 2:59:37 PM [Info  ]:   Command line: /usr/sap/BJD/J51/exe/sapcontrol -nr 51 -host servername -prot NI_HTTPS -function GetProcessList

May 27, 2016 2:59:37 PM [Info  ]:   Standard out: /install/BJD/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_51_853.OUT

May 27, 2016 2:59:37 PM [Info  ]: Process ID 286 has been started.

May 27, 2016 2:59:37 PM [Info  ]: Waiting for process ID 286, name sapcontrol to finish.

May 27, 2016 2:59:37 PM [Info  ]: Process ID 286, name sapcontrol has been finished, exit code 1.

May 27, 2016 2:59:37 PM [Info  ]: The sapcontrol service on host servername and instance 51 is not started.

May 27, 2016 2:59:39 PM [Info  ]: Process ID 287, name sapcontrol has been started.

May 27, 2016 2:59:39 PM [Info  ]:   Command line: /usr/sap/BJD/J51/exe/sapcontrol -nr 51 -host servername -prot NI_HTTPS -function GetProcessList

May 27, 2016 2:59:39 PM [Info  ]:   Standard out: /install/BJD/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_51_854.OUT

May 27, 2016 2:59:40 PM [Info  ]: Process ID 287 has been started.

May 27, 2016 2:59:40 PM [Info  ]: Waiting for process ID 287, name sapcontrol to finish.

May 27, 2016 2:59:40 PM [Info  ]: Process ID 287, name sapcontrol has been finished, exit code 1.

May 27, 2016 2:59:40 PM [Info  ]: The sapcontrol service on host servername and instance 51 is not started.

May 27, 2016 2:59:42 PM [Info  ]: Process ID 288, name sapcontrol has been started.

May 27, 2016 2:59:42 PM [Info  ]:   Command line: /usr/sap/BJD/J51/exe/sapcontrol -nr 51 -host servername -prot NI_HTTPS -function GetProcessList

May 27, 2016 2:59:42 PM [Info  ]:   Standard out: /install/BJD/SUM/sdt/tmp/SAPCONTROL_GETPROCESSLIST_51_855.OUT

May 27, 2016 2:59:42 PM [Info  ]: Process ID 288 has been started.

May 27, 2016 2:59:42 PM [Info  ]: Waiting for process ID 288, name sapcontrol to finish.

May 27, 2016 2:59:42 PM [Info  ]: Process ID 288, name sapcontrol has been finished, exit code 1.

May 27, 2016 2:59:42 PM [Info  ]: The sapcontrol service on host servername and instance 51 is not started.

May 27, 2016 2:59:42 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.controlservice.ServiceControllerException: Service for instance 51 on host servername is not started after 240 seconds.

2. Kernel version: 722_EXT_REL ; 64 bit UNICODE; Patch Level 101

3. SUM is started using root user as per SUM 1.0 SP16 Patch level 10. I am able to restart Portal System (manually).

Ian:

Yes I am able to manually start Portal system using sapcontrol command. Also SUM is able to start Portal System but takes around 6 min and before it completely restarts it throws error.

sapcontrol -nr 51 -host servername -prot NI_HTTP -function StartSystem (System starts successfully)

sapcontrol -nr 51 -host servername -prot NI_HTTPS -function StartSystem (System fails with below error)

servername:bjdadm 65> /usr/sap/BJD/J51/exe/sapcontrol -nr 51 -host servername -prot NI_HTTPS -function GetProcessList

sapparam: sapargv(argc, argv) has not been called!

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

27.05.2016 17:05:19

GetProcessList

FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()

Bhavin

[Former Member]

Hello Bhavin,

Can you please try the following.

1. sapcontrol -nr 51 -host <servername> -nr 51 -function StartService BJD

2. Try your GetProcessList again

Let us know what happens as a result of the above.

3. cd /install/BJD/SUM/sdt/param

4. cp jump_config.txt jump_config.txt.ORG

5. vi jump_config.txt

6. Set /sapstartsrv/httpsconnection = false

Retry the step from SUM.

KR,

A.

[IanSegobio]

Hello Bhavin,

Can you find out what is exactly the command which fails after this time? Judging the error message, it seems that sapstartsrv is facing some trouble to launch.

*** Is there a sapstartsrv process running at the affected host associated with instance 00?

*** Are you able to start it manually through command:

sapcontrol -nr 00 -function StartService bjd

Cheers,

Ian Segóbio.

[MarceloPinheiro]

Hi Bhavin,

if you monitor the Java instance and see that running, you can do a retry in SUM to continue. Is this not working to continue the upgrade?

Thanks,
Marcelo Pinheiro

[former_member186587]

I have tried multiple time with no success.

Bhavin

[Sriram2009]

Hi

1.  Could you share the log file RESTART-SYSTEM-JAVAONLY_02.LOG.

2. Could you share the kernel release and level?

3. Are starting the using the SIDADM user id?

BR

SS

[MarceloPinheiro]

Hi,

share the files to us see the error in J2EE side. Maybe a error there is preventing the engine to start.

Thanks,
Marcelo Pinheiro

[former_member186587]

Message edited.

[MarceloPinheiro]

Hi,

please upload std_severver*, dev_server*, dev_bootstrap*. There we can see if the j2ee is working.

Thanks,
Marcelo Pinheiro

[former_member186587]

Please see attached work directory logs.

Bhavin

std_server0.out.txt.zip

dev_bootstrap.txt.zip

dev_server0.txt.zip

[MarceloPinheiro]

Hi

there are no issue in the j2ee. No exceptions in the traces and the system is running since May 30 09:06:47.

Took 5 minutes to start, so the issue seems to be related to SUM part.

thanks,

Marcelo Pinheiro

[former_member186587]

Yes that is correct. When SUM triggers step "Restart System for Java-Only", it does successfully restarts but takes more then threshold "240 sec". I wanted to know where is this threshold defined and/or how we can skip/increase this value.

I have opened OSS Message with SAP as well and I am waiting for response.

Bhavin