Originally posted by: DianeC

I've searched this forum & did not see an answer.

We are upgrading from WTX 8413 to ITX9003 and moving from AIX to Linux.    After deploying a system to Linux, when I attempted to start the launcher, I received an error message & can't seem to find documentation on it anywhere.  Does anyone know what a "result 127" means?  Any help is greatly appreciated.

List of deployment directories:

/edi/837/systems

Sep 27, 2018 1:02:41 PM.
Adding System 837_5010.msl; to list of systems.

Automatic Initial Start option is on.

Sep 27, 2018 1:02:41 PM
Recieved the request Start System for system 837_5010.msl;.

Sep 27, 2018 1:02:41 PM.
Command line for starting the system 837_5010.msl; is /edi/837/bin/launcher /edi/837/systems/837_5010.msl  -s8660,8661,8662  -d='/edi/837/logs/CompoundSystem-2018-09-27-13-02-41_lnxditx01.log' -L='/edi/837/logs/CompoundSystem-2018-09-27-13-02-41_lnxditx01.txt' -N='/edi/837/config/dtx.ini'.

Sep 27, 2018 1:02:41 PM
System 837_5010.msl; has stopped with result 127.

Sep 27, 2018 1:02:43 PM.
System "837_5010.msl;" may have crashed. Restarting the system.

Sep 27, 2018 1:02:43 PM.
Command line for starting the system 837_5010.msl; is /edi/837/bin/launcher /edi/837/systems/837_5010.msl  -s8660,8661,8662  -d='/edi/837/logs/CompoundSystem-2018-09-27-13-02-43_lnxditx01.log' -L='/edi/837/logs/CompoundSystem-2018-09-27-13-02-43_lnxditx01.txt' -N='/edi/837/config/dtx.ini'.

Sep 27, 2018 1:02:43 PM
System 837_5010.msl; has stopped with result 127.

Originally posted by: tomw

Hi,

we got a 139 and have opened a pmr with IBM.

look into install dir /tmp for abort and the .launcher xxxx dir for crash  may be of help. Also if you still have the 8.4 doc you that still as a reference

UNIX signal-generated codes in the Launcher log file

Hope this helps

Tom W

Originally posted by: PaulBrett

See also this:

https://www.ibm.com/support/knowledgecenter/SSVSD8_9.0.0/com.ibm.websphere.dtx.es.doc/references/r_event_server_LauncherLog.htm

The log generated by activating this setting will tell you so much more detail.

Thank you

Paul

Follow me on Twitter

Originally posted by: DianeC

Thanks Paul.  We do have that log turned on in the dtx.ini file.  There isn't any details in the log other than the launcher stopped with a result 127.

We are currently checking all paths to make sure that those exist & are available to the id being used.

Originally posted by: PaulBrett

In the log, you can see a line that starts with:

Command line for starting the system System2.msl; is ....

Everything after this bit, but before the final full stop (.) can be used to start the Launcher manually (outside of the Java Event Server wrapper process).

Example:

Command line for starting the system System2.msl; is /nfshome/pbrett/lnx64/wtx8412/bin/launcher /nfshome/pbrett/lnx64/wtx8412/systems/System2.msl  -s47100,47101,47102  -d='/nfshome/pbrett/lnx64/wtx8412/logs/CompoundSystem02-23-18-12-27-46-PM.log' -L='/nfshome/pbrett/lnx64/wtx8412/logs/CompoundSystem02-23-18-12-27-46-PM.txt' -N='/nfshome/pbrett/lnx64/wtx8412/config/dtx.ini'.

Command line would be:

/nfshome/pbrett/lnx64/wtx8412/bin/launcher /nfshome/pbrett/lnx64/wtx8412/systems/System2.msl  -s47100,47101,47102  -d='/nfshome/pbrett/lnx64/wtx8412/logs/CompoundSystem02-23-18-12-27-46-PM.log' -L='/nfshome/pbrett/lnx64/wtx8412/logs/CompoundSystem02-23-18-12-27-46-PM.txt' -N='/nfshome/pbrett/lnx64/wtx8412/config/dtx.ini'

Thank you

Paul

Follow me on Twitter

Starting the Launcher this way may give you more information.