Issue in PREP_PRE_CHECK/INSTANCELIST_INIT phase

Hello Everyone!!

I recently came across a issue related to SUM. It got stopped in stage “PREP_PRE_CHECK/INSTANCELIST_INIT”

The error which I received was :

“SYSTEM MANAGER: instance list does not contain SUM central instance”

==> The version of SUM I was using was : SUM 2.0 SP0 (PL4)

The steps to reproduce the issue are :

Step 1: Start SUM (SUMSTART confighostagent)

Step 2: Provide stack.xml file generated in maintenance planner

My environment :

This trouble ticket was created by SAPup on <DATE/TIME>——————————————————-

——SAPup broke during phase INSTANCELIST_INIT in module PREP_PRE_CHECK / Checks the system statusError Message: Last error code set:SYSTEM MANAGER: instance list does not contain SUM central instance.

————————————————————-Summary of SAPup:————————————————————-SAPup Release: lmt_020SAPup Version: SAPup release lmt_020 version 53.000

————————————————————-Summary of operating system details:————————————————————-OS Type: Linux X86_64OS Version: 2.17-————————————————————Summary of database details:————————————————————-Database Type: hdbDatabase Version: ————————————————————-

ANALYSIS :

When I looked into the SAPUp.eco log I could find the following entries:

1 ETQ399 SYSTEM MANAGER: sapcontrol feature -systempki is available.

// My first clue!!

3 ETQ120 <DATE/TIME>: PID 57041 execute ‘/usr/sap/<SID>/SYS/exe/uc/linuxx86_64/sapcontrol -prot NI_HTTP -host <hostname> -nr <instance number>’, output written to ‘/install/SUM/abap/log/SAPCONTROL_FEATURE.OUT’.

3WETQ122 <DATE/TIME>: PID 57041 exited with status 1 (time: 0.0/ 0.0/ 0.0/27MB real/usr/sys/maxmem)1 ETQ399 SYSTEM MANAGER: sapcontrol feature sapcontrol (Version: is available.1

ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 00, Instance Host: <hostname>1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 01, Instance Host: <hostname>1

ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO|DIAG_NO|WEBDISP.1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO|DIAG_YES.

// Here I could see somehow the ASCS is not being detected ?? // 
/* Very strange!! */

1EETQ399 SYSTEM MANAGER: initialize instance list has failed.1EETQ399 SYSTEM MANAGER: instance list does not contain SUM central instance. <====================1EETQ399 Last error code set is: SYSTEM MANAGER: instance list does not contain SUM central instance. <<==========
// Here I could notice the error //

1EETQ204 Upgrade phase “INSTANCELIST_INIT” aborted with severe errors (“<DATE/TIME>”)
// This is the phase where the error occurred //

Now as next steps my first clue was to check if the sapcontrol detected ASCS instance!!

This apparently lead to conclusion too 🙂

I checked with sapcontrol command using the systempki as with 742 sapstartsrv always initializes the System PKI and offers an https based access to his web service methods with a certificate of the system PKI. Sapstartsrv also uses the system PKI to make calls to another sapstartsrv instance in the same system.

A blog is nicely written on this topic -> https://blogs.sap.com/2015/04/04/secure-server-communication-in-sap-netweaver-as-abap/

Back to to topic!!!

When I checked with sapcontrol with systempki I could find the result as:
sapcontrol -host <hostname> -nr <instance number> -systempki /usr/sap/<SID>/SYS/profile -function GetProcessList

and the output was :

“PKI library initialization failed”

Now , this is strange output.

After this my next step was to check the “Master Note i.e 2200230 – Problems with use of system PKI ” (this note is very beautifully written and contains much of the information).

I could notice a strange thing on this.

Whenever I ran the sapcontrol command with systempki command with just the “profile” for example:sapcontrol -host <hostname> -nr <instance number> -systempki /usr/sap/<SID>/SYS/profile -function GetProcessList

It FAILED.

It strike to me that something is wrong here.

I had hit a idea here!!

Why was I using the work ‘profile’ here ??

Shouldn’t I be giving the complete path of the profile here ??

And there I was with the solution!!  🙂

It worked….

When I issued the sapcontrol command with systempki option I got my results..

The final command is:

“sapcontrol -host <hostname> -nr <instance number> -systempki /usr/sap/<SID>/SYS/profile/<complete path to profile> -debug -function GetProcessList”

With this I could get the output..

Now the main part is why wasn’t the sapcontrol returning the output with just the profile and it required the complete path to profile??

The reason was that apparently sapcontrol cannot take the profile value directly.If the complete profile name is not specified then sapcontrol will use the sapparam build in default values which will not work giving the error.

So to fix the issue we need to specify the complete path of profile.

After this I could get past the initial phase i.e “PREP_PRE_CHECK/INSTANCELIST_INIT”

I hope you this blog answers some questions regarding to the issues being faced when you encounter this problem!!

MAY THE FORCE BE WITH YOU!!

Please let me know in case any queries!!!

Regards,

Manjunath Hanmantgad