Diagnostics Agent Installation Warnings - but installation finishes success

[Former Member]

Hi

I have written earlier about the Diagnostics Agent crashes within 5-10 mins after the startup, but I could not find a relevant solution from forums as well as from SAP.

So decided to reinstall DAA again today. this is the 4th time I am reinstalling it, (one of my colleague has did it more than 5 times without success).

our OS is HP UX 11.31, diagnostics agent 7.11, jce_policy used is jce_policy-1_5_0.zip

in between I got the below error messages

INFO 2010-11-19 15:35:22.137

Creating file /usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2.

INFO 2010-11-19 15:35:22.217

Effective group id set to 106.

INFO 2010-11-19 15:35:22.687

Working directory changed to /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST.

INFO 2010-11-19 15:35:23.87

Execute step registerLoggingDirectories of component |NW_DiagnosticsAgent|ind|ind|ind|ind|0|0|NW_DiagnosticsAgent_Instance|ind|ind|ind|ind|6|

0|NW_Instance|ind|ind|ind|ind|0|0

INFO 2010-11-19 15:35:24.27

Working directory changed to /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST.

INFO 2010-11-19 15:35:24.397

Execute step stopInstance of component |NW_DiagnosticsAgent|ind|ind|ind|ind|0|0|NW_DiagnosticsAgent_Instance|ind|ind|ind|ind|6|0|NW_Instance|

ind|ind|ind|ind|0|0

INFO 2010-11-19 15:35:25.337

Creating file /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST/sapcontrol_DAA_SMDA97.log.

INFO 2010-11-19 15:35:25.417

Output of /usr/sap/DAA/SYS/exe/uc/hpia64/sapcontrol -prot NI_HTTP -nr 97 -host kgsand2 -function GetInstanceProperties is written to the logf

ile sapcontrol_DAA_SMDA97.log.

WARNING 2010-11-19 15:36:16.620

Execution of the command "/usr/sap/DAA/SYS/exe/uc/hpia64/sapcontrol -prot NI_HTTP -nr 97 -host kgsand2 -function GetInstanceProperties" finis

hed with return code 1. Output:

19.11.2010 15:36:16

GetInstanceProperties

FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()

INFO 2010-11-19 15:36:16.850

Account daaadm already exists.

INFO 2010-11-19 15:36:16.870

Account 0 already exists.

INFO 2010-11-19 15:36:16.880

Account 107 already exists.

..

..

..

19.11.2010 15:58:06

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

jstart, J2EE Server, YELLOW, Starting the processes, 2010 11 19 15:55:21, 0:02:45, 5478

INFO 2010-11-19 15:58:06.722

CJSlibModule::writeInfo_impl()

Node sapcontrol_DAA_SMDA97.log already exists.

INFO 2010-11-19 15:58:06.782 [syuxccuren.cpp:1068]

CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath & /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST)

lib=syslib module=syslib

Working directory changed to /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST.

INFO 2010-11-19 15:58:06.792

CJSlibModule::writeInfo_impl()

Output of /usr/sap/DAA/SMDA97/exe/sapcontrol -prot NI_HTTP -nr 97 -host kgsand2 -function GetProcessList is written to the logfile sapcontrol_DAA_SMDA97.log.

WARNING 2010-11-19 15:58:57.645

CJSlibModule::writeWarning_impl()

Execution of the command "/usr/sap/DAA/SMDA97/exe/sapcontrol -prot NI_HTTP -nr 97 -host kgsand2 -function GetProcessList" finished with return code 4. Output:

..

.

.

.

.

WARNING 2010-11-19 16:00:52.960 [iaxxejshlp.cpp:150]

Could not get property IDs of the JavaScript object.

ERROR 2010-11-19 16:00:52.960 [iaxxejsctl.cpp:492]

FJS-00010 Could not get value for property .

When I check the installation with the below command is says successful without any error message

./smdsetup supportlogs

Can anyone help?

Thanks

Senthil

[Former Member]

Hi Senthil,

First we need to uninstall the Diagnois agent propely including the OS users.

then try to install it with the different SID.

By default solution manager installs the Diagnosis agent.Please ensure that only one diagnosis agent runs per system.

Regards,

Venkat.

[TomCenens]

Dear Senthil

It's best you use the latest available SAPJVM SAR package and appoint that to be directly installed in the SAPInst installation for your agent (to avoid issue with SAPJVM version from installation DVD of Diagnostics Agent 7.11).

It shouldn't be a problem that the os user already exists, in fact you shouldn't get the screen in SAPinst in that case to create the os users.

To reinstall the same SID (diagnostics agent) I would just delete the content out of it's filesystem and clear the existing entry out of /usr/sap/sapservices if it exists. That should be sufficient to restart installation.

KInd regards

Tom

[Former Member]

Tom

I tried with the latest SAPJVM, but no luck. SAP also could not fix the issue, they have asked me to install 720 version, which I did but still the DAA stops after 5 mins.

I found the below warning message in the smd_checkPrerequisiteSetup.log file during the installation.

Nov 23, 2010 11:26:22 AM [1290529582250]:Warning : Thread[main,5,main] com.sap.engine.services.rmi_p4: com

.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getClassLoader MSG:iaik.protocol.https.HttpsURLStreamHandlerFactory

java.lang.ClassNotFoundException: iaik.protocol.https.HttpsURLStreamHandlerFactory

at java.net.URLClassLoader$1.run(URLClassLoader.java:261)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:249)

at java.lang.ClassLoader.loadClass(ClassLoader.java:362)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:319)

at java.lang.ClassLoader.loadClass(ClassLoader.java:307)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:169)

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getClassLoader(P4ObjectBrokerClientImpl.java:602)

at com.sap.engine.services.rmi_p4.P4ObjectBroker.narrow(P4ObjectBroker.java:530)

at com.sap.engine.services.rmi_p4.MarshalInputStream.resolveObject(MarshalInputStream.java:174)

at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1377)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

at com.sap.engine.services.security.remote.RemoteSecurity_Stub.getRemoteLoginContext(RemoteSecurity_Stub.java:660)

at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:28)

at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)

at javax.naming.InitialContext.init(InitialContext.java:223)

at javax.naming.InitialContext.<init>(InitialContext.java:197)

at com.sap.smd.setup.tasks.agent.configuration.check.CheckConfigurationMonitoringData.checkP4Connection(CheckConfigurationMonitoringD

ata.java:323)

at com.sap.smd.setup.tasks.agent.configuration.check.CheckConfigurationMonitoringData.executeTasks(CheckConfigurationMonitoringData.j

ava:161)

at com.sap.smd.setup.tasks.agent.configuration.check.CheckConfigurationMonitoringData.main(CheckConfigurationMonitoringData.java:76)

Nov 23, 2010 11:26:22 AM [1290529582250]:Warning : Thread[main,5,main] com.sap.engine.services.rmi_p4: com

.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.construktor MSG: Cannot Load/set : iaik.protocol.https.HttpsURLStreamHandlerFactory <>

iaik.protocol.https.HttpsURLStreamHandlerFactory

Whether is this a relevant error message?

Thanks

Senthil

[TomCenens]

Hello Senthil

I doubt it.

You should check if the "stopping" comes from the fact that there is a technical issue or that there is a connection problem.

Can you check the log file jvm_smdagent.out in /usr/sap/<SID>/SMDA<instance number>/work

The logs in the work directory concern the actual vm startup, the agent connection and so on.

It should contain lines like either

ms://<hostname solution manager>:81<instance number>/P4 Agent ready.

Initialization Done

or

p4://<hostname solution manager>:5<instance number>04 Agent ready.

Initialization Done

Perhaps give me the log file names of the last 5 where the system has written into (of the work filesystem) so I have an idea what is being used logging wise.

Now also check the SMDSystem log file in /usr/sap/<SID>/SMDA<instance number>/SMDAgent/log

You should only find some lines with "Info" in this logfile is your agent is working properly.

In the same filesystem you could also find SMDAgentApplication log files in which you will get exceptions if your agent RFC (bad user/pass often) is not working properly.

Kind regards

Tom

[Former Member]

>

> Hello Senthil

>

> I doubt it.

>

> You should check if the "stopping" comes from the fact that there is a technical issue or that there is a connection problem.

>

> Can you check the log file jvm_smdagent.out in /usr/sap/<SID>/SMDA<instance number>/work

> The logs in the work directory concern the actual vm startup, the agent connection and so on.

>

> It should contain lines like either

> ms://<hostname solution manager>:81<instance number>/P4 Agent ready.

> Initialization Done

>

> or

>

> p4://<hostname solution manager>:5<instance number>04 Agent ready.

> Initialization Done

>

> Perhaps give me the log file names of the last 5 where the system has written into (of the work filesystem) so I have an idea what is being used logging wise.

>

> Now also check the SMDSystem log file in /usr/sap/<SID>/SMDA<instance number>/SMDAgent/log

>

> You should only find some lines with "Info" in this logfile is your agent is working properly.

>

> In the same filesystem you could also find SMDAgentApplication log files in which you will get exceptions if your agent RFC (bad user/pass often) is not working properly.

>

> Kind regards

>

> Tom

Tom,

SAP says that

:jstart launches successfully the process smdagent

smdagent was not able to get the secure communication key from

shared memory to open the static connection between both processes.

jstart stopped smdagent because it is assumed to be a fake.

Next steps:

please increase the trace by setting the following parameter in

instance profile and restart the instance

rdsip/TRACE=3"

Given below is the logs files, please let me know if you need any specific files,

*[/usr/sap/DAA/SMDA97/work]*
*(kgsand2)#cat std_flightrec.out*
*--------------------------------------------------------------------------------*
*stdout/stderr redirection*
*--------------------------------------------------------------------------------*
*node name   : collector*
*host name   : kgsand2*
*system name : DAA*
*system nr.  : 97*
*started at  : Mon Nov 29 09:46:42 2010*

*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.*
*/usr/sap/DAA/SMDA97/exe/jstart=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.*



*dev_jstart log file*

*F [Thr 01] Mon Nov 29 09:49:12 2010*
*F  [Thr 01] *** WARNING => SfCJavaProcHandler(flightrec)::onTimer: connect from flightrec timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1286]*
*F  [Thr 01] *** LOG => Send SIGINT to collector (pid 748).*
*F  [Thr 01] *** LOG => Process flightrec stopping (pid 748).*
*F  [Thr 01] *** LOG => Signal 18 SIGCHLD.*
*F  [Thr 01] *** WARNING => process collector (pid 748) killed (signal 2). [sfuxlib.hpp  836]*
*F  [Thr 01] *** LOG => Process flightrec stopped (pid 748).*
*F  *********************************************************************************
*F  Starting process: /usr/sap/DAA/SMDA97/exe/jstart*
*F    arg[ 1] = -nodeId=0*
*F    arg[ 2] = pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2*
*F    arg[ 3] = -hostvm*
*F    arg[ 4] = -nodeName=smdagent*
*F    arg[ 5] = -file=/usr/sap/DAA/SMDA97/SMDAgent/smdagent.properties*
*F    arg[ 6] = -jvmFile=/usr/sap/DAA/SMDA97/work/jstart.jvm*
*F    arg[ 7] = -traceFile=/usr/sap/DAA/SMDA97/work/dev_smdagent*
*F    arg[ 8] = -javaOutFile=/usr/sap/DAA/SMDA97/work/jvm_smdagent.out*
*F    env   : LD_PRELOAD=libjvm.so*
*F  exePath : PATH=/usr/sap/DAA/SMDA97/exe/sapjvm_6/bin:/usr/sap/DAA/SMDA97/exe:.:/home/daaadm:/usr/sap/DAA/SYS/exe/run:/usr/sap/DAA/SYS/exe/uc/hpia64:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/gvsd/bin:/opt/ipf/bin:/opt/nettladm/bin:/opt/fcms/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/sas/bin:/opt/graphics/common/bin:/opt/atok/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/sec_mgmt/bastille/bin:/opt/caliper/bin:/opt/drd/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/resmon/bin:/opt/firefox:/opt/gnome/bin:/opt/perf/bin:/opt/propplus/bin:/usr/contrib/kwdb/bin:/opt/perl_32/bin:/opt/perl_64/bin:/opt/prm/bin:/opt/sfm/bin:/opt/swm/bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/swa/bin:/opt/hpsmh/bin:/opt/thunderbird:/opt/sentinel/bin:/opt/langtools/bin:/opt/wlm/bin:/opt/gwlm/bin:/opt/ignite/bin*
*F  libPath : LD_LIBRARY_PATH=/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ia64/server:/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ia64:/usr/sap/DAA/SMDA97/j2ee/os_libs:/usr/sap/DAA/SMDA97/exe*
*F  stdout  : /usr/sap/DAA/SMDA97/work/std_smdagent.out*
*F  stderr  : /usr/sap/DAA/SMDA97/work/std_smdagent.out*
*F  console : no*
*F  debugger: no*
*F  nice    : no*
*F  *********************************************************************************
*F  Process SMDAgent started with pid 750*
*F  *********************************************************************************
*F  [Thr 01] *** LOG => Process smdagent started (pid 750).*
*F*
*F [Thr 01] Mon Nov 29 09:49:42 2010*
*F  [Thr 01] *** WARNING => SfCJavaProcHandler(smdagent)::onTimer: connect from smdagent timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1286]*
*F  [Thr 01] *** LOG => Send SIGINT to SMDAgent (pid 750).*
*F  [Thr 01] *** LOG => Process smdagent stopping (pid 750).*
*F  [Thr 01] *** LOG => Signal 18 SIGCHLD.*
*F  [Thr 01] *** WARNING => process SMDAgent (pid 750) killed (signal 2). [sfuxlib.hpp  836]*
*F  [Thr 01] *** LOG => Process smdagent stopped (pid 750).*
*F  [Thr 01] *** WARNING => Node smdagent failed: result 1, exit code 2. [sfxxnode.hpp 1022]*
*F  *********************************************************************************
*F  Starting process: /usr/sap/DAA/SMDA97/exe/jstart*
*F    arg[ 1] = -nodeId=1000*
*F    arg[ 2] = pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2*
*F    arg[ 3] = -DSAPINFO=DAA_97_flightrec*
*F    arg[ 4] = -hostvm*
*F    arg[ 5] = -nodeName=flightrec*
*F    arg[ 6] = -file=/usr/sap/DAA/SMDA97/exe/startup.properties*
*F    arg[ 7] = -jvmFile=/usr/sap/DAA/SMDA97/work/jstart.jvm*
*F    arg[ 8] = -traceFile=/usr/sap/DAA/SMDA97/work/dev_flightrec*
*F    arg[ 9] = -javaOutFile=/usr/sap/DAA/SMDA97/work/jvm_flightrec.out*
*F    arg[10] = -clusterId=smdagent*
*F    arg[11] = -exitcode*
*F    arg[12] = 2*
*F    env   : LD_PRELOAD=libjvm.so*
*F  exePath : PATH=/usr/sap/DAA/SMDA97/exe/sapjvm_6/bin:/usr/sap/DAA/SMDA97/exe:.:/home/daaadm:/usr/sap/DAA/SYS/exe/run:/usr/sap/DAA/SYS/exe/uc/hpia64:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/gvsd/bin:/opt/ipf/bin:/opt/nettladm/bin:/opt/fcms/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/sas/bin:/opt/graphics/common/bin:/opt/atok/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/sec_mgmt/bastille/bin:/opt/caliper/bin:/opt/drd/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/resmon/bin:/opt/firefox:/opt/gnome/bin:/opt/perf/bin:/opt/propplus/bin:/usr/contrib/kwdb/bin:/opt/perl_32/bin:/opt/perl_64/bin:/opt/prm/bin:/opt/sfm/bin:/opt/swm/bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/swa/bin:/opt/hpsmh/bin:/opt/thunderbird:/opt/sentinel/bin:/opt/langtools/bin:/opt/wlm/bin:/opt/gwlm/bin:/opt/ignite/bin*
*F  libPath : LD_LIBRARY_PATH=/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ia64/server:/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ia64:/usr/sap/DAA/SMDA97/j2ee/os_libs:/usr/sap/DAA/SMDA97/exe*
*F  stdout  : /usr/sap/DAA/SMDA97/work/std_flightrec.out*
*F  stderr  : /usr/sap/DAA/SMDA97/work/std_flightrec.out*
*F  console : no*
*F  debugger: no*
*F  nice    : no*
*F  *********************************************************************************
*F  Process collector started with pid 757*
*F  *********************************************************************************
*F  [Thr 01] *** LOG => Process flightrec started (pid 757).*
*F*
*F [Thr 01] Mon Nov 29 09:50:12 2010*
*F  [Thr 01] *** WARNING => SfCJavaProcHandler(flightrec)::onTimer: connect from flightrec timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1286]*
*F  [Thr 01] *** LOG => Send SIGINT to collector (pid 757).*
*F  [Thr 01] *** LOG => Process flightrec stopping (pid 757).*
*F  [Thr 01] *** LOG => Signal 18 SIGCHLD.*
*F  [Thr 01] *** WARNING => process collector (pid 757) killed (signal 2). [sfuxlib.hpp  836]*
*F  [Thr 01] *** LOG => Process flightrec stopped (pid 757).*
*F  [Thr 01] *** LOG => Instance state is "Stopping the processes" (STOPPING @ 0, INACTIVE).*
*F  [Thr 01] *** LOG => Run level 3 completed.*
*F  [Thr 01] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).*
*F*
*F  *********************************************************************************
*F  *** ERROR => Node 'smdagent' failed with exit code 2.*
*F  ****
*F  *** Please see section 'Other issues'*
*F  *** in SAP Note 1316652 for additional information and trouble shooting advice.*
*F  *********************************************************************************
*F*
*F  [Thr 01] *** LOG => exiting (exitcode 22002, retcode 1).*Regards
Senthil

Edited by: Senbala on Nov 29, 2010 4:55 PM

Edited by: Senbala on Nov 29, 2010 4:56 PM

[Former Member]

dev_jstart Logs

F  [Thr 01] SfCreateShm: ShmCreate(79, 4096, ATTACH) failed (rc = 3 SHM segment doesn't exist)... creating it.
F  [Thr 01] SfCreateShm: dynamic SHM protection is disabled.
M  [Thr 01] SemRel( 60, 1 ) enter
M  [Thr 01] SemRel( 60, 1 ) exit rtc=0, 0us
F  [Thr 01] SfCreateShm: static shm created ok at 0xc0000000004a2000
F  [Thr 01] JsfGetShmInstance: ok.

F  [Thr 01]         jstart/nodeFiles=$[$[$[jstart/startupNodeFile:ir]::? Cannot read $[jstart/startupNodeFile] file.]::+]$[jstart/startupNode
File]$[FILE_SEP]$[jstart/instanceNodeFiles]$[$[$[rdbg.proxy::@$[jstart/InstanceHome]]::id]::+$[FILE_SEP]$[dproxy.properties::@$[DIR_EXECUTABL
E]]]


F  [Thr 01]         elem/appTrcArg=$[$[elem/_nodeType]/appTrcArg:-$[jstart/appTrcArg]]
F  [Thr 01]         elem/checkedDebugPort=$[elem/debugPort:? Cannot activate $[elem/vmtool] without a debugPort.]
F  [Thr 01]         elem/collector=$[jstart/collector]
F  [Thr 01]         elem/connectTimeout=$[jstart/connectTimeout]
F  [Thr 01]         elem/console=$[jstart/startMode:~console]
F  [Thr 01]         elem/dbgBrkArg=$[$[elem/_nodeType]/dbgBrkArg:-$[jstart/dbgBrkArg]]


F  [Thr 01]         elem/traceVersions=$[jstart/traceVersions]
F  [Thr 01]         elem/vm/args=$[$[elem/type]/vm/args] $[_js/vmargs] $[elem/javaParameters] $[jstart/vm/args] $[_js/memargs] $[$[$[$[system
/type:~DS] $[$[elem/javaParameters] $[jstart/vm/args]::~!*-DSAPSTART=1*]::t]::? Setting -DSAPSTART=1 is only allowed for double stack systems
.]::+]
F  [Thr 01]         elem/vm/classPath=$[elem/classPath]
F  [Thr 01]         elem/vm/ignoreUnrecognized=$[jstart/vm/ignoreUnrecognized]