Start of SMD agent fails!
Hi!
After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error Exception ID: 1160572286256
Registering agent on server myhost.de:50004failed:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
However, the manual setup of the agent succeeds:
./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
SMD Agent Setup is in process ...
- STEP 1: checking JDK location
JDK location is consistent: /usr/java14_64/bin
- STEP 2: checking JDK Version
JDK Version is correct: 1.4.2
- STEP 3: checking Connection to SMD Server
SMD Server check completed successfully
- STEP 4: generating Runtime Properties
runtime.properties has been created.
- STEP 5: generating Launcher
smdagent.bat has been created.
smdagent.sh has been created.
- STEP 6: generating SecStore
secstore.properties: has been created.
secstore.properties: user has been set.
secstore.properties generation completed successfully.
- STEP 7: checking P4 Connection and SMD Agent Registration
SMD Agent Registration succeeded
SMD Agent Setup completed successfully
During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
What can we do?
Thanks for all hints solving our problem!
Greetz,
André Richter
Hi Rahul,
please try SMD Agent 7.00 SP10! We had no problems with this version!
Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
Regards
André
Similar Messages
-
Urgent!! Setup of SMD Agent failed due to Remote Error....
I am getting the following error when i tried to Setup the Smd agent using setup wizard:
<b>The assignment of server frces4153 to SMD Agent failed
Remote error occurs during the connection to the smd agent for agent frces4153</b>
Can you please give me the solution for this...
<b>Reward points of all the replies....</b>
Ajay KandeThnx for ur suggestions, Now i colud see the following error "[Setup]Failed to assign SMD Agent to frces4146/EP7 (frces4146)
[EXCEPTION]
Time out occurred when calling method 'getService' on object [com.sap.smd.api.IAgentContext_Stub@7fc07fc] after 10000 ms.... [siehe Details]
from the logs....
Ajay Kande -
Manual Setup of SMD Agent failed
Hi gurus!!
I have already installed the SMDAgent into my monitored system (EP 7.0 on Windows) but when I execute the smdsetup.bat with the corresponding parameters the next error ocurred when it tries to create the secstore.properties file:
- STEP 6: generating SecStore
External Command Executed:
C:\j2sdk1.4.2_14\bin\java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp "lib/sapxmltoolkit.jar;lib/smdagent.jar;lib/tc_sec_secstorefs.jar;lib/iaik_jce_export.jar;lib/launcher/smdagentlauncher.jar;lib/launcher/logging.jar;lib/smdserver.jar;lib/exception.jar;lib/sapj2eeclient.jar" com.sap.security.core.server.secstorefs.SecStoreFS create -f K:\usr\sap\SMD\J98\SMDAgent\configuration\secstore.properties -k "" -noenc
secstore.properties: creation failed. exitcode= 1
java.lang.NoClassDefFoundError: com/sap/tc/logging/LogController
Exception in thread "main"
Now, I can see the agent from the server ../smd/admin in the Agent administration tab but the scheduler can't execute task because it says that is no agent connected or started.
Can anybody show me the way to solve this problem?
Thank you very much in advanced.
Edorta Ramos.Great thanks stephan, I had the same issue and this solves it!!
Just copy logging.jar from
x:\usr\sap\<SMD SID>\<instance>\SMDAgent\lib
to
x:\usr\sap\<SMD SID>\<instance>\SMDAgent\lib\launcher
and then re-execute the smdsetup.bat!
Regards,
Nico... -
SAP CPS - Starting SAP RFC-Agent fails
Dear Developers
I try to start an SAP RFC-Agent for a specific SAP instance (which is one of the test environments) and a client in a Redwood Cronacle Repository Version 7.0.3 which fails.
I get the following error message:
Redwood Cronacle for SAP Agent V7.0.3.0 Production build 20071219
(C) Copyright 1993-2007 Redwood Technology B.V., Houten, The Netherlands All rights reserved.
2009/07/22 10:26:43: Daemon start
Info: This SAP Agent can not be used to connect to SAP production systems
Info: This SAP Agent can not be used to connect to SAP production systems
Redwood Cronacle for SAP Agent V7.0.3.0 Production build 20071219
Stop at 2009/07/22 10:27:21
With the command "show license" in Redwood Shell rs I can see that there is a line which checks whether the SAP instance is productive or not ("Y SAP non-production"). I know this check is not there in Version 7.0.4 but at this point in time we cannot upgrade our whole platform.
I went to my inhouse SAP colleagues. They checked the definition for that SAP instance and that client. It is defined as test and not productive. Nevertheless the check in Redwood Cronacle brings back that it is a productive system.
Best regards,
StephanHi Stephan,
From your description you seem pretty sure that in your Test SAP Instance, having used transaction SCC4 the client role is configured as a non-production client? And I assume from SAP CPS the SAP connect string defined uses the same client and is definitely pointing to your Test SAP instance?
With regards to the license check not being there in 7.0.4 and not wanting to upgrade. You shouldn't need to. As I understand things the license key was included without considering/understanding the practical implications, e.g. how was a customer going to import thier existing Batch into a test CPS environment if they cannot initially connect to production!! And as you know was later removed again. All you need to do I believe is create an OSS message including you current license information and ask that a new key be generated that has the restriction removed. You should then be able to just apply the new license over the old. SAP should include the necessary instructions for applying the license.
Regards,
Simon -
Hello All,
In order to install Wily Introscope Agent, initially I have installed
a SMD Agent on managed system host.
After the installtion of SMD Agent , while starting the SMD agent I am getting below error .
Starting SMDAgent ...
Establishing connection to server '[host is empty]' on port [port is
empty]
Smd connector is disabled because no SLD association and no credentials
found.
Smd connector is disabled because no SLD association and no credentials
found.
Waiting for connection ...
Checking server availability...
Warning :
Connecting to SMD server null failed - error counter: 0 -
com.sap.engine.services.jndi.persistent.exceptions.NamingException: No
InitialContext can be created because the java.naming.provider.url
property is no specified in the jndi environment.
Next try to push instance data in SLD is Tue May 19 14:36:31 CDT 2009
I have given user SLDAPIUSER in SLDAPICUST transaction. This user
which is not locked and I have also reconfirmed the password of this
user.
Kindly request your suggestion!!!!
Regards,
SuhasSantosh Asuthkar
I am receiving the same error in my SMD agent log:
Starting SMDAgent ...
Dec 8, 2009 1:43:48 PM [Thread[main,5,main]] Info Establishing connection to server '[host is empty]' on port [port is empty]
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info [null] Waiting for connection ...
Dec 8, 2009 1:43:52 PM [Thread[SMDAgent connection thread,5,main]] Info [null] Checking server availability...
Dec 8, 2009 1:43:53 PM [Thread[SMDAgent connection thread,5,main]] Warning Connecting to SMD server null failed - error counter: 0 - com.sa
p.engine.services.jndi.persistent.exceptions.NamingException: No InitialContext can be created because the java.naming.provider.url property i
s no specified in the jndi environment.
Dec 8, 2009 1:43:54 PM [Thread[SLD-Registration,1,main]] Info [SLDReg] Next try to push instance data in SLD is Wed Dec 09 01:43:54 EST
2009
Dec 8, 2009 1:46:52 PM [Thread[SLD-AssocWatcher,1,main]] Info [SLDManagingConnectionMonitor] Next time to check Managing System Associat
ion is Tue Dec 08 14:01:52 EST 2009
Can you please provide details if you found a solution?
Thanks!!!!!
Jeff -
The SMD Agent 'server' hasn't been found
I've seen this question posted, but no answer provided. I'm trying to install Wily Introscope on a Java-only (Netweaver 7) system. The SMD software is installed and the agent is running. I can see in the log files that the Wily agent has connected to the management console.
I'm running EHP1 on the Solution Manager server.
When I go to Introscope Agent - Detailed Selection and select this server this message is displayed "Failed to connect to server: "server" - Please make sure SMD Agent is up and running"
When I attempt to run the Diagnostic Setup Wizard. I get the following message "the SMD Agent "server" hasn't been found"
1.) I've stopped and started the SMD agent on the client serveral times - Does not fix the problem
2.) I've restarted Solution Manager - does not fix problem
Any idea how to trouble shoot this issue?Thanks for pointing me in the right direction - here are the steps to resolve this issue.
In my case the problem was caused by dual entries in smsy for the server. I had the hostname and a DNS u2013 cname u2013 for the server in smsy. This was confusing Solution Manager.
1. Use SOLMAN_WORKCENTER
2. GoTo ROOT CAUSE ANALYSIS COMMON TASKS ADMINISTRATION AGENT ADMINISTRATION
a. Right-click on the server with the problem and select u201CRESET SERVER NAMEu201D
i. The SMD agent will be disassociated with the server. Restart the SMD agent on the server.
3. Steps to reassign the server name
a. Use SOLMAN_WORKCENTER
b. GoTo ROOT CAUSE ANALYSIS COMMON TASKS SETUP and CHECK DIAGNOSTIC SETUP DIAGNOSTIC SYSTEMS UPGRADER
i. Select the UPGRADE NOW button
c. Once the UPGRADER tasks completes
d. GoTo ROOT CAUSE ANALYSIS COMMON TASKS SETUP and CHECK DIAGNOSTIC SETUP MANAGED SYSTEMS SETUP WIZARD
i. Select the server
ii. Reassign the SMD agent to this server
1. The SMD agent will restart with the correct server name -
SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)
I am getting the following message when I start the agent. I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects. Just eventually times out after 30 mins.
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.cat dev_SMDAgent
trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
node name : smdagent
pid : 17393
system name : SMD
system nr. : 98
started at : Wed Oct 7 08:56:32 2009
arguments :
arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
arg[02] : -DSAPINFO=SMD_98_server
arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : /usr/sap/SMD/exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SMD/J98/profile/smd.properties
Instance properties
-> ms host :
-> ms port : 36
-> os libs : /usr/sap/SMD/exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] smdagent : /usr/sap/SMD/J98/profile/smd.properties
[Thr 182894174624] Wed Oct 7 08:56:32 2009
[Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
[Thr 182894174624] SigISetDefaultAction : default handling for signal 17
[Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182894174624] CPIC (version=701.2009.01.26)
[Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
Java Home: /opt/IBMJava2-amd64-142
[Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
JStartupIReadSection: read node properties [smdagent]
-> node name : SMDAgent
-> node type : server
-> node id : 1
-> node execute : yes
-> java path : /opt/IBMJava2-amd64-142
-> java parameters : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
-> java vm version : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
-> java vm vendor : IBM J9 VM (IBM Corporation)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 256M
-> init heap size : 256M
-> root path : ../SMDAgent
-> class path : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> OS libs path : /usr/sap/SMD/exe
-> main class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
-> parameters : run jcontrol
-> debuggable : yes
-> debug mode : no
-> debug port : 58981
-> shutdown timeout : 20000
[Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
[Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -DP4ClassLoad=P4Connection
-> arg[ 4]: -Xj9
-> arg[ 5]: -Xmn50m
-> arg[ 6]: -Xgcpolicy:gencon
-> arg[ 7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
-> arg[ 8]: -Dapplication.home=/usr/sap/SMD/exe
-> arg[ 9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
-> arg[ 11]: -Dmemory.manager=256M
-> arg[ 12]: -Xmx256M
-> arg[ 13]: -Xms256M
-> arg[ 14]: -DLoadBalanceRestricted=no
-> arg[ 15]: -Djstartup.mode=JCONTROL
-> arg[ 16]: -Djstartup.ownProcessId=17393
-> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
-> arg[ 18]: -Djstartup.whoami=server
-> arg[ 19]: -Djstartup.debuggable=yes
-> arg[ 20]: -DSAPINFO=SMD_98_server
-> arg[ 21]: -DSAPSTARTUP=1
-> arg[ 22]: -DSAPSYSTEM=98
-> arg[ 23]: -DSAPSYSTEMNAME=SMD
-> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
-> arg[ 25]: -DSAPDBHOST=
-> arg[ 26]: -Dj2ee.dbhost=
[Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
[Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1086335328] Wed Oct 7 08:56:35 2009
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1086335328] Wed Oct 7 08:56:38 2009
[Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
[Thr 1101334880] Wed Oct 7 08:56:43 2009
[Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
[Thr 1101334880] Wed Oct 7 08:56:48 2009
[Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)] -
RCA - SMD agent is not getting started
Hello Gurus ,
We have installed SMD agent 7.11 on managed system. It installed smoothly but at the time of starting the agent , it is giving error as follows.
jcmon=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jcmon=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
jcmon=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jcmon=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
I am seeing following errors in logs.
[Thr 01] Tue Apr 6 10:43:05 2010
[Thr 01] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx_mt.c 228]
[Thr 01] Tue Apr 6 10:43:08 2010
[Thr 01] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx_mt.c 228]
[Thr 01] Tue Apr 6 10:43:11 2010
[Thr 01] ***LOG Q0I=> NiPGetHostByName: '' not found: getaddrinfo [niuxi.c 1599]
[Thr 01] *** ERROR => MsIAttachEx: NiBufConnect to /36 failed (rc=NIEHOST_UNKNOWN) [msxxi_mt.c 707]
[Thr 01] *** ERROR => Can't attach to message server [jcmonms_mt.c 138]
[Thr 01] *** ERROR => Can't connect to message server [jcmonxx_mt.c 185]
[Thr 01] Tue Apr 6 10:43:13 2010
[Thr 01] *** ERROR => JsfOpenShm: ShmCreate(79, 4096, ATTACH) failed (rc = 3 SHM segment doesn't exist) [jsfxxshm_mt. 1683]
Please help.Thanks
It was related to DNS server problem.
It is resolved now.
thanks
Deepak Joshi -
Install SMD agent on EP6 fails
Hi,
I get an error when installing SDM agent on EP6 (HP-UX):
STEP 7: checking P4 Connection and SMD Agent Registration
External Command Executed:
/opt/java1.4/bin/java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp ":/usr/sap/SMD/J97/SMDAgent/lib/sapxmltoolkit.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdagent.jar:/usr/sap/SMD/J97/SMDAgent/lib/tc_sec_secstorefs.jar:/usr/sap/SMD/J97/SMDAgent/lib/iaik_jce_export.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/logging.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdserver.jar:/usr/sap/SMD/J97/SMDAgent/lib/exception.jar:/usr/sap/SMD/J97/SMDAgent/lib/sapj2eeclient.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/smdagentlauncher.jar:" com.sap.smd.setup.Setup /p4connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
P4 Connection succeeded but SMD Agent Registration failed
Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of smdserver.
I couldn't find anything on SAP Market Place but a similar thread here advised to check if SDM servers is not in maintenance mode.
Well, it's not.
Can someone please help?
Thx
BertHi,
Did you connect to smd server http://host:port/smd and desactivate maintenance mode in Agent Administration page?
This should solve your issue.
Regards,
Frederic -
Hi,
wihout changing the version or so we suddenly we experience the following error at status page (although the monitored web-page is fine):
Current alert: Failed to start e-TEST agent: error starting agent: \ne-TEST process has not established socket in 30 seconds.
Any ideas?
Thanks in advanceHi emposadi,
It looks like the e-Load server is having trouble communicating with the agent. Are you running the load test using an agent on the same machine or remote machine? You might want to see if a process has grabbed a port that the server communicates with the agent on. I would reboot the machines in question, shut down the Empirix Application Server and verify that ports 1099 and 9001 are not in use. Those are the ports that e-Load uses to communicate with the agent.
-GateCity_QA -
hi All
I am using SQl 2008, and agent failed to start
2015-03-16 11:11:31 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2015-03-16 11:11:31 - ! [298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
2015-03-16 11:11:31 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2015-03-16 11:11:32 - ? [098] SQLServerAgent terminated (normally)
SQLserver has started~~Hello,
Try changing the SQL Server agent service account to Local System or by the same account you are using to
start the SQL Server service account. The following article for changing SQL Server service account may help you, since it is a similar procedure.
https://msdn.microsoft.com/en-us/library/ms345578.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Hi everyone.
I am trying to start the diagnostic agent by going to /usr/sap/SMD/J98/scripts and giving the command smdstart.sh 98
But on executing the command I get the below error message :
SAP Solution Manager - Diagnostics Agent - Copyright (c) 2007 SAP AG
[-] Prerequisites
Max open files limit .. OK
Max memory size limit .. OK
[-] Starting agent SMD / 98 on host with user ep1adm ..
/usr/sap/SMD/exe/smdstart.sh: !: not found
SAPOSCOL version COLL 20.95 700 - V3.72 64Bit, 64 bit, single threaded, Non-Unicode
compiled at Jan 23 2008
systemid 370 (Solaris on SPARCV9 CPU)
relno 7000
patch text COLL 20.95 700 - V3.72 64Bit
patchno 144
intno 20050900
running on prdrcl2 SunOS 5.10 Generic_137111-08 sun4u
[-] Launching SAP SERVICE for Diagnostics Instance ...
ok.
[-] Launching Diagnostics Agent Instance ...
SAP-R/3-Startup Program Rel 700 V1.8 (2003/04/24)
Starting at 2010/01/04 14:23:55
Startup Profile: "/usr/sap/SMD/SYS/profile/START_J98_EP1-lh-ora2"
Starting Programs
04.01.2010 14:23:55
ShmDetach
OK
(24040) Starting: local /usr/sap/SMD/J98/../exe/jcontrol pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_EP1-lh-ora2
(24036) Waiting for Child Processes to terminate.
(24036) **** 2010/01/04 14:23:55 Child 24040 terminated with Status 255 . ****
(24036) **** No more Child Processes to wait for.
(24036) Parent Shutdown at 2010/01/04 14:23:55
Execute Post-Shutdown Commands
04.01.2010 14:23:55
ShmDetach
OK
(24036) Exiting with Return-Code 3. (No more child processes)
Can anyone let me know what might be going wrong and what I need to do to start the diagnostic agent?
Regards,
Saurabh.Hi,
there are many possiblities
1) Could you plz check the permission of script.
2) Manually execute the script by appending the log text, and paste the same log here.
eg. script.exe >>log.txt
3) Clean restart of total system, becoz there may be problem with SHM.
Regards,
Shyam. -
SMD agent starts, but stderr0 has errors
Hallo Gurus,
we had installed the new Diagnostic Agents 7.11 for our EP.
Now the Agent runs after installation, but in the stderr0 we have the following errors.
(13107436) New Child Process created.
(13107436) Starting local Command:
Command: jc.sapDAA_SMDA97
pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_sapipp
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
In the sdn are no answer for this issue.
Some suggestion???
regards
ChrisWe get data from the agent, but i think that is not all data that we can get...
SAPSYSTEMNAME = DAA
SAPSYSTEM = 97
INSTANCE_NAME = SMDA97
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/rs6000_64
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = sapepp
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/DAA_SMDA97_sapepp
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
# Copy SAP Executables
_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
_CPARG1 = list:$(DIR_CT_SAPJVM)/sapjvm_5.lst
_CPARG2 = source:$(DIR_CT_SAPJVM)
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1) $(_CPARG2)
# JStart configuration
SAPJVM_VERSION = 5.1.038
jstartup/vm/home = $(DIR_SAPJVM)
jstartup/bootstrap = no
# Start SMD Agent
_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_JC)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jstart$(FT_EXE) $(_JC)
Start_Program_00 = local $(_JC) pf=$(_PF)
# File generated automatically by the diagnostics agent sapinst.
# Created 2010.09.23 at 12:23:10 GMT
# sapinst classes version: 7.01.2.6.20090526074537
# Title: DAA_SMDA97_sapepp
# Description: File which specify the start parameters used by Jstartup framework for Diagnostics Agent process.
# Don't modifiy manually this script.
smd/agent/type=710
jstartup/instance_properties=$(DIR_INSTANCE)/SMDAgent/smdagent.properties -
Failed to connect to server - Please make sure SMD Agent is up and Running
Hi All
I am getting this message in SMD when trying to set up the SMD agent on one of our JAV servers - this is possibly a really simple problem to solve but I have no idea how to start the SDM Agent.
Can anyone give me instructions on how to do this (Windows / SQL)?
Thanks in advance
PhilHi Phil,
The SMD Agent gets installed as an instance & can be started/stopped via the SAP MMC.
Have a great day,
-S. -
Connecting to SMD server failed
Hello folks,
We installed a java add-in on a machine running ECC 6.0. The installation went fine and we could log-in to the portal using the webbrowser. After that we tried to upgrade all components from SP14 to SP17. But when the JSPM tried to restart the J2EE-Engine, the SMD didn't come up again and stayed in status "Starting processes". We could fix this be reinstalling the SMD-Agent, but now our main instance tells us in the MMC that "J2EE status info unavailable". I can't reach the portal using the webbrowser as well as I can't login using visual administrator.
In the SMDSystem.x.log I just get following lines over and over again:
Mar 25, 2009 5:59:27 PM [Thread[SMDAgent connection thread,5,main]] Info [p4://saphcx:59804] Waiting for connection ...
Mar 25, 2009 5:59:27 PM [Thread[SMDAgent connection thread,5,main]] Info [p4://saphcx:59804] Checking server availability...
Mar 25, 2009 5:59:29 PM [Thread[SMDAgent connection thread,5,main]] Warning Connecting to SMD server p4://saphcx:59804 failed - error counter: 0 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
Nested exceptions are:
com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 10.10.24.4 and port: 59804
Content of dev_jcontrol:
trc file: "D:\usr\sap\SMD\J98\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 132
system name : SMD
system nr. : 98
started at : Wed Mar 25 18:08:20 2009
arguments :
arg[00] : D:\usr\sap\SMD\J98\..\exe\jcontrol.exe
arg[01] : pf=D:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saphcx
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMD\J98\profile\smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : D:\usr\sap\SMD\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMD\J98\profile\smd.properties
Instance properties
-> ms host :
-> ms port : 36
-> os libs : D:\usr\sap\SMD\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] smdagent : D:\usr\sap\SMD\J98\profile\smd.properties
[Thr 4444] Wed Mar 25 18:08:20 2009
[Thr 4444] *** WARNING => Key profile parameters not set D:\usr\sap\SMD\J98\..\SYS\profile\DEFAULT.PFL:
j2ee/scs/host=
j2ee/scs/system= [jcntrxx.c 1459]
[Thr 4444] *** WARNING => Can't open default profile [D:\usr\sap\SMD\J98\..\SYS\profile\DEFAULT.PFL] for migration [jcntrxx.c 1460]
[Thr 4444] JControlExecuteBootstrap: jcontrol runs in 6.20 compatible mode
[Thr 4444] JControlExecuteBootstrap: jcontrol runs in 6.20 compatible mode
[Thr 4444] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5320] JControlRequestFunc: Thread 5320 started as listener thread for np messages.
[Thr 4444] [Node: SMDAgent] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_19-x64\
[Thr 4444] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMD\exe\jvmx.jar
JStartupIReadSection: read node properties [smdagent]
-> node name : SMDAgent
-> node type : server
-> node id : 1
-> node execute : yes
-> java path : C:\j2sdk1.4.2_19-x64\
-> java parameters : -DP4ClassLoad=P4Connection
-> java vm version : 1.4.2_19-rev-b07
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 128M
-> init heap size : 128M
-> root path : ..\SMDAgent
-> class path : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> OS libs path : D:\usr\sap\SMD\exe
-> main class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\SMD\exe\jstartup.jar;D:\usr\sap\SMD\exe\jvmx.jar
-> shutdown class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> parameters : run jcontrol
-> debuggable : yes
-> debug mode : no
-> debug port : 58981
-> shutdown timeout : 20000
[Thr 4444] JControlConnectToMS: jcontrol runs in 6.20 compatible mode without message server
JControlStartJLaunch: program = D:\usr\sap\SMD\J98\..\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\SMD\J98\..\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saphcx
-> arg[02] = -DSAPINFO=SMD_98_server
-> arg[03] = -nodeId=0
-> arg[04] = -file=D:\usr\sap\SMD\J98\profile\smd.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_132
-> arg[06] = -nodeName=smdagent
-> arg[07] = -jvmOutFile=D:\usr\sap\SMD\J98\work\jvm_SMDAgent.out
-> arg[08] = -stdOutFile=D:\usr\sap\SMD\J98\work\std_SMDAgent.out
-> arg[09] = -locOutFile=D:\usr\sap\SMD\J98\work\dev_SMDAgent
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saphcx
-> lib path = PATH=C:\j2sdk1.4.2_19-x64
jre\bin\server;C:\j2sdk1.4.2_19-x64
jre\bin;C:\Program Files\Legato\nsr\bin;D:\oracle\HCX\102\bin;C:\Program Files (x86)\Windows Resource Kits\Tools\;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_19-x64\bin;D:\usr\sap\SMD\exe
-> exe path = PATH=C:\j2sdk1.4.2_19-x64
bin;D:\usr\sap\SMD\exe;C:\Program Files\Legato\nsr\bin;D:\oracle\HCX\102\bin;C:\Program Files (x86)\Windows Resource Kits\Tools\;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_19-x64\bin;D:\usr\sap\SMD\exe
[Thr 4444] JControlICheckProcessList: process SMDAgent started (PID:6048)
Content of dev_SMDAgent
trc file: "D:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "700"
node name : smdagent
pid : 6048
system name : SMD
system nr. : 98
started at : Wed Mar 25 18:08:20 2009
arguments :
arg[00] : D:\usr\sap\SMD\J98\..\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saphcx
arg[02] : -DSAPINFO=SMD_98_server
arg[03] : pf=D:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saphcx
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMD\J98\profile\smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : D:\usr\sap\SMD\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMD\J98\profile\smd.properties
Instance properties
-> ms host :
-> ms port : 36
-> os libs : D:\usr\sap\SMD\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] smdagent : D:\usr\sap\SMD\J98\profile\smd.properties
[Thr 5948] Wed Mar 25 18:08:20 2009
[Thr 5948] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5948] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2000] WaitSyncSemThread: Thread 2000 started as semaphore monitor thread.
[Thr 4740] JLaunchRequestFunc: Thread 4740 started as listener thread for np messages.
[Thr 5948] NiInit3: NI already initialized; param 'maxHandles' ignored (1;402)
[Thr 5948] CPIC (version=700.2006.09.13)
[Thr 5948] [Node: SMDAgent] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_19-x64\
[Thr 5948] Wed Mar 25 18:08:21 2009
[Thr 5948] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMD\exe\jvmx.jar
JStartupIReadSection: read node properties [smdagent]
-> node name : SMDAgent
-> node type : server
-> node id : 1
-> node execute : yes
-> java path : C:\j2sdk1.4.2_19-x64\
-> java parameters : -DP4ClassLoad=P4Connection
-> java vm version : 1.4.2_19-rev-b07
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 128M
-> init heap size : 128M
-> root path : ..\SMDAgent
-> class path : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> OS libs path : D:\usr\sap\SMD\exe
-> main class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\SMD\exe\jstartup.jar;D:\usr\sap\SMD\exe\jvmx.jar
-> shutdown class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> parameters : run jcontrol
-> debuggable : yes
-> debug mode : no
-> debug port : 58981
-> shutdown timeout : 20000
[Thr 5948] JLaunchISetDebugMode: set debug mode [no]
[Thr 6040] JLaunchIStartFunc: Thread 6040 started as Java VM thread.
[Thr 6040] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
Java Parameters: -Xss2m
JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -DP4ClassLoad=P4Connection
-> arg[ 4]: -Dsys.global.dir=D:\usr\sap\SMD\SYS\global
-> arg[ 5]: -Dapplication.home=D:\usr\sap\SMD\exe
-> arg[ 6]: -Djava.class.path=D:\usr\sap\SMD\exe\jstartup.jar;D:\usr\sap\SMD\exe\jvmx.jar;lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> arg[ 7]: -Djava.library.path=C:\j2sdk1.4.2_19-x64
jre\bin\server;C:\j2sdk1.4.2_19-x64
jre\bin;C:\j2sdk1.4.2_19-x64
bin;D:\usr\sap\SMD\exe;C:\Program Files\Legato\nsr\bin;D:\oracle\HCX\102\bin;C:\Program Files (x86)\Windows Resource Kits\Tools\;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_19-x64\bin;D:\usr\sap\SMD\exe
-> arg[ 8]: -Dmemory.manager=128M
-> arg[ 9]: -Xmx128M
-> arg[ 10]: -Xms128M
-> arg[ 11]: -DLoadBalanceRestricted=no
-> arg[ 12]: -Djstartup.mode=JCONTROL
-> arg[ 13]: -Djstartup.ownProcessId=6048
-> arg[ 14]: -Djstartup.ownHardwareId=F1342910626
-> arg[ 15]: -Djstartup.whoami=server
-> arg[ 16]: -Djstartup.debuggable=yes
-> arg[ 17]: -Xss2m
-> arg[ 18]: -DSAPINFO=SMD_98_server
-> arg[ 19]: -DSAPSTARTUP=1
-> arg[ 20]: -DSAPSYSTEM=98
-> arg[ 21]: -DSAPSYSTEMNAME=SMD
-> arg[ 22]: -DSAPMYNAME=saphcx_SMD_98
-> arg[ 23]: -DSAPDBHOST=
-> arg[ 24]: -Dj2ee.dbhost=
[Thr 6040] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
[Thr 6040] Wed Mar 25 18:08:22 2009
[Thr 6040] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 6040] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 6040] JLaunchISetState: change state from [Waiting for start (1)] to [Initial (0)]
[Thr 6040] JLaunchISetState: change state from [Initial (0)] to [Starting (2)]
Does anybody have any idea on how to fix the problem?
Thanks and best regards,
Benjamin HuthHi Benjamin Huth
Please check SAP Note 1144737 -Inst.NW 7.0 SR3 - Diagnostics Agent installation.
Open a shell on <drive>:\usr\sap\<smdsid>\JXX\script and execute
the command:
smdsetup sldconf hostname:"<SLD_HOSTNAME>" port:"<SLD_PORT>" user:"<SLDDSUSER>" pwd:"<SLDDSUSER_PWD>"
maybe solove your problem.
Best Regards,
Wu
Maybe you are looking for
-
Use of "Open FPGA VI Reference" function --- Build Specification vs VI vs Bitfile
When using the "Open FPGA VI Reference" function in a LV2012 cRIO application, there are 3 options: Build Specification, VI, or Bitfile. What would be the reasons for selecting one over the others? Does it affect the resulting startup.rtexe when the
-
Can I delete all files and users (including admin account) without re-installing SL?
I have a 1st generation Macbook Air, running Snow Leopard 10.6.8. Just bought myself a new MBA, want to sell the old one (privately, not soliciting here). The original install disks were Leopard. I bought a family pack SL and upgraded the MBA at th
-
Top n Growing tables in BW & R/3 with Oracle env
Hi all, We are on BW 7.0 with Oracle 10.2.0.2 , please let me know how to get the top N growing tables & Top N largest tables. I remember collecting these stats from TX: DB02 when we had MS SQLserver as the DB. It was as easy as clicking a button.
-
How to set the heap size of JVM
please let me know that how to set the heap size of JVM
-
Understand​ing DAQmxTaskC​ontrol()
Hi all , I have a few question about the DAQmxTaskControl() function: 1. What's the difference between DAQmxStartTask(gAItaskHandle); to DAQmxTaskControl (gAItaskHandle, DAQmx_Val_Task_Start); is there any difference in the time it takes ? 2. What