- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- SOLMAN 7.0 EHP1 problem with starting SMD instance
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
SOLMAN 7.0 EHP1 problem with starting SMD instance
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-08-2010 2:01 PM
Hello everyone,<br><br>
i have problem with starting instance SMD in my Solution Manager. After START this instance is status for one-two secend green and then status go to yellow color in SAP Management Console. I dont now where is problem, i try everything, can you help me?<br><br>
Here is LOG from <b>dev_SMDAgent</b><br><br>
-
trc file: "G:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "701"
-
node name : smdagent
pid : 1136
system name : SMD
system nr. : 98
started at : Thu Jul 08 14:49:55 2010
arguments :
arg[00] : G:\usr\sap\SMD\J98\..\exe\jlaunch.exe
arg[01] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_SAPVSM01
arg[02] : -DSAPINFO=SMD_98_server
arg[03] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_SAPVSM01
**********************************************************************
JStartupReadInstanceProperties: read instance properties [G:\usr\sap\SMD\J98\profile\smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : G:\usr\sap\SMD\J98\..\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : G:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host :
-> ms port : 36
-> os libs : G:\usr\sap\SMD\J98\..\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
**********************************************************************
**********************************************************************
Worker nodes
-> [00] smdagent : G:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
[Thr 5392] Thu Jul 08 14:49:55 2010
[Thr 5392] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5392] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2068] JLaunchRequestFunc: Thread 2068 started as listener thread for np messages.
[Thr 220] WaitSyncSemThread: Thread 220 started as semaphore monitor thread.
[Thr 5392] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 5392] CPIC (version=701.2009.01.26)
[Thr 5392] [Node: SMDAgent] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_26-x64\
[Thr 5392] JStartupICheckFrameworkPackage: can't find framework package G:\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 : C:\j2sdk1.4.2_26-x64\
-> java parameters : -DP4ClassLoad=P4Connection
-> java vm version : 1.4.2_26-b03
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 256M
-> init heap size : 256M
-> root path : ..\SMDAgent
-> class path : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> OS libs path : G:\usr\sap\SMD\J98\..\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 : G:\usr\sap\SMD\J98\..\exe\jstartup.jar;G:\usr\sap\SMD\J98\..\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 5392] JLaunchISetDebugMode: set debug mode [no]
[Thr 2448] JLaunchIStartFunc: Thread 2448 started as Java VM thread.
[Thr 2448] Thu Jul 08 14:49:56 2010
[Thr 2448] [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=G:\usr\sap\SMD\SYS\global
-> arg[ 5]: -Dapplication.home=G:\usr\sap\SMD\J98\..\exe
-> arg[ 6]: -Djava.class.path=G:\usr\sap\SMD\J98\..\exe\jstartup.jar;G:\usr\sap\SMD\J98\..\exe\jvmx.jar;lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> arg[ 7]: -Djava.library.path=C:\j2sdk1.4.2_26-x64
jre\bin\server;C:\j2sdk1.4.2_26-x64
jre\bin;C:\j2sdk1.4.2_26-x64
bin;G:\usr\sap\SMD\J98\..\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;G:\usr\sap\SMD\exe
-> arg[ 8]: -Dmemory.manager=256M
-> arg[ 9]: -Xmx256M
-> arg[ 10]: -Xms256M
-> arg[ 11]: -DLoadBalanceRestricted=no
-> arg[ 12]: -Djstartup.mode=JCONTROL
-> arg[ 13]: -Djstartup.ownProcessId=1136
-> arg[ 14]: -Djstartup.ownHardwareId=H1630488451
-> 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=SAPVSM01_SMD_98
-> arg[ 23]: -DSAPDBHOST=
-> arg[ 24]: -Dj2ee.dbhost=
**********************************************************************
[Thr 2448] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
**********************************************************************
[Thr 2448] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2448] Thu Jul 08 14:49:57 2010
[Thr 2448] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 2448] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 2448] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 3140] JLaunchIExitJava: exit hook is called (rc = -11112)
[Thr 3140] **********************************************************************
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 3140] JLaunchCloseProgram: good bye (exitcode = -11112)<br><br>
LOG dev_jcontrol<br><br>
-
trc file: "G:\usr\sap\SMD\J98\work\dev_jcontrol", trc level: 1, release: "701"
-
node name : jcontrol
pid : 840
system name : SMD
system nr. : 98
started at : Thu Jul 08 14:49:53 2010
arguments :
arg[00] : G:\usr\sap\SMD\J98\..\exe\jcontrol.exe
arg[01] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_SAPVSM01
**********************************************************************
JStartupReadInstanceProperties: read instance properties [G:\usr\sap\SMD\J98\profile\smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : G:\usr\sap\SMD\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : G:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host :
-> ms port : 36
-> os libs : G:\usr\sap\SMD\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
**********************************************************************
**********************************************************************
Worker nodes
-> [00] smdagent : G:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
[Thr 5968] Thu Jul 08 14:49:53 2010
[Thr 5968] *** WARNING => Key profile parameters not set G:\usr\sap\SMD\J98\..\SYS\profile\DEFAULT.PFL:
j2ee/scs/host=
j2ee/scs/system= [jcntrxx.c 1459]
[Thr 5968] *** WARNING => Can't open default profile [G:\usr\sap\SMD\J98\..\SYS\profile\DEFAULT.PFL] for migration [jcntrxx.c 1460]
[Thr 5968] JControlExecuteBootstrap: jcontrol runs in 6.20 compatible mode
[Thr 5968] JControlExecuteBootstrap: jcontrol runs in 6.20 compatible mode
[Thr 5968] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5968] [Node: SMDAgent] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_26-x64\
[Thr 384] JControlRequestFunc: Thread 384 started as listener thread for np messages.
[Thr 5968] Thu Jul 08 14:49:54 2010
[Thr 5968] JStartupICheckFrameworkPackage: can't find framework package G:\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_26-x64\
-> java parameters : -DP4ClassLoad=P4Connection
-> java vm version : 1.4.2_26-b03
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 256M
-> init heap size : 256M
-> root path : ..\SMDAgent
-> class path : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> OS libs path : G:\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 : G:\usr\sap\SMD\exe\jstartup.jar;G:\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 5968] JControlConnectToMS: jcontrol runs in 6.20 compatible mode without message server
**********************************************************************
JControlStartJLaunch: program = G:\usr\sap\SMD\J98\..\exe\jlaunch.exe
-> arg[00] = G:\usr\sap\SMD\J98\..\exe\jlaunch.exe
-> arg[01] = pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_SAPVSM01
-> arg[02] = -DSAPINFO=SMD_98_server
-> arg[03] = -nodeId=0
-> arg[04] = -file=G:\usr\sap\SMD\J98\profile\smd.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_840
-> arg[06] = -nodeName=smdagent
-> arg[07] = -jvmOutFile=G:\usr\sap\SMD\J98\work\jvm_SMDAgent.out
-> arg[08] = -stdOutFile=G:\usr\sap\SMD\J98\work\std_SMDAgent.out
-> arg[09] = -locOutFile=G:\usr\sap\SMD\J98\work\dev_SMDAgent
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_SAPVSM01
-> lib path = PATH=C:\j2sdk1.4.2_26-x64
jre\bin\server;C:\j2sdk1.4.2_26-x64
jre\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;G:\usr\sap\SMD\exe
-> exe path = PATH=C:\j2sdk1.4.2_26-x64
bin;G:\usr\sap\SMD\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;G:\usr\sap\SMD\exe
**********************************************************************
[Thr 5968] JControlICheckProcessList: process SMDAgent started (PID:1136)
[Thr 5968] Thu Jul 08 14:49:59 2010
[Thr 5968] JControlICheckProcessList: process SMDAgent (pid:1136) died (RUN-FLAG)
[Thr 5968] JControlIResetProcess: reset process SMDAgent
[Thr 5968] JControlIResetProcess: [SMDAgent] not running -> increase error count (1)
[Thr 5968] JControlICheckProcessList: shutdown node from console -> restart off
THANKS FOR RESPONSE
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (0)
Answers (2)
Answers (2)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Martin,
Check note 940893 (If this is not done already )
Regards
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Martin,
Kindly check Note 1375494 .
Kindly post more brief abt server.
Regards,
Karthik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- CAP Autentication error in Technology Q&A
- Demystifying the Common Super Domain for SAP Mobile Start in Technology Blogs by SAP
- App to automatically configure a new ABAP Developer System in Technology Blogs by Members
- How to use AI services to translate Picklists in SAP SuccessFactors - An example in Technology Blogs by SAP
- IoT - Ultimate Data Cyber Security - with Enterprise Blockchain and SAP BTP 🚀 in Technology Blogs by Members
| User | Count |
|---|---|
| 83 | |
| 10 | |
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.