Skip to Content
avatar image
Former Member

MAIN_SHDRUN/START_SHDI_FIRST

Hi ,

When using SUM update for Solution Manager 7.2 SP3 in RHEL 7, we are receiving the below error. i have pasted startsfi.log and attached the DEVTRACE.TXT

Severe error(s) occurred in phase MAIN_SHDRUN/START_SHDI_FIRST! Last error code set: Shadow instance couldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process /usr/sap/PSA/SUM/abap/exe/sapcontrol exited with 2, see '/usr/sap/PSA/SUM/abap/log/SAPup.E CO' for details

STARTSFI.LOG

1 ETQ201 Entering upgrade-phase "MAIN_SHDRUN/START_SHDI_FIRST" ("20180102073338") 2 ETQ367 Connect variables are set for standard instance access 4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000' 4 ETQ399 Environment variables: 4 ETQ399 dbs_ora_schema=SAPSR3 1 ETQ206 Executing pre-phase OS specific actions 0/1. 1 ETQ200 Executing actual phase 'MAIN_SHDRUN/START_SHDI_FIRST'. 1 ETQ399 Phase arguments: 2 ETQ399 Arg[0] = 'START_SERVICE' 2 ETQ399 Arg[1] = 'DEVTRACE.LOG' 2 ETQ399 Starting shadow instance 4 ETQ399 Set database connect to shadow. 4 ETQ399 Set environment for shadow connect: 4 ETQ399 Set RFC variables for shadow connect: 4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000' 4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT" 4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system" 4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW" 4 ETQ399 Requirement for tp maps to 'exe' 4 ETQ383 translates to path "/usr/sap/PSA/SUM/abap/exe" 4 ETQ399 Set tool parameters for shadow connect with TPPARAM 'SHADOW.TPP'. 4 ETQ399 Set RFC variables for shadow connect: 4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000' 1 ETQ359 RFC Login to: System="PSA", AsHost="pmlsol" Nr="04", Client="000", GwHost="pmlsol", GwService="sapgw04" 2EETQ231 RFC Login failed 2 ETQ353 Starting system 1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_YES. 1 ETQ399 SYSTEM MANAGER: instance found. 1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_YES. 1 ETQ399 SYSTEM MANAGER: instance found. 1 ETQ399 SYSTEM MANAGER: STOPSAP on UNIX. 1 ETQ399 SYSTEM MANAGER: STOPSAP with SAPCONTROL. 1 ETQ399 SYSTEM MANAGER: SAPControl tries to control all instances. 1 ETQ399 SYSTEM MANAGER: Calling getInstances. 1 ETQ399 SYSTEM MANAGER: found instance for action STOP : Instance Number: 04 1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTROL action STOP for instance 04 and host pmlsol. 1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 04 on host pmlsol. 2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 4 for used ports on host 'pmlsol'. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3204 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3304 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3604 appears to be used. 1 ETQ399 SYSTEM HEALTH MANAGER: call test rfc. 4 ETQ399 Set RFC variables for shadow connect: 4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000' 1 ETQ359 RFC Login to: System="PSA", AsHost="pmlsol" Nr="04", Client="000", GwHost="pmlsol", GwService="sapgw04" 2EETQ231 RFC Login failed 1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist. 1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: pmlsol and instance: 04 3 ETQ120 20180102073338: PID 27106 execute '~/exe/sapcontrol -format script -prot NI_HTTP -host pmlsol -nr 04 -function GetProcessList', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3 ETQ122 20180102073338: PID 27106 exited with status 0 (time: 0.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1 ETQ399 SYSTEM HEALTH MANAGER: System up and running, go on with stop action 1 ETQ399 SAPCONTROL MANAGER: stopWait with host: pmlsol and instance: 04 3 ETQ120 20180102073338: PID 27108 execute '~/exe/sapcontrol -prot NI_HTTP -host pmlsol -nr 04 -function StopWait 300 10', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3 ETQ122 20180102073348: PID 27108 exited with status 0 (time: 10.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1 ETQ399 SYSTEM HEALTH MANAGER: running postCheck for instance 04 on host pmlsol 4 ETQ399 Set RFC variables for shadow connect: 4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000' 1 ETQ359 RFC Login to: System="PSA", AsHost="pmlsol" Nr="04", Client="000", GwHost="pmlsol", GwService="sapgw04" 2EETQ231 RFC Login failed 2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 4 for used ports on host 'pmlsol'. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3204 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3304 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3604 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3904 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 8104 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 30401 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 50419 appears to be unused. 1 ETQ399 SYSTEM HEALTH MANAGER: System is down and fine 1 ETQ399 SYSTEM MANAGER: Poststop on Unix. 1 ETQ399 SYSTEM MANAGER: STARTSAP on UNIX. 1 ETQ399 SYSTEM MANAGER: STARTSAP with SAPCONTROL. 1 ETQ399 SYSTEM MANAGER: PRESTARTACTION on UNIX. 1 ETQ399 SYSTEM MANAGER: Starting the service. 1 ETQ399 SYSTEM MANAGER: StartService on Unix. 1 ETQ399 SYSTEM MANAGER: Starting service. 1 ETQ399 SAPCONTROL MANAGER: startService 1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction on UNIX 1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using start path: /usr/sap/PSA/SUM/abap/exe and start profile : /usr/sap/PSA/SUM/abap/system/PSA/SYS/profile/PSA_DVEBMGS04_pmlsol 1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using ouput file: /usr/sap/PSA/SUM/abap/log/SAPup.ECO 3 ETQ120 20180102073350: PID 27175 execute '~/exe/sapstartsrv pf=~/system/PSA/SYS/profile/PSA_DVEBMGS04_pmlsol -D', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3 ETQ122 20180102073350: PID 27175 exited with status 0 (time: 0.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using kernel exe release: 749 and kernel state: 0 1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using timeout: 300 and delay: 10 3 ETQ120 20180102073350: PID 27177 execute '~/exe/sapcontrol -prot NI_HTTP -host pmlsol -nr 04 -function WaitforServiceStarted 300 10', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3 ETQ122 20180102073350: PID 27177 exited with status 0 (time: 0.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1 ETQ399 SYSTEM MANAGER: Start all instances. 1 ETQ399 SYSTEM MANAGER: Calling getInstances. 1 ETQ399 SYSTEM MANAGER: found instance for action START : Instance Number: 04 1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTROL action START for instance 04 and host pmlsol. 1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 04 on host pmlsol. 2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 4 for used ports on host 'pmlsol'. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3204 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3304 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3604 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 3904 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 8104 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 30401 appears to be unused. 3 ETQ399 SYSTEM HEALTH MANAGER: Port 50419 appears to be unused. 1 ETQ399 SYSTEM HEALTH MANAGER: call test rfc. 4 ETQ399 Set RFC variables for shadow connect: 4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000' 1 ETQ359 RFC Login to: System="PSA", AsHost="pmlsol" Nr="04", Client="000", GwHost="pmlsol", GwService="sapgw04" 2EETQ231 RFC Login failed 1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist. 1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: pmlsol and instance: 04 3 ETQ120 20180102073350: PID 27180 execute '~/exe/sapcontrol -format script -prot NI_HTTP -host pmlsol -nr 04 -function GetProcessList', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3WETQ122 20180102073350: PID 27180 exited with status 4 (time: 0.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1 ETQ399 SYSTEM HEALTH MANAGER: System is down, go on with start action 1 ETQ399 SAPCONTROL MANAGER: StartSystem with host: pmlsol and instance: 04 3 ETQ120 20180102073350: PID 27183 execute '~/exe/sapcontrol -prot NI_HTTP -host pmlsol -nr 04 -function StartWait 300 10', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3WETQ122 20180102073431: PID 27183 exited with status 2 (time: 41.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1 ETQ399 SYSTEM MANAGER: SAPControl action START failed for instance 04 ('SAPCONTROL MANAGER: call (sapcontrol) failed with return code '-1' '). 1 ETQ399 SYSTEM MANAGER: CheckSystemStatus. 1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: pmlsol and instance: 04 3 ETQ120 20180102073431: PID 27726 execute '~/exe/sapcontrol -format script -prot NI_HTTP -host pmlsol -nr 04 -function GetProcessList', output written to '/usr/sap/PSA/SUM/abap/log/SAPup.ECO'. 3 ETQ122 20180102073431: PID 27726 exited with status 0 (time: 0.0/ 0.0/ 0.0/223MB real/usr/sys/maxmem) 1EETQ399 SYSTEM MANAGER: START of mandatory instance 04 on server pmlsol has failed 2EETQ399 Starting shadow instance failed 1EETQ399 Last error code set is: Shadow instance 1EETQ399Xcouldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process /usr/sap/PSA/SUM/abap/exe/sapcontrol exited with 2, see '/usr/sap/PSA/SUM/abap/log/SAPup.ECO' for details 1EETQ204 Upgrade phase "START_SHDI_FIRST" aborted with severe errors ("20180102073431")

devtrace.txt

devtrace.txt (104.2 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jan 02 at 07:24 AM

    Issue is resolved,

    1 Adjusted the kernel.shmmax and kernel.shmall as per to the sappfpar check pf=<shadow instance profile> recommendations in /etc/sysctl.conf file

    2. Stoped SUM

    3. Restart of Main Instance and server .

    4. Start of SUM.

    Regards.

    Add comment
    10|10000 characters needed characters exceeded