SUM can't connect to Java instance

[Former Member]

Sorry for bothering you with something that has to be a beginner's problem:

I started SUM on the java instance of an MCOD installation. But it fails when it tries to connect to the java instances with sapcontrol:

more /usr/sap/P1E/SUM/sdt/log/SUM/INPUT-OS-USER-PASSWORDS_10.LOG

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/P1E/SUM/sdt/log/SUM/INPUT-OS-USER-PASSWORDS_10.LOG]/-->

<!--PATTERN[INPUT-OS-USER-PASSWORDS_10.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Nov 5, 2013 11:17:20 AM [Info  ]: Connecting to the instance with address http://r9018i1:51013 using the SAPControl web service API.

Nov 5, 2013 11:17:27 AM [Info  ]: Setting the credentials for user p1eadm and a password.

Nov 5, 2013 11:17:27 AM [Info  ]: Setting the service timeout to 300 s.

Nov 5, 2013 11:17:34 AM [Info  ]: The detected sapstartsrv release is 720 and patch level is 401. The minimum supported patch level for this release is 54.

Nov 5, 2013 11:17:34 AM [Info  ]: Connecting to the instance with address http://r9018i1:51013 using the SAPControl web service API.

Nov 5, 2013 11:17:39 AM [Info  ]: Setting the credentials for user p1eadm and a password.

Nov 5, 2013 11:17:39 AM [Info  ]: Setting the service timeout to 300 s.

Nov 5, 2013 11:17:40 AM [Info  ]: Connecting to the instance with address http://r9018i1:51013 using the SAPControl web service API.

Nov 5, 2013 11:17:43 AM [Info  ]: Setting the credentials for user p1eadm and a password.

Nov 5, 2013 11:17:43 AM [Info  ]: Setting the service timeout to 300 s.

Nov 5, 2013 11:17:43 AM [Warning]: No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

Nov 5, 2013 11:17:43 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.tools.sysinfo.RequiredKernelFunctionNotSupportedException: No instances

were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

.

but as you can see, sapstartsrv processes are up 'n running.

r9018:p1eadm 12> ps -ef | grep saps | grep P1E

  p1eadm 17760268        1   0 15:19:48      -  0:29 /usr/sap/P1E/SCS11/exe/sapstartsrv pf=/usr/sap/P1E/SYS/profile/P1E_SCS11_r9018i1 -D

  p1eadm 22610000        1   0 10:37:06      -  0:00 sapstart pf=/usr/sap/P1E/SYS/profile/P1E_SCS11_r9018i1

  p1eadm 26149094        1   0 15:01:59      -  1:59 /usr/sap/P1E/J10/exe/sapstartsrv pf=/usr/sap/P1E/SYS/profile/P1E_J10_r9018i1 -D

  p1eadm 30801988        1   0 10:37:23      -  0:00 sapstart pf=/usr/sap/P1E/SYS/profile/P1E_J10_r9018i1

privileges for sapuxuserchk:

-rwsr-xr-x    1 root     sapsys      1024159 Jan 16 2013  sapuxuserchk

and the provided password for p1eadm is correct, too.

So what may be the error?

[Former Member · Accepted solution]

Hi guys,

now that a colleague has solved the riddle, I would like to pass the information to all of you. Looks like this is somehow typical for the way, SUM handles the upgrade and sometimes makes a mountain out of a molehill:

During some earlier upgrade from 7.x to 7.3 there was created a java central instance J10 out of the former JC10. I don't know whether this is usual behavior or just a fault from the guy who did the upgrade, but the old instance directory remained.

Switching traceleve higher, my colleague discovered that SUM still tried to connect to this old JC10.

So we just removed the old instance directory - and now it runs ...

Regards

Ralf

[Former Member · Accepted solution]

We too faced similar issue where it was not able to find the instance using sapcontrol and also checked the below notes-

1895278 - SUM fails in INPUT-OS-USER-PASSWORDS phase .

1401712 - JSPM/SAPJup/SAPehpi/SUM cannot detect all cluster instances

But that doesn't work and found the below note which resolves our issue even though this note is released for Linux/UNIX-

1950848 - No instances were detected via sapcontrol

Issue logs for our Solman 7.1 upgrade through SUM1.0 SP10 Patch 8-

<!--LOGHEADER[END]/-->

Jun 12, 2014 10:09:20 AM [Info  ]: Creating a proxy to the sapcontrol web service at http://sp-sol:50013

Jun 12, 2014 10:09:22 AM [Info  ]: Setting the credentials for user administrator and a password.

Jun 12, 2014 10:09:22 AM [Info  ]: Using user name administrator to authenticate against the SAPControl web service API.

Jun 12, 2014 10:09:22 AM [Info  ]: Setting the service timeout to 300 s.

Jun 12, 2014 10:09:22 AM [Info  ]: getParameterValue $(0) from $(1)

Jun 12, 2014 10:09:22 AM [Info  ]: getParameterValue response: $(0)

Jun 12, 2014 10:09:22 AM [Info  ]: The detected sapstartsrv release is 721 and patch level is 201. The minimum supported patch level for this release is 21.

Jun 12, 2014 10:09:22 AM [Info  ]: accessCheck for function $(0) ...

Jun 12, 2014 10:09:22 AM [Info  ]: accessCheck for function $(0) is ok

Jun 12, 2014 10:09:22 AM [Info  ]: Creating a proxy to the sapcontrol web service at http://sp-sol:50013

Jun 12, 2014 10:09:24 AM [Info  ]: Setting the credentials for user administrator and a password.

Jun 12, 2014 10:09:24 AM [Info  ]: Using user name administrator to authenticate against the SAPControl web service API.

Jun 12, 2014 10:09:24 AM [Info  ]: Setting the service timeout to 300 s.

Jun 12, 2014 10:09:24 AM [Info  ]: getParameterValue $(0) from $(1)

Jun 12, 2014 10:09:24 AM [Info  ]: getParameterValue response: $(0)

Jun 12, 2014 10:09:24 AM [Info  ]: getParameterValue $(0) from $(1)

Jun 12, 2014 10:09:24 AM [Info  ]: getParameterValue response: $(0)

Jun 12, 2014 10:09:25 AM [Warning]: No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

Jun 12, 2014 10:09:25 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.tools.sysinfo.RequiredKernelFunctionNotSupportedException: No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

.

Saurabh Mishra

[Farid]

Thank you so much for providing the solution Ralf !

Instead of Responding "solved" (Like so many *******)

[Former Member]

Hello Ralf,

Is the Java instance up and running ? if not then you need to bring it up.  Or restart the instance and try again connecting with SUM.

Regards,

Mudasir.

[Former Member]

Hi Mudasir,

yes it's up. Sapcontrol reports green status of all processes, and I may log on. Just the communication between SUM and sapcontrol does not work...

Thank you anyway.

Ralf

[Former Member]

We are doing upgrade using SUM 1.0 SP06 patch 5, we have faced couple of major problems during this upgrade.

There is major bug in the tool hence please don’t use SUM 1.0 SP06.

If you want to do any upgrades please wait for the next higher patch level is available on SMP or use SUM 1.0 SP5

SAP has released note 1831282 on SUM 1.0 SP06..

BR,

Prabhakar

[Former Member]

Hi everybody,

thanks for a lot of cool hints, but currently I'm a bit lost:

What I tried out:

• I filled the exe directorys for the instances from the sapmount. So /usr/sap/P1E/J10/exe and /sapmnt/P1E/exe have the same content.
• I checked again sapuxuserchk permissions.
• I cleaned up the profile directory. There were some old profiles and links.
• I started STARTUP providing a hostname (sometimes we get problems with our "virtual hostname" concept and sapinst / JSPM if we don't provide a hostname.
• sapcontrol -GetProcessList shows GREEN status
• Just to be sure I started JSPM and discovered that JSPM had no problems connecting to the local system - expecially the sapcontrol check was successful.
• Not to mention that I always installed SUM from scratch ...
• My last try was to take the new SUM 10 SP 09_0, but this didn't change anything significantly

But until now all efforts failed.

I discovered some nice TRACE-File:

<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[/usr/sap/P1E/SUM/sdt/trc/DETECT.TRC]/-->
<!--PATTERN[DETECT.TRC]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Nov 5, 2013 3:54:20 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found i
n class path
Nov 5, 2013 3:54:22 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found
in class path
Nov 5, 2013 3:54:22 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found i
n class path
Nov 5, 2013 3:54:23 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found
in class path
Nov 5, 2013 3:55:44 PM [Error]:                                                               com.sap.sdt.dsu.ui.SDTCommonGUIManager [Thread[ProcessWorker,5,main]]: The common ui roadmap id is: we
lcome
Nov 5, 2013 3:55:50 PM [Error]:                                                               com.sap.sdt.dsu.ui.SDTCommonGUIManager [Thread[ProcessWorker,5,main]]: The common ui roadmap id is: in
put-credentials
Nov 5, 2013 3:57:01 PM [Error]:                                                               com.sap.sdt.executor.step.StepExecutor [Thread[ProcessWorker,5,main]]: The following problem has occur
red during step execution: java.lang.reflect.InvocationTargetException.
Nov 5, 2013 3:57:01 PM [Error]:                                                               com.sap.sdt.executor.step.StepExecutor [Thread[ProcessWorker,5,main]]: The following problem has occur
red during step execution: com.sap.sdt.tools.sysinfo.RequiredKernelFunctionNotSupportedException: No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process run
ning.
.
Nov 5, 2013 3:57:01 PM [Error]:                                                           com.sap.sdt.executor.module.ModuleExecutor [Thread[ProcessWorker,5,main]]: A problem has occurred: com.sap
.sdt.executor.exception.StepExecutionException: Problem while trying to execute operation on service  input-os-user-passwords. The following problem has occurred java.lang.reflect.InvocationTarget
Exception. CSN Component BC-UPG-TLS-TLJ.
No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process running.
.
Nov 5, 2013 3:57:01 PM [Error]:                                                           com.sap.sdt.executor.module.ModuleExecutor [Thread[ProcessWorker,5,main]]: No instances were detected via
sapcontrol. Most probably there is no local sapstartsrv process running.
Nov 5, 2013 3:57:01 PM [Error]:                                                           com.sap.sdt.executor.module.ModuleExecutor [Thread[ProcessWorker,5,main]]: com.sap.sdt.tools.sysinfo.Requi
redKernelFunctionNotSupportedException: No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

        at com.sap.sdt.j2ee.tools.sysinfo.InstanceDetector.getSysmtemInstanceList(InstanceDetector.java:130)
        at com.sap.sdt.j2ee.services.servicesimpl.UserCredentialsDialogService.getSystemInstanceList(UserCredentialsDialogService.java:883)
        at com.sap.sdt.j2ee.services.servicesimpl.UserCredentialsDialogService.doDialog(UserCredentialsDialogService.java:549)
        at com.sap.sdt.j2ee.services.servicesimpl.UserCredentialsDialogService.showUserCredentialsDialogInternal(UserCredentialsDialogService.java:253)
        at com.sap.sdt.j2ee.services.servicesimpl.UserCredentialsDialogService.showUserCredentialsDialog(UserCredentialsDialogService.java:231)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sap.sdt.executor.step.StepExecutor.executeStep(StepExecutor.java:186)
        at com.sap.sdt.executor.module.ModuleExecutor.executeModule(ModuleExecutor.java:104)
        at com.sap.sdt.executor.action.ActionExecutor.executeModule(ActionExecutor.java:348)
        at com.sap.sdt.executor.action.ActionExecutor.executeAction(ActionExecutor.java:83)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeOrRevokeRegularAction(UseCaseExecutor.java:528)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeActionInternal(UseCaseExecutor.java:431)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeAction(UseCaseExecutor.java:406)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeActionInRoadmapStep(UseCaseExecutor.java:270)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeRoadmapStepAction(UseCaseExecutor.java:242)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeRoadmapStepActions(UseCaseExecutor.java:226)
        at com.sap.sdt.executor.usecase.UseCaseExecutor.executeRoadmapStep(UseCaseExecutor.java:194)
        at com.sap.sdt.dsu.service.UseCaseService$1.run(UseCaseService.java:784)

Nov 5, 2013 3:57:01 PM [Error]:                                                           com.sap.sdt.executor.module.ModuleExecutor [Thread[ProcessWorker,5,main]]: Problem while trying to execute
operation on service  input-os-user-passwords. The following problem has occurred java.lang.reflect.InvocationTargetException. CSN Component BC-UPG-TLS-TLJ.

Any suggestions?

[Former Member]

Hi,

Looks like most of the things have been tried.

Can you try and do kernel upgrade and see if it helps. Dont forget to run saproot .sh.

Second thing try to set SAPLOCALHOST in the env and see if it helps you.

Third i still think that some of the kernel files are different in some exe directory so they to copy the new kernel in all the three directory.

/usr/sap/SID/SCS11/exe/sapuxuserchk

/usr/sap/SID/J10/exe/sapuxuserchk

/sapmnt/SID/exe/sapuxuserchk

Once this is done try to reset the SUM tool and delete the directory and extract it again.

Have you also check the note that i provided you earlier all the steps. As it talk about running sapstartsrv with correct settings.

Try for restart the application and then start sum tool.

Thanks

Rishi Abrol

[Reagan]

Hello

Check these notes

927637  - Web service authentication in sapstartsrv as of Release 7.00

1401712  - JSPM/SAPJup/SAPehpi/SUM cannot detect all cluster instances

Also can you check the sapuxuserchk file permission in all places.

ls-la /usr/sap/P1E/SCS11/exe/sapuxuserchk

ls-la /usr/sap/P1E/J10/exe/sapuxuserchk

ls-la /sapmnt/P1E/exe/sapuxuserchk

Regards

RB

[Former Member]

Hello Reagan,

it looks like something very SUM-specific. JSPM has no problems checking the instances. Any other suggestions?

Regards

Ralf

[Reagan]

There is nothing wrong in checking these things

Also try to restart the service and see if that helps

sapcontrol -nr <Instance_Number> -host <Hostname> -function RestartService

I would also try stopping the instance, delete the stream files in the /tmp directory and restart the system and then check if I am able to work with SUM.

These are just suggestion and sometimes it works and sometimes it won't.

Regards

RB

[Former Member]

Hi Reagan,

thanks for advice. What are the stream files in the /tmp directory?

Regards

Ralf

[Former Member]

Note 1600846 - JSPM/SUM calls sapcontrol without user credentials

[Former Member]

Hi,

I had the same issue and the issue fixed by this note.

1895278 - SUM fails in INPUT-OS-USER-PASSWORDS phase .

Please also check that you have same kernel files in /sapmnt/SID/exe and /usr/sap/SID/J*/exe.

specialy sapuxuserchk and the permission of this file

1 ) root@xxxxxxx(/sapmnt/SID/exe)# chown root:sapsys sapuxuserchk

2) root@xxxxxxx(/sapmnt/SID/exe)# chmod u+s,o-rwx sapuxuserchk

Thanks

Rishi Abrol

[Former Member]

Sorry for not mentioning this: SUM is SP8 PL9, so note 1600846 does not apply.

[Former Member]

Hi Rishi,

that was a nice one. As I wrote, I already checked / corrected the privileges for sapuxuserchk. But the sapcontrol failure could have been - could ...:

05.11.2013 12:50:20

GetSystemInstanceList

OK

hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus

r9018i1, 11, 51113, 0, 1, GATEWAY|MESSAGESERVER|ENQUE, GREEN

r9018i1, 10, 51013, 51014, 3, J2EE|ICMAN|IGS, GREEN

Perhaps I should just start the upgrade from scratch again?

Just another question: This task has a timeout of 300 secs, as is written in the protocols. Since the system response time is between lousy and half-dead, I would not rule out that this is a simple timeout problem. Do you know, how to modifiy the timeout for this step?

Regards

Ralf

[Former Member]

Hi,

First of all there is SP10 also released ,so always try to use the latest tools before starting the upgrade if this is your first system .Try to upgrade the system before going for the upgrade and see if it helps.

Second thing you should reset the tool and start again.

Third thing i will try to find if i the exact details of the time out.

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

I downloaded the newest SUM and tried again - nothing changed. I tried some other changes, too (see my reply to myself ...) Now I'm really rather clueless.

Any suggstions?

Regards

Ralf

[Former Member]

You'll have to reset the current one and restart the ugprade procedure.

If you plan uninstalled Java instance then you might need to perform some post uninstallation process.

Follow below link http://scn.sap.com/thread/776757

after that reset your upgrade process and then restart the upgrade. This will help for sure.

BR,

Prabhakar

[AtulKumarJain]

Hi Ralf,

Please check sapcontrol command output for GetprocessList with your java instance no .

It should show all green , then only it will connect .

BR

atul

[Former Member]

r9018:p1eadm 2> sapcontrol -nr 10 -function GetProcessList

05.11.2013 12:41:12
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
jstart, J2EE Server, GREEN, All processes running, 2013 11 05 10:37:25, 2:03:47, 8650908
igswd_mt, IGS Watchdog, GREEN, Running, 2013 11 05 10:37:25, 2:03:47, 15794284
r9018:p1eadm 3> sapcontrol -nr 11 -function GetProcessList

05.11.2013 12:41:57
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, GREEN, Running, 2013 11 05 10:37:07, 2:04:50, 29622510
enserver, EnqueueServer, GREEN, Running, 2013 11 05 10:37:08, 2:04:49, 15269914
gwrd, Gateway, GREEN, Running, 2013 11 05 10:37:08, 2:04:49, 21889200
r9018:p1eadm 4>

[Former Member]

Hi,

Please check the SAP Note No. 1681776.

BR,

Prabhakar