After applying SPS using SUM unable to start additional application instances

[Former Member]

Hello All,

We are on EP (Only Java) - NW 730 SPS 08. I have applied SPS to SPS12 using SUM tool (We are having total of 5 application instances - 1 CI + 4 additional application insatnce)

As part of last step in Execution phase, when tool tried starting all applications except CI other are not coming up

I tried manually starting them - In JCMON i see the bootstrap is in Stopped status, however dev_bootstrap log says that it successfully finished with RC 0

F  [Thr 140259627857664] *** LOG => SfCJavaVm: exit hook is called. (rc = 0)

F

F [Thr 140260318033760] Mon Jan 12 10:09:19 2015

F  [Thr 140260318033760] *** LOG => exiting (exitcode 0, retcode 0).

M  [Thr 140260318033760] CCMS: CCMS Monitoring Cleanup finished successfully.

i tried with option mentioned in note - 710663 - AS Java Bootstrap Synchronization. but with no luck

With no errors seen anywhere i am having a hard time to understand the issue

Could you guys please assist?

Thanks,

Subbu

[TomXing · Accepted solution]

Hi Subbu,

So you are near (but not reached) the end of upgrade process in SUM.

Does SUM complain about DIs that they can't start?

If so, it means SUM is really trying to start all instances (CI + DIs).

Then you can check in configtool and make sure all the instances are out of safe mode.

BR, Tom

[Former Member · Accepted solution]

Thank you very much Manu and Tom.

As Tom suspected, we do had the runMode="SAFE" which prevented the servers to start.

I have changed it to NORMAL which fixed the issue

I updated from 7.30.08 to 7.30.12 using SUM 1.0 SP 12 version.

The above issue had brought a doubt to my mind in the way i executed SUM:

Just before EXECUTION phase - DOWNTIME, SUM had never asked me to stop all DIs (When i did this on dual stack, i had been asked by SUM to stop all DIs - this is only JAVA stack Portal system)

Do we need to stop all DIs (Additional application server instances) before starting the Downtime?

Is this the reason SUM had never kept the runMode to NORMAL from SAFE?

Please clarify

Thanks,

Subbu

[TomXing · Accepted solution]

Hi Subbu,

First of all thanks for the update, and it's glad to hear the issue is gone.

As per my understanding, SUM should bring down all the instances during *downtime* automatically or at least prompt you to do so.

(But on the other hand - was SCS (supposed to be) running? If SCS is down, all DIs will be down soon.

If anything is still running - is that a 'downtime'?)

I reviewed the upgrade guide but I did not yet notice such requirement of manual stop/start of AAS (DI).

Not to mention switching SAFE Mode manually...

Could it be possible that you have a in-homogeneous landscape?

BR, Tom

[manumohandas82]

Hi Subbu ,

Please increase the bootstrap timeout parameter

(JSTSG)(Kernel)Bootstrap-Exit556 - Java Server Troubleshooting Guide - SCN Wiki

Also check the following SAP KBA

2067062 - AS Java fails to start due to exitcode 556

Thanks ,

Manu

[Former Member]

Hello All,

I just conmpared the dev_jstart file with the sever which started perfectly fine (Main instance), i see this line (F  [Thr 140119685568352] *** CONFIG => instance is disabled.) in addtion to the one which started perfectly fine:

Any suggestions where to check if the instance is disabled to start by SUM - not sure if SUM tool had skipped this step of enabling the instance

dev_jstart file:

F [Thr 140119685568352] Mon Jan 12 10:41:36 2015

F  [Thr 140119685568352] *** LOG => Process bootstrap running (pid 7164).

F  [Thr 140119685568352] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).

F

F [Thr 140119685568352] Mon Jan 12 10:41:45 2015

F  [Thr 140119685568352] *** LOG => Process bootstrap stopping (pid 7164).

F  [Thr 140119685568352] *** LOG => Signal 17 SIGCHLD.

F  [Thr 140119685568352] *** LOG => Process bootstrap stopped (pid 7164).

F  [Thr 140119685568352] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).

F  [Thr 140119685568352] *** LOG => Run level 2 completed.

F  [Thr 140119685568352] *** LOG => Starting run level 3.

F  [Thr 140119685568352] *** CONFIG => instance is disabled.

F  [Thr 140119685568352] *** LOG => Run level 3 completed.

F  [Thr 140119685568352] *** LOG => Instance state is "Synchronizing binaries" (STOPPED @ 0, INACTIVE).

Thanks,

Subbu