Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Objective

The purpose of this wiki is to help customers to identify the reasons why the diagnostics agent might not start, provide help in finding the correct logs and solutions for known cases.

We will be adding known cases as we resolve them

General Information

The Diagnostics agent is a Java system, therefore, to understand the reasons why it does not start, we should look for the JVM start up logs in the work folder of the agent: /usr/sap/<SID of the DAA>/SMDA<xx>/work. Someone troubleshooting an issue can order the files by change date, decreasing order, and then look for errors in each of them:

Here is a screenshot of the work folder, usually we can start looking the logs in a top-down order:

Known cases

If the issue you're facing is not directly listed here, refer to note 1858920 before opening an incident.

Case #1 - sapcpe_sapjvm_6 shows /sapjvm_6.lst" does not exist, 2, No such file or directory

The agent does not start. the log file sapcpe_sapjvm_6 will contain lines similar to this:

Trace level (profile): 1
*** ERROR: File-List "/usr/sap/DAA/SYS/exe/jvm/rs6000_64/sapjvm_6.1.064/sapjvm_6.lst" does not exist, 2, No such file or directory, [sapxxcpe.c:1467]
parameter "all" is also not defined. Exit.

Solution

This issue is described in note 1858920:

The \usr\sap\<DASID>\SYS\exe\jvm\<platform> directory is emptied on all platforms, as part of the installation procedure.

To resolve the issue, perform a re-installation with SWPM 1.0 SP4 or higher(preferably the latest version). Use the SWPM***.SAR installer. Do not use the 70SWPM***.SAR installer.

Case #2 - dev_smdagent shows NIECONN_BROKEN  

The dev_smdagent will contain lines similar to the below:

 

F  [Thr 18632] *** ERROR => SfEStartupError: SfCControlClient::SfCControlClient: NiBufReceive failed (rc = -6 NIECONN_BROKEN  [sfxxcli.hpp  332]
F  [Thr 18632] *** ERROR => Operation failed: SfEStartupError: NiBufReceive failed (rc = -6 NIECONN_BROKEN [sfxxmain.cpp 1186]
F  
F  ********************************************************************************
F  *** ERROR => Cannot connect to parent process.
F  ***
F  *** Please see section 'Java process initialization issues'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
F  
F  [Thr 18632] *** LOG => exiting (exitcode -21001, retcode 2).

There is, at least, one icman or sapwebdisp process running in the same server:

The cause is that theDiagnostics Agent connects to a port which is already in use by another application (administration port of an icman/sapwebdisp process running in the same server).

Solution

The solution is to configure the ICM(s) and/or (WDP(s) of each instance running in the same server to use a specific TCP port to avoid the conflict. This can be done by specifying an unique port for each process, using parameter icm/admin_port.

See KBA 2164002.

Case #3 - smdagentgroup.properties is corrupted, having 0KB.

  1. The Diagnostics Agents on-the-fly do not start. In the work folder, the log file "INSTSTAT" will contain the following errors:

    SHUTDWN_BY NO_MORE_CHILD_PROCESSES
    SHUTDWN_AT <timestamp>
    EXIT_TIME  <timestamp>
    EXIT_WITH  3 No more child processes

  2. In file sapstart.log you may find:

    Execute Post-Shutdown Commands
    ------------------------------
    (16387) Exiting with Return-Code 3. (No more child processes)

  3.  You will also notice that file smdagentgroup.properties is corrupted, having 0KB.

Solution 

  1. Stop the physical agent.
  2. Go to /usr/sap/<DAA folder>/SMDA<xx>/script.
  3. Run the command "smdsetup installer resetall".
  4. Restart the physical agent.

See KBA 2151975.

Case #4 - dev_smdagent shows 'Connection refused'

The dev_smdagent contain logs like the following:

F [Thr 140053856118528] Thu Jul  9 12:17:08 2015
F  [Thr 140053856118528] *** LOG => State changed from 3 (Running) to 23 (Disconnected).
F  [Thr 140053856118528] *** LOG    state real time: 0.376 CPU time: 0.020 sys, 0.400 usr
F  [Thr 140053856118528] *** LOG    total real time: 27.017 CPU time: 0.700 sys, 5.220 usr
F  [Thr 140053856118528]
F  [Thr 140053856118528] *** LOG => State changed from 23 (Disconnected) to 10 (Starting apps).
F  [Thr 140053856118528] *** LOG    state real time: 0.000 CPU time: 0.000 sys, 0.000 usr
F  [Thr 140053856118528] *** LOG    total real time: 27.018 CPU time: 0.700 sys, 5.220 usr
F  [Thr 140053856118528]
M
M [Thr 140053483230976] Thu Jul  9 12:17:15 2015
M  [Thr 140053483230976] ***LOG Q0I=> NiPConnect2: 10.93.83.39:3301: connect (111: Connection refused) [/bas/741_REL/src/base/ni/nixxi.cpp 3320]
M  [Thr 140053483230976] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 25/sock 66
    (SI_ECONN_REFUSE/111; I4; ST; 10.93.83.39:3301) [nixxi.cpp    3320]
 

You may not find errors in the other log files of the work folder, so, you may check if in the log folder, the latest changed file with name "SMDSystem*.log" or the "smdagent.trc" contain lines such as:

 

 

[Thread[ExDaemon:exmgmt:jobmgr_1,5,exmgmt:j...] Error      Exception occured when trigerring task for executor : exmpush in execution manager: Execution Manager[exmgmt:jobmgr] 1011980385 :
[...]
[EXCEPTION]
java.lang.IllegalThreadStateException
               at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:843)
               at java.lang.Thread.init(Thread.java:403)
               at java.lang.Thread.init(Thread.java:355)
               at java.lang.Thread.<init>(Thread.java:625)
               at com.sap.smd.server.exec.ExecThreadFactory.newThread(ExecThreadFactory.java:22)


Solution 

The solution is provided with a patch for the LM-SERVICE. Please refer to note 2124709.

Before proceeding with the deployment, pay attention to the general recommendations of SAP note 1483508.


Case #5 - dev_smdagent shows good bye (exitcode = -11112)

The Diagnostics Agent does not start.  In the dev_smdagent contains the following:

 

[Thr 8004] Thu Sep 03 06:03:34 2015
[Thr 8004] JLaunchIStartFunc: end of main method (rc = 0)
[Thr 5588] JLaunchIExitJava: exit hook is called (rc = -11112)
[Thr 5588] **********************************************************************
*** ERROR => The Java VM terminated with a non-zero exit code.
*** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
*** for additional information and trouble shooting.
**********************************************************************
[Thr 5588] JLaunchCloseProgram: good bye (exitcode = -11112)

Solution

This error is described in the Diagnostics Agent troubleshooting guide, and is caused by wrong credentials provided by the agent.

This guide is attached to note 1833501

To resolve this issue, please proceed as follows:

 

Before restarting the agent It is important to execute some checks about the J2EE user as follow:
1. Connect to the ABAP transaction SU01, to check if the J2EE user (SMD_ADMIN or SMD_AGT) is not locked and if the
Role assigned is compliant to SAP recommendations done in the “User Administration guide”.
2. Logon to the Agent administration tool with the J2EE user (SMD_ADMIN or SMD_AGT) to check that the logon module of
the Java stack works correctly.
3. Call the smdsetup to update only the credentials to be sure the password is up-to-date.
4. Restart the Diagnostic agent.

 

Case #6 - std_smdagent.out shows java.lang.OutOfMemoryError

In the std_smdagent.out, you find the following:

os::malloc: failed to malloc <bytes> bytes (errno 12).#
# A fatal error has been detected by SAP Java Virtual Machine:
#
# java.lang.OutOfMemoryError: requested 148928 bytes for Chunk::new - os::malloc. Out of swap space or heap resource limit exceeded (check with limits or ulimit)?

--------------------------------------------------------------------------------
stdout/stderr redirection
--------------------------------------------------------------------------------
node name : SMDAgent
host name : <host_name>
system name : DAA
system nr. : 97
started at : Sun Oct 18 15:46:41 2015

os::malloc: failed to malloc <bytes> bytes (errno 12).#
# A fatal error has been detected by SAP Java Virtual Machine:
#
# java.lang.OutOfMemoryError: requested <bytes> bytes for Chunk::new - os::malloc. Out of swap space or heap resource limit


Solution

 Refer to KBA 2608979.. 

Case #7 - dev_jstart shows cannot open file '/usr/sap/<DAA>/SMDA<xx>/smdagentgroup.properties' for input

The dev_jstart of the Diagnostics Agent shows the following error:
--------------------------------------------
I [Thr 47272926838944] MtxInit: 30002 0 2
F [Thr 47272926838944] *** CONFIG => Message Server client disabled.
F [Thr 47272926838944] *** CONFIG => Enqueue Server client disabled.
F [Thr 47272926838944] *** WARNING => SfCConfig::parseFile: cannot open file '/usr/sap/<DAA>/SMDA<xx>/smdagentgroup.properties' for input. [sfxxlib.hpp 3196]
F [Thr 47272926838944] *** WARNING => SfCInstanceManager::newState: unknown runMode ''. [sfxxinst.hpp 1217]
F [Thr 47272926838944] *** LOG => Starting run level 3.
F [Thr 47272926838944] *** LOG => Run level 3 completed.
F [Thr 47272926838944] *** LOG => Instance state is "All processes stopped" (STOPPED @ 0, INACTIVE).
F [Thr 47272926838944] *** LOG => exiting (exitcode 0, retcode 0).
--------------------------------------------

The root cause of the above error is that file smdagentgroup.properties does not exist in the mentioned location. When a Diagnostics Agent is configured as on-the-fly controller, the smdagent.properties is renamed to smdagentgroup.properties and the profile file is modified accordingly to reference it. If the SMDAgent instance profile refers to file smdagentgroup.properties but only the smdagent.properties exists, the SMDAgent cannot start.

 Solution

  • Firstly, check the SMDAgent installation, this problem might occur if there are more than one SMDAgent installed under the same SID, for example DAK/SMDA97 and DAK/SMDA98 and sharing the same profile folder. This kind of installation is not supported when using the SMDAgents on-the-fly feature. The SMDAgents on-the-fly WIKI provides information, note 1365123 also provides information. In case that  several Diagnostics Agents are installed on the same host and at least one of them is configured as on-the-fly, then ensure to use a distinct SID for each SMDAgent.

  • If it is not a SMDAgent installation issue as described above, then as workaround manually fix the SMDAgent profile to refer to the correct file. The steps below show how to do it:

1) Backup the SMDAgent profile 'SMD_SMDA<XX>_<hostname>'.

2) Fix the SMDAgent profile, change property 'jstartup/instance_properties' to refer to the 'smdagent.properties' file.
ACTUAL CONFIGURATION:
-----------------------------------
smd/agent/type = 710
jstartup/instance_properties=$(DIR_INSTANCE)/smdagentgroup.properties
Autostart = 1
-----------------------------------
FIXED CONFIGURATION:
-----------------------------------
smd/agent/type = 710
jstartup/instance_properties=$(DIR_INSTANCE)/smdagent.properties
Autostart = 1
-----------------------------------

3) Start the SMDAgent.


 

Case #8 - dev_jstart shows ERROR => SfCreateShm: Shm in use by process <XXXX>. [jsfxxshm_mt. <xxxx>]

 

The dev_jstart of the Diagnostics Agent shows the following error:
--------------------------------------------

I  [Thr 01] MtxInit: 30002 0 2
F  [Thr 01] *** ERROR => SfCreateShm: Shm in use by process 787224. [jsfxxshm_mt. 1277]
F  [Thr 01] *** ERROR => SfEStartupError: SfCInstanceManager::initShm: SfCreateShm failed (rc = 13 already in use)  [sfxxinst.hpp 406]
F  [Thr 01] *** ERROR => Operation failed: SfEStartupError: SfCInstanceManager::initShm: SfCreateShm failed (rc = 13 already in use)
[sfxxmain_mt. 1186]

F  ********************************************************************************
F  *** ERROR => Shared memory initialization failed.
F  ***
F  *** Please see section 'Instance initialization issues'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************

F  [Thr 01] *** LOG => exiting (exitcode -21001, retcode 2).


--------------------------------------------

The cause of this issue could be a zombie process that is holding the resource. 

Solution

Check what is the process ID mentioned in the error(highlighted in red above) doing in the Operational system level. It could likely be a process held by the Diagnostics Agent OS level user, <daa>adm.

If you can confirm that this is a process started by the <daa>adm user, or a not relevant process, you can kill it and start the Diagnostics Agent again.
Another possibility is to restart the OS.

See KBA 2367366.

Case #9 - "Starting Startup Agent sapstartsrv - FAIL: Timeout - Startup of Instance Service failed"

In this case, the work folder of the agent is not updated. You may try to start the agent with the command below:

startsap SMDA<XX>

It will fail and show the following message:

 

Starting Startup Agent sapstartsrv
FAIL: Timeout
Startup of Instance Service failed
See /home/dadadm/startsap_SMDA<XX>.log for details

 

 The mentioned file will not contain much information, like below:

17:27:57

Starting Startup Agent sapstartsrv

-----------------------------------------

17:29:58
Startup of Instance Service failed

-------------------------------------------

17:29:58
See /home/dadadm/startsap_SMDA98.log for details

To have more information about the error, the following must be done:

  1. Change the default.pfl of this agent, adding parameter service/trace = 2.

  2. Clean the agent work folder.

  3. Ensure that the agent process is not running, kill it if necessary.

  4. Restart the agent trying the 2 following commands:

    1. /usr/sap/DAD/SMDA<XX>/exe/sapstartsrv pf=/usr/sap/DAD/SYS/profile/DAD_SMDA<XX>_<host>
      ("<XX>" above is the agent instance)

    2. sapcontrol -nr <agent instance> -function RestartService

More details should be available in the sapstartsrv.log:

[Thr 01] GwMonSetGwhost: / >> localhost/sapgw98
[Thr 01] *** ERROR => JsfCloseShm: Static shared memory is not initialized. [jsfxxshm_mt. 2074]
[Thr 01] *** ERROR => SemRmMgt: Sema Mgt Table not init'd [semux0_mt.c 1749]
[Thr 01] ShmDelete2( 84 )
[Thr 01] *** ERROR => ShmDelete2(84): ShmAdm not present. [shmux0_mt.c 2883]
[Thr 01] ShmDelete2( 83 )

Solution

These errors are related to a shared memory issue. Follow KBA 2420245 to fix it.

Case #10 - Diagnostics Agent on Linux X86 SLES12 SPS2 fails with OutOfMemoryError

 

After install a Diagnostics Agents on Linux X86 SLES12 SPS2, the agent fails to start due to an out of memory error. The dev_smdagent shows the following:

F  [Thr 140317487847168] *** java.lang.OutOfMemoryError: unable to create new native thread (12 threads running, rlimit: STACK 8192k, CORE infinity, NPROC 257656, NOFILE 65535, AS infinity, DATA infinity , Memory: 4k page, physical 65978080k(41781260k free), swap 2103292k(2103292k free)  )

....

F  [Thr 140317487847168] *** ERROR => SfEStartupError: SfCSapVm::callMainMethod: : Cannot call method: static void com/sap/smd/agent/launcher/SMDAgentLauncher.main(String[])  [sfxxjvm.hpp  1409]
F  [Thr 140317487847168] *** ERROR => Java thread failed: SfEStartupError: : Cannot call method: static void com/sap/smd/agent/launcher/SMDAgentLauncher.main(String[])
 [sfxxjvm.hpp  1476]
F  
F Thu Apr  6 08:11:34 2017
F  
F  ********************************************************************************
F  *** ERROR => Cannot call main method in com/sap/smd/agent/launcher/SMDAgentLauncher.
F  ***
F  *** Please see section 'Java VM shared library issues'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
F  
F  [Thr 140317587146624] *** LOG => exiting (exitcode -21003, retcode 2).
M  [Thr 140317587146624] CCMS: alert/disable_j2ee_monitoring set. CCMS Monitoring of J2EE Engine switched off.

Solution

Refer to KBA 2456149.

Case #11 - Diagnostics Agent does not start - bad SAPLOCALHOST

The Diagnostics Agent does not start, the dev_jstart contains the following or similar error:

 

I [Thr 140086098384736] MtxInit: 30002 0 2
M [Thr 140086098384736] ***LOG Q0I=> NiIBindSocket: 172.19.193.252:0: bind (99: Cannot assign requested address) [nixxi.cpp 3740]
M [Thr 140086098384736] *** ERROR => NiIBindSocket: SiBind failed for hdl 25/sock 9 (SI_EADDR_NAVAIL/99; I4; ST; 172.19.193.252:0) [nixxi.cpp 3740]
M [Thr 140086098384736] *** ERROR => NiIMyAddrVerify: NiIListen failed ('vadblgg'; 172.19.193.252; rc=-16) [nixxi.cpp 8983]
F [Thr 140086098384736] *** ERROR => SfEStartupError: SfCMsClient::SfCMsClient: NiMyAddrCheck(vadblgg) failed (rc = -16 NIEMYHOST_VERIFY) - bad SAPLOCALHOST [sfxxmsc.hpp 482]
F [Thr 140086098384736] *** ERROR => Operation failed: SfEStartupError: SfCMsClient::SfCMsClient: NiMyAddrCheck(vadblgg) failed (rc = -16 NIEMYHOST_VERIFY) - bad SAPLOCALHOST [sfxxmain_mt. 1173]
F
F
********************************************************************************
F *** ERROR => Shared memory initialization failed.
F ***
F *** Please see section 'Instance initialization issues'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F
********************************************************************************
F
F [Thr 140086098384736] *** LOG => exiting (exitcode -21001, retcode 2).

Solution

Refer to KBA 2477602.

 

Case #12 - Diagnostics Agent does not due to SAPStartSrv issue

The SMDAgent does not start, in the Diagnostics Agents 'work' folder only the files 'available.log' and 'sapstartsrv.log' are updated.

Solution

Refer to KBA 2501764.

Case #13 - Diagnostics Agent does not start due to error 'Cannot connect to Message Server' in dev_jstart

The Diagnostics Agents does not start correctly and the dev_jstart shows the error:

F Fri <timestamp>
F  ********************************************************************************
F  Java environment properties (/usr/sap/DAA/SMDA98/work/jstart.jvm)
F    root directory    : /usr/sap/DAA/SMDA98/exe/sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_101
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.083 25.51-b02
F    jvm library name  : libjvm.so
F    library path      : /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/amd64/server:/usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/amd64
F    executable path   : /usr/sap/DAA/SMDA98/exe/sapjvm_6/bin
F  ********************************************************************************
F    SAP extensions    : available
F  ********************************************************************************
I  [Thr 139776594798464] MtxInit: 30002 0 2
F  [Thr 139776594798464] *** WARNING => connection to Message Server not possible (j2ee/ms/host = , j2ee/ms/port = 36). [sfxxmsc.hpp  531]
F  [Thr 139776594798464] *** WARNING => connection to Enqueue Server not possible (j2ee/enq/host = , j2ee/enq/port = 32). [sfxxenc.hpp  194]
F  [Thr 139776594798464] *** LOG => Run level 0 completed.
F  [Thr 139776594798464] *** LOG => Instance state is "Instance terminated" (STOPPED @ 0, INACTIVE).
F  
F  ********************************************************************************
F  *** ERROR => Cannot connect to Message Server.
F  ***
F  *** Please see section 'Instance initialization issues'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
F  
F  [Thr 139776594798464] *** LOG => exiting (exitcode -21000, retcode 2).

Solution

Refer to KBA 2501871.

Case #14 - Diagnostics Agent does not start with a timeout

The Diagnostic Agent does not start with a timeout error:


Also, it is possible to find this error in the dev_jstart.log under the Agent's work folder:

F [Thr 01] Mon Jul 24 15:28:58 2017

F  [Thr 01] *** WARNING => SfCJavaProcHandler(smdagent)::onTimer: connect from smdagent timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1288]

F  [Thr 01] *** LOG => Send SIGINT to SMDAgent (pid 40894548).

F  [Thr 01] *** LOG => Process smdagent stopping (pid 40894548).

F  [Thr 01] *** LOG => Signal 20 SIGCHLD.

F  [Thr 01] *** WARNING => process SMDAgent (pid 40894548) killed (signal 2). [sfuxlib.hpp  852]

F  [Thr 01] *** LOG => Process smdagent stopped (pid 40894548).

F  [Thr 01] *** WARNING => Node smdagent failed: result 1, exit code 131074. [sfxxnode.hpp 1034]

Solution

Refer to KBA 2513385

Case #15 - Diagnostics Agent does not start with 'Signal 20 SIGCHLD' error message in the jvm_smdagent.log


You try to start the Agent and it does not start. It is possible to see this error message in the jvm_smdagent.log under the work folder:

F  [Thr 3001EE00:00000001] *** LOG => Signal 20 SIGCHLD.
F  [Thr 3001EE00:00000001] *** LOG => Process smdagent stopped (pid XXXXXX).
F  [Thr 3001EE00:00000001] *** LOG => Run level 3 completed.
F  [Thr 3001EE00:00000001] *** LOG => Instance state is "Instance terminated" (STOPPED @ 0, INACTIVE).
F  [Thr 3001EE00:00000001] *** LOG => exiting (exitcode 0, retcode 0).

Solution

Refer to KBA 2474618

Case #16 - Diagnostics Agent does not Start with 'This patch level of the Startup Framework 720 has not been released for OS' error message in dev_jstart.new

The Diagnostics Agent does not start due to the folloing error message in the dev_jstart.new log file.

 

M *** This patch level of the Startup Framework 720
M *** has not been released for OS releaseLinux 1.2.34-56.78-default #1 SMP Thu Jul 4th 12:00:00 UTC 1776 (d11a83a) x86_64. "

 

Solution 1

Upgrade the SAP Kernel used by the agent. This can be done as described at SAP Note 1707141. According to the Product Availability Matrix the following Kernel versions are generally supported (see SAP Note 1858920): 7.21, 7.22, 7.45, 7.49. For kernel downloads go to https://launchpad.support.sap.com/#/softwarecenter , select the 'Installation and Upgrades' tab -> 'By Alphabetical Index' -> 'K' -> 'SAP KERNEL 64-BIT UNICODE' -> select the kernel -> 'INSTALLATION' -> Download.  

Solution 2

As upgrading the kernel is not recommeded, comletely reinstalling the Diagnostics Agent using the correct SAP Kernel might also be an option. Therefore, follow SAP Note 1858920

Case #17 - Diagnostics Agent does not start with 'java.lang.NoClassDefFoundError: iaik/utils/Base64InputStream' in the dev_smdagent.log

In the log of the diagnostic agent dev_smdagent.log you find the following issue :

F [Thr 140011446728448] *** java.lang.NoClassDefFoundError: iaik/utils/Base64InputStream
F [Thr 140011446728448] *** at com.sap.smd.agent.security.SecureStorage.getSecureStore(SecureStorage.java:23)
F [Thr 140011446728448] *** at com.sap.smd.agent.security.SecureStorage.getAgentSecureStore(SecureStorage.java:65)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.sld.SLDConfigurationLoader.getSLDCredentials(SLDConfigurationLoader.java:262)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.sld.SLDConfigurationLoader.loadBasisProperties(SLDConfigurationLoader.java:113)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.sld.SLDConfigurationLoader.init(SLDConfigurationLoader.java:71)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.sld.SLDConfigurationLoader.<init>(SLDConfigurationLoader.java:63)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.sld.SLDQueryBuilder.<init>(SLDQueryBuilder.java:73)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.sld.SLDQueryBuilder.getInstance(SLDQueryBuilder.java:109)
F [Thr 140011446728448] *** at com.sap.smd.agent.connection.SMDConnector.<init>(SMDConnector.java:435)
F [Thr 140011446728448] *** at com.sap.smd.agent.SMDAgent.initConnector(SMDAgent.java:282)
F [Thr 140011446728448] *** at com.sap.smd.agent.SMDAgent.run(SMDAgent.java:237)
F [Thr 140011446728448] *** at com.sap.smd.agent.launcher.SMDAgentLauncher.launchAgent(SMDAgentLauncher.java:201)
F [Thr 140011446728448] *** at com.sap.smd.agent.launcher.SMDAgentLauncher.main(SMDAgentLauncher.java:76)
F [Thr 140011446728448] *** Caused by: java.lang.ClassNotFoundException: iaik.utils.Base64InputStream
F [Thr 140011446728448] *** at com.sap.smd.agent.loader.FileClassLoader.findClass(FileClassLoader.java:789)
F [Thr 140011446728448] *** at com.sap.smd.agent.loader.FileClassLoader.loadClass(FileClassLoader.java:684)
F [Thr 140011446728448] *** at com.sap.smd.agent.loader.FileClassLoader.loadClass(FileClassLoader.java:668)
F [Thr 140011446728448] *** ... 13 more
F [Thr 140011446728448] *** ERROR => SfEStartupError: SfCSapVm::callMainMethod: : Cannot call method: static void com/sap/smd/agent/launcher/SMDAgentLauncher.main(String[]) [sfxxjvm.hpp 1409]
F [Thr 140011446728448] *** ERROR => Java thread failed: SfEStartupError: : Cannot call method: static void com/sap/smd/agent/launcher/SMDAgentLauncher.main(String[])

Solution

Refer to KBA 2058923 - NoClassDefFoundError: iaik/utils/Base64Exception 

Case #18 - Diagnostics Agent fails to start - native thread creation failed ( returned error code 11)

It's not possible to start the agent and at  std_smgagent.out you can see the following error:

OS: [15944] 10:03:21 ***Warning: pthread_create failed (11, Resource temporarily unavailable) : [15944] 10:03:21 ***ERROR (:0): Native thread creation failed: native thread creation failed (returned error code 11): EAGAIN OS: [16201] 10:03:21 ***Warning: pthread_create failed (11, Resource temporarily unavailable) : [16201] 10:03:21 ***ERROR (:0): Native thread creation failed: native thread creation failed (returned error code 11): EAGAIN # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (malloc) failed to allocate 373840 bytes for Chunk::new. Out of swap space or heap resource limit exceeded (check with limits or ulimit)? # An error report with more information is generated, # it is saved as a file at this location: # /usr/sap/DAA/SMDA97/SMDAgent/hs_err_pid24313904.log [thread 4370 also had an error (0xb) Details: pc=0x090000000dd4f6d0 siginfo: si_signo: 11 (SIGSEGV), si_code: 51 (SEGV_ACCERR), si_addr: 0x00000000000000a0 ]

Solution

Refer to KBA 2608979


Case #19 - Diagnostics Agent does not start with 'cannot find jc.sapDXX_SMDAXX' error message in the dev_jstart.log

It's not possible to start the agent and at  dev_jstart.log you can see the following error:

 ERROR => Initialization failed: SfEStartupError: SfGetProgramPath: cannot find jc.sapDXX_SMDAXX on path '/usr/sap/DXX/SMDAXX/exe:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/daaadm/.local/bin:/home/daaadm/bin'.
[sfxxmain.cpp 1018]

[Thr 139865820075904] *** LOG => exiting (exitcode -21000, retcode 2).

Solution

Refer to KBA 1924672 - Java system does not start due to "cannot find jc.sap" error

Case #20 - Diagnostics Agent does not start with 'Cannot find class: com/sap/smd/agent/launcher/SMDAgentLauncher' error message in the dev_smdagent.log

It's not possible to start the agent and at  dev_smdagent.log you can see the following error:

*** WARNING => SfCJavaVm::callStatic: Cannot find class: com/sap/smd/agent/launcher/SMDAgentLauncher[sfxxjvm.hpp 676]
*** java.lang.NoClassDefFoundError: com/sap/smd/agent/launcher/SMDAgentLauncher
*** Caused by: java.lang.ClassNotFoundException: com.sap.smd.agent.launcher.SMDAgentLauncher
*** at java.net.URLClassLoader$1.run(URLClassLoader.java:253)
*** at java.security.AccessController.doPrivileged(Native Method)
*** at java.net.URLClassLoader.findClass(URLClassLoader.java:241)
*** at java.lang.ClassLoader.loadClass(ClassLoader.java:376)
*** at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:344)
*** at java.lang.ClassLoader.loadClass(ClassLoader.java:317)
*** ERROR => SfEStartupError: SfCSapVm::callMainMethod: : Cannot call method: static void com/sap/smd/agent/launcher/SMDAgentLauncher.main(String[]) [sfxxjvm.hpp 1409]
*** ERROR => Java thread failed: SfEStartupError: : Cannot call method: static void com/sap/smd/agent/launcher/SMDAgentLauncher.main(String[])

Solution

Refer to KBA 2585884 - Diagnostics Agent does not start: Cannot find class: com/sap/smd/agent/launcher/SMDAgentLauncher



 

 

 

 

 

 

 

 

 





 

  • No labels