- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Errors during install of Solution Manager 7.0 w/Ma...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Errors during install of Solution Manager 7.0 w/MaxDB (central)
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-18-2011 1:41 PM
Hi
I am trying to install Solution Manager 7.0 w/MaxDB on a linux box. I have reached phase 47/50 and am running into errors that say:
ERROR 2011-07-14 16:29:54.609
CJS-30151 Java process server0 of instance OSM/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 1:30 minutes. Giving up.
ERROR 2011-07-14 16:29:54.757
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|6|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|startJava was executed with status ERROR ( Last error reported by the step :Java process server0 of instance OSM/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 1:30 minutes. Giving up.).
Here is the java version I am using (JVM 4.1)
atl-osm-01:osmadm 80> java -version
java version "1.4.2_30"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.009)
SAP Java Server VM (build 4.1.009 17.0-b16, May 27 2011 00:12:32 - 41_REL - optU - linux amd64 - 6 - bas2:154157 (mixed mode))
in the dev_jcontrol log I see:
-> lib path = LD_LIBRARY_PATH=/opt/java/sapjvm_4/jre/lib/amd64/server:/opt/java/sapjvm_4/jre/lib/amd64:/opt/java/sapjvm_4/jre/../lib/amd64:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/tmp/sapinst_exe.26924.1310559612:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/OSM/DVEBMGS00/j2ee/os_libs:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib
-> exe path = PATH=/opt/java/java/bin:/usr/sap/OSM/DVEBMGS00/j2ee/os_libs:/sapdb/programs/bin:/opt/java/java/bin:.:/home/osmadm:/usr/sap/OSM/SYS/exe/run:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/dell/srvadmin/bin
**********************************************************************
[Thr 47171544096752] JStartupICreateProcess: fork process (pid 5857)
[Thr 47171544096752] JControlICheckProcessList: process server0 started (PID:5857)
[Thr 47171544096752] Thu Jul 14 16:29:19 2011
[Thr 47171544096752] JControlICheckProcessList: process server0 (pid:5857) died (RUN-FLAG)
[Thr 47171544096752] JControlIResetProcess: reset process server0
[Thr 47171544096752] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 47171544096752] JControlICheckProcessList: running flight recorder:
/opt/java/java/bin/java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID3888650 1310675354 -bz /usr/sap/OSM/SYS/global
In the dev_w12 trace log I see:
M *****************************************************************************
M *
M * LOCATION SAP-Gateway on host atl-osm-01 / sapgw00
M * ERROR program SLD_UC not registered
M *
M * TIME Thu Jul 14 16:25:52 2011
M * RELEASE 700
M * COMPONENT SAP-Gateway
M * VERSION 2
M * RC 679
M * MODULE gwr3cpic.c
M * LINE 1778
M * DETAIL TP SLD_UC not registered
M * COUNTER 3
M *
M *****************************************************************************
M
A RFC 1485 CONVID 80159271
A * CMRC=2 DATA=0 STATUS=0 SAPRC=679 ThSAPOCMINIT
A RFC> ABAP Programm: RSLDAGDS (Transaction: )
A RFC> User: DDIC (Client: 001)
A RFC> Destination: SLD_UC (handle: 1, , )
A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
[abrfcio.c 8141]
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
DEST =SLD_UC
HOST =%%RFCSERVER%%
PROG =SLD_UC
GWHOST =atl-osm-01
GWSERV =sapgw00
[abrfcio.c 8141]
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
B table logging switched off for all clients
S handle memory type is RSTSPROMMM
Any ideas on how I can fix this? Anything else that I should post that will help with analyzing the issue?
Thanks in advance!
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
> Here is the java version I am using (JVM 4.1)
> atl-osm-01:osmadm 80> java -version
> java version "1.4.2_30"
> Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.009)
> SAP Java Server VM (build 4.1.009 17.0-b16, May 27 2011 00:12:32 - 41_REL - optU - linux amd64 - 6 - bas2:154157 (mixed mode))
The problem you face is the following:
The SolMan installation media assumes, that you use the IBM JDK for the installation. The parameters, that are set by sapinst are for the IBM JDK.
The SAP JDK is based on the Sun JDK - which uses different parameters.
--> Your system doesn't start because the JVM has unkonwn parameter settings.
You have now two options:
- Install the system using the IBM JDK and use the Java switch tool to change to the SAP JVM
- Modify the parameters of the Java engine using configtool and the parameter settings of "Note 1522200 - SAP JVM 4.1 parameters when switching from a partner JDK"
Markus
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Answers (8)
Answers (8)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
If the server is not starting, you might check the log space in the database. By default, MaxDB does not grow the log and the server will have some difficulties fully starting if there is no log space.
Rob
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Using JCMON to restart the instance and looking at the display I see:
Idx | Name | PID | State | Error | Restart |
--- | |||||
0 | dispatcher | 30978 | Running | 0 | yes |
1 | server0 | 0 | Stopped | 5 | no |
2 | SDM | 30980 | Running | 0 | yes |
-
There is still some error bringing the server0 up. What should I look at next?
I also see in the std_server0 file that there is an error regarding jvmx.jar:
JStarupICheckFrameworkPackage: can't find framework package /usr/sap/OSM/DVEBMGS00/exe/jvmx.jar.
I searched for this file and it is not in the exe directory, however it is in the java directory:
/opt/java/sapjvm_4/tools/lib/jvmx.jar
Could this be the problem? Do i need to copy the jvmx.jar file over to the exe directory?
Edited by: Hans Bhargava on Jul 19, 2011 9:57 AM
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Sunny -
I do not see a a defaultTrace log created in the directory since 7/14:
drwxr-xr-x 3 osmadm sapsys 839680 Jul 14 12:46 archive
-rw-rr 1 osmadm sapsys 434317 Jul 14 12:48 applications.0.log
-rw-rr 1 osmadm sapsys 4017733 Jul 14 12:48 defaultTrace.5.trc
drwxr-xr-x 3 osmadm sapsys 4096 Jul 19 10:35 system
atl-osm-01:osmadm 118> pwd
/usr/sap/OSM/DVEBMGS00/j2ee/cluster/server0/log
Why would I not be getting defaultTrace logs now?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
What specifically am I looking for to determine if server0 has started or not? Is there a process I can search for?
After restarting the system and performing a ps -ef | grep sap here is what I see:
osmadm 684 1 0 Jul13 ? 00:00:00 /usr/sap/OSM/SCS01/exe/sapstartsrv pf=/usr/sap/OSM/SYS/profile/START_SCS01_atl-osm-01 -D
root 716 1 0 Jul13 ? 00:23:35 /usr/sap/OSM/SYS/exe/run/saposcol
osmadm 10456 1 0 Jul14 ? 00:00:00 /usr/sap/OSM/DVEBMGS00/exe/sapstartsrv pf=/usr/sap/OSM/SYS/profile/START_DVEBMGS00_atl-osm-01 -D
sdb 28837 1 0 Jul13 pts/0 00:00:00 /sapdb/programs/pgm/niserver
sdb 28840 1 0 Jul13 pts/0 00:00:01 /sapdb/programs/pgm/vserver start
sdb 29935 1 0 08:19 ? 00:00:00 /sapdb/ODB/db/pgm/kernel ODB
sdb 29940 29935 3 08:19 ? 00:00:04 /sapdb/ODB/db/pgm/kernel ODB
osmadm 30028 1 0 08:19 ? 00:00:00 /usr/sap/OSM/SCS01/exe/sapstart pf=/usr/sap/OSM/SYS/profile/START_SCS01_atl-osm-01
osmadm 30042 30028 0 08:19 ? 00:00:00 ms.sapOSM_SCS01 pf=/usr/sap/OSM/SYS/profile/OSM_SCS01_atl-osm-01
osmadm 30043 30028 0 08:19 ? 00:00:00 en.sapOSM_SCS01 pf=/usr/sap/OSM/SYS/profile/OSM_SCS01_atl-osm-01
osmadm 30071 1 0 08:20 ? 00:00:00 /usr/sap/OSM/DVEBMGS00/exe/sapstart pf=/usr/sap/OSM/SYS/profile/START_DVEBMGS00_atl-osm-01
osmadm 30098 30071 0 08:20 ? 00:00:00 ms.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30099 30071 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30100 30071 0 08:20 ? 00:00:00 co.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -F
osmadm 30101 30071 0 08:20 ? 00:00:00 se.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -F
osmadm 30102 30071 0 08:20 ? 00:00:00 ig.sapOSM_DVEBMGS00 -mode=profile pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30103 30102 0 08:20 ? 00:00:00 /usr/sap/OSM/DVEBMGS00/exe/igsmux_mt -mode=profile -restartcount=0 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30104 30102 0 08:20 ? 00:00:00 /usr/sap/OSM/DVEBMGS00/exe/igspw_mt -mode=profile -no=0 -restartcount=0 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30105 30102 0 08:20 ? 00:00:00 /usr/sap/OSM/DVEBMGS00/exe/igspw_mt -mode=profile -no=1 -restartcount=0 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30122 30099 1 08:20 ? 00:00:00 gwrd -dp pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30123 30099 0 08:20 ? 00:00:00 icman -attach pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30124 30099 0 08:20 ? 00:00:00 jcontrol pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DSAPSTART=1 -DCONNECT_PORT=65000 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=OSM -DSAPMYNAME=atl-osm-01_OSM_00 -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
osmadm 30125 30099 2 08:20 ? 00:00:01 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30126 30099 2 08:20 ? 00:00:01 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30127 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30129 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30131 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30132 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30133 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30134 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30137 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30138 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30139 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30140 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30141 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30142 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30143 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30144 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30145 30099 0 08:20 ? 00:00:00 dw.sapOSM_DVEBMGS00 pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
osmadm 30240 30124 19 08:20 ? 00:00:12 /usr/sap/OSM/DVEBMGS00/exe/jlaunch pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DSAPINFO=OSM_00_dispatcher -nodeId=0 -file=/usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties -syncSem=344260748 -nodeName=ID3888600 -jvmOutFile=/usr/sap/OSM/DVEBMGS00/work/jvm_dispatcher.out -stdOutFile=/usr/sap/OSM/DVEBMGS00/work/std_dispatcher.out -locOutFile=/usr/sap/OSM/DVEBMGS00/work/dev_dispatcher -mode=JCONTROL pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DSAPSTART=1 -DCONNECT_PORT=50779 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=OSM -DSAPMYNAME=atl-osm-01_OSM_00 -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
osmadm 30242 30124 7 08:20 ? 00:00:05 /usr/sap/OSM/DVEBMGS00/exe/jlaunch pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DSAPINFO=OSM_00_sdm -nodeId=2 -file=/usr/sap/OSM/DVEBMGS00/SDM/program/config/sdm_jstartup.properties -syncSem=344260748 -nodeName=sdm -jvmOutFile=/usr/sap/OSM/DVEBMGS00/work/jvm_sdm.out -stdOutFile=/usr/sap/OSM/DVEBMGS00/work/std_sdm.out -locOutFile=/usr/sap/OSM/DVEBMGS00/work/dev_sdm -mode=JCONTROL pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DSAPSTART=1 -DCONNECT_PORT=50779 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=OSM -DSAPMYNAME=atl-osm-01_OSM_00 -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
sdb 30346 28840 0 08:20 pts/0 00:00:00 /sapdb/programs/pgm/vserver start
sdb 30413 28840 0 08:20 pts/0 00:00:00 /sapdb/programs/pgm/vserver start
osmadm 30529 28995 0 08:21 pts/1 00:00:00 grep sap
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
After restarting the system, the system does come up, but what am I looking for in terms of server0 coming up?
Once I restarted the system, I start sapinst again and restarted it from the point of failure and it failed again with the same error message.
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Sunny -
To restart the system manually is it simply using the commands:
1. stopsap all
2. startsap all
?
Thanks
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
And here is the std_server0.out log:
1 --------------------------------------------------------------------------------
2 stdout/stderr redirect
3 --------------------------------------------------------------------------------
4 node name : server0
5 pid : 5541
6 system name : OSM
7 system nr. : 00
8 started at : Thu Jul 14 16:28:59 2011
9
10 [Thr 47057802424304] MtxInit: -2 0 0
11 The following options are non-standard and subject to change without notice.
12
13 -XtraceFile=<file>
14 write traces to the given file
15 -XtraceInfoHeader=<format>
16 set the header format for info messages
17 -XtraceWarningHeader=<format>
18 set the header format for warning messages
19 -XtraceErrorHeader=<format>
20 set the header format for error messages
21 -XtraceHeader=<format>
22 set the header format for all messages
23
24 -XtraceMethods traces every method call
25 -XtraceExceptions traces java exception handling
26 -XtraceClassLoading
27 traces class loading
28 -XtraceClassUnloading
29 traces class unloading
30 -XtraceControls traces basic operations done by the VM controls
31 -XtraceControlsInternals
32 traces internals of the VM controls
33 -XtraceDebugOnDemand
34 traces the debug on demand functionality
35 -XtraceDebugModifications
36 traces modifications done to programs and program flow during
37 debugging
38 -XtraceFileIoBasic
39 traces basic file IO (open/close)
40 -XtraceFileIoReadWrite
41 traces file IO read and write
42 -XtraceFileIoReadWriteData
43 trace file IO read and write and dumps the data read and
44 written
45 -XtraceFileIoInternals
46 traces internals of the file IO
47 -XtraceNetworkIoBasic
48 traces basic network operations (bind, accept, listen, ...)
49 -XtraceNetworkIoSendReceive
50 traces send and receive network operations
51 -XtraceNetworkIoSendReceiveData
52 traces send and receive network operations and dumping the
53 data send or received
54 -XtraceNetworkIoInternals
55 traces internals of the network system
56 -XtraceJdwp traces JDWP packets exchanged between the JDPA library and
57 the debugger
58 -XtraceJdwpInternals
59 traces JDWP internals
60 -XtraceClassStatistic
61 traces class statistics after full GCs
62 -XtraceCMSPLABRefillSampling
63 traces the sampled time spent while refilling the PLABs
64 during each young generation GC
65 -XtraceCMSFreeListSpaceCensus
66 traces the CMS free list space census at each young
67 generation garbage collection
68 -XtraceConcMarkSweepGC
69 traces the concurrent mark sweep garbage collector
70 -XtraceConcMarkSweepGCInternals
71 traces internals of the concurrent mark sweep garbage
72 collector
73 -XtraceProfiling traces profiling
74 -XtraceProfilingInternals
75 traces profiling internals
76 -XtraceProfilingMPTBasics
77 traces basics of the method parameter trace
78 -XtraceProfilingMPTValues
79 traces the values wirtten by the method parameter trace
80 -XtraceProfilingMPTInternals
81 traces the internals of the method parameter trace
82 -XtraceProfilingMPTModifiers
83 traces the modifiers of the method parameter trace
84 -XtraceProfilingSyncBasics
85 traces basics of the synchronization trace
86 -XtraceProfilingIOBasics
87 traces basics of the profiling I/O trace
88 -XtraceProfilingNetBasics
89 traces basics of the profiling network trace
90 -XtraceChunkedProfilingFile
91 traces operations of chunked profiling files
92 -XtraceAllocLocalMisc
93 traces allocations referrering to local misc
94 -XtraceAllocSharedData
95 traces allocations referring to shared data
96 -XtraceAllocSharedMisc
97 traces allocations referring to shared misc data
98 -XtraceAllocSharedBootstrap
99 traces bootstrap allocations
100 -XtraceAllocAny traces any allocation
101 -XtraceGCOneLineExperimental
102 internal GC trace, do not use
103 -XtraceGCStatisticLevel1
104 traces GCs (basics)
105 -XtraceGCStatisticLevel2
106 traces GCS (detailed)
107 -XtraceGCStatisticLevel3
108 traces Gcs (detailed + basic event information)
109 -XtraceGCStatisticLevel4
110 traces GCs (detailed + detailed event information)
111 -XtraceGCStatisticLevel5
112 traces GCs (detailed + basic reference handling information)
113 -XtraceExceptionsWithByteCode
114 traces exceptions with byte code excerpt for top frames
115 -XtraceMethodsWithParameters
116 traces method calls and prints their parameters
117 -XtraceExtStackTrace
118 traces handling of extendes stack traces
119 -XtraceDetailedClassStatistic
120 traces detailed class statistics after full GCs
121 -XtraceGCStatisticLevel6
122 traces GCs (detailed + detailed reference handling
123 information)
124 -XtraceHeapManager
125 traces information about the heap manager
126 -XtraceHeapManagerInternals
127 traces internals about the heap manager
128 -XtraceOsMisc traces miscellaneous OS internals
129 -XtraceOsMmap traces miscellaneous OS internals (mmap/mprotects etc)
130 -XtraceOsSignals traces miscellaneous OS internals (signal handling)
131 -XtraceProfilingStackTrace
132 traces stack trace handling in profiling
133 -XtraceProfilingStackTraceInternals
134 traces internals of stack trace handling in profiling
135 -XtraceByteCodeUtils
136 traces byte code utils (e.g. used for extended exception
137 messages)
138 -XtraceByteCodeUtilsInternals
139 traces byte code utils (e.g. used for extended exception
140 messages)
141 -XtraceProfilingTimeBasedSampling
142 traces time based sampling in profiling
143 -XtraceProfilingTimeBasedSamplingInternals
144 traces internals of time based sampling in profiling
145 -XtraceVmInit traces internals of VM initialization
146 -XtraceSharedSynchronization
147 traces shared synchronization operations
148 -XtraceOsDllLoad traces resolution/loads of shared objects
149 -XtraceJavaZipOpenClose
150 traces open/close operations of zip files from Java
151 -XtraceJavaZipGetEntry
152 traces getEntry operations of zip files from Java
153 -XtraceJVMTI traces JVMTI operations
154 -XtraceJdkInternals
155 traces JDK internals
156 -XtraceIoStatInternals
157 traces internals about the iostat layer
158 -XtraceMonitoringInternals
159 traces internals about the SAPJVM monitoring
160 -XtraceHeartBeat traces heart beat events
161 -XtraceRainyDayFund
162 traces the memory rainy day fund
163 -XtraceJVMTIStackTraceRetrieval
164 traces the rfetrieval of stack traces by JVMTI
165 -XtraceClassDefinitionTiming
166 traces timing of the class definition
Edited by: Hans Bhargava on Jul 18, 2011 9:09 AM
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Sunny -
Thank you for your quick response. I will have to ask a beginner's question now, but how do I restart the system manually? Is that just the startsap/stopsap scripts that I need to run?
How would I know if the server0 is actually up and running after restarting?
Also, Here is the dev_server0 log (I am posting snippets of the logs as they repeat):
1
2 -
3 trc file: "/usr/sap/OSM/DVEBMGS00/work/dev_server0", trc level: 1, release: "700"
4 -
5 node name : ID3888650
6 pid : 5639
7 system name : OSM
8 system nr. : 00
9 started at : Thu Jul 14 16:28:59 2011
10 arguments :
11 arg[00] : /usr/sap/OSM/DVEBMGS00/exe/jlaunch
12 arg[01] : pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
13 arg[02] : -DSAPINFO=OSM_00_server
14 arg[03] : pf=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
15 arg[04] : -DSAPSTART=1
16 arg[05] : -DCONNECT_PORT=60140
17 arg[06] : -DSAPSYSTEM=00
18 arg[07] : -DSAPSYSTEMNAME=OSM
19 arg[08] : -DSAPMYNAME=atl-osm-01_OSM_00
20 arg[09] : -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
21 arg[10] : -DFRFC_FALLBACK=ON
22 arg[11] : -DFRFC_FALLBACK_HOST=localhost
23
24
25 [Thr 47057802424304] Thu Jul 14 16:28:59 2011
26 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.box.number=OSMDVEBMGS00atl-osm-01] [jstartxx_mt. 841]
27 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.en.host=atl-osm-01] [jstartxx_mt. 841]
28 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 841]
29 [Thr 47057802424304] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx_mt. 841]
30
31 **********************************************************************
32 JStartupReadInstanceProperties: read instance properties [/usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties]
33 -> ms host : atl-osm-01
34 -> ms port : 3901
35 -> OS libs : /usr/sap/OSM/DVEBMGS00/j2ee/os_libs
36 -> Admin URL :
37 -> run mode : NORMAL
38 -> run action : NONE
39 -> enabled : yes
40 **********************************************************************
41
42
43 **********************************************************************
44 Used property files
45 -> files [00] : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
46 **********************************************************************
46 **********************************************************************
47
48 **********************************************************************
49 Instance properties
50 -> ms host : atl-osm-01
51 -> ms port : 3901
52 -> os libs : /usr/sap/OSM/DVEBMGS00/j2ee/os_libs
53 -> admin URL :
54 -> run mode : NORMAL
55 -> run action : NONE
56 -> enabled : yes
57 **********************************************************************
58
59 **********************************************************************
60 Bootstrap nodes
61 -> [00] bootstrap : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
62 -> [01] bootstrap_ID3888600 : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
63 -> [02] bootstrap_ID3888650 : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
64 **********************************************************************
65
66 **********************************************************************
67 Worker nodes
68 -> [00] ID3888600 : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
69 -> [01] ID3888650 : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/instance.properties
70 **********************************************************************
71
72 [Thr 47057802424304] JLaunchRequestQueueInit: create named pipe for ipc
73 [Thr 47057802424304] JLaunchRequestQueueInit: create pipe listener thread
74 [Thr 1115011392] WaitSyncSemThread: Thread 1115011392 started as semaphore monitor thread.
75 [Thr 1104521536] JLaunchRequestFunc: Thread 1104521536 started as listener thread for np messages.
76 [Thr 47057802424304] SigISetDefaultAction : default handling for signal 17
77
78 [Thr 47057802424304] Thu Jul 14 16:29:00 2011
79 [Thr 47057802424304] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
80 [Thr 47057802424304] CPIC (version=700.2006.09.13)
81 [Thr 47057802424304] [Node: server0] java home is set by profile parameter
82 Java Home: /opt/java/java
83 [Thr 47057802424304] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/OSM/DVEBMGS00/exe/jvmx.jar
84
85 **********************************************************************
86 JStartupIReadSection: read node properties [ID3888650]
87 -> node name : server0
88 -> node type : server
89 -> node execute : yes
90 -> jlaunch parameters :
91 -> java path : /opt/java/java
92 -> java parameters : -verbose:gc -Xtrace -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap. engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.eng ine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Xmn400m -XX:PermSize=2048m -XX:MaxPermSize=2048m -Dorg.omg.PortableInterceptor.ORBInitializerClass.co m.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
93 -> java vm version : 4.1.009 17.0-b16
94 -> java vm vendor : SAP Java Server VM (SAP AG)
95 -> java vm type : server
96 -> java vm cpu : amd64
97 -> heap size : 2048M
98 -> init heap size : 2048M
99 -> root path : /usr/sap/OSM/DVEBMGS00/j2ee/cluster/server0
100 -> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
101 -> OS libs path : /usr/sap/OSM/DVEBMGS00/j2ee/os_libs
102 -> main class : com.sap.engine.boot.Start
103 -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
104 -> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
105 -> framework path : /usr/sap/OSM/DVEBMGS00/exe/jstartup.jar:/usr/sap/OSM/DVEBMGS00/exe/jvmx.jar
106 -> shutdown class : com.sap.engine.boot.Start
107 -> parameters :
108 -> debuggable : no
109 -> debug mode : no
110 -> debug port : 50021
111 -> shutdown timeout : 120000
112 **********************************************************************
113
114 [Thr 47057802424304] JLaunchISetDebugMode: set debug mode [no]
115 [Thr 1101179200] JLaunchIStartFunc: Thread 1101179200 started as Java VM thread.
116
117 **********************************************************************
118 JHVM_LoadJavaVM: VM Arguments of node [server0]
119 -> stack : 1048576 Bytes
120 -> arg[ 0]: exit
121 -> arg[ 1]: abort
122 -> arg[ 2]: vfprintf
123 -> arg[ 3]: -verbose:gc
124 -> arg[ 4]: -Xtrace
125 -> arg[ 5]: -Djava.security.policy=./java.policy
126 -> arg[ 6]: -Djava.security.egd=file:/dev/urandom
127 -> arg[ 7]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
128 -> arg[ 8]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
129 -> arg[ 9]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
130 -> arg[ 10]: -Djco.jarm=1
131 -> arg[ 11]: -Xmn400m
132 -> arg[ 12]: -XX:PermSize=2048m
133 -> arg[ 13]: -XX:MaxPermSize=2048m
134 -> arg[ 14]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
135 -> arg[ 15]: -Dsys.global.dir=/usr/sap/OSM/SYS/global
136 -> arg[ 16]: -Dapplication.home=/usr/sap/OSM/DVEBMGS00/exe
137 -> arg[ 17]: -Djava.class.path=/usr/sap/OSM/DVEBMGS00/exe/jstartup.jar:/usr/sap/OSM/DVEBMGS00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin /system/bytecode.jar:.
138 -> arg[ 18]: -Djava.library.path=/opt/java/sapjvm_4/jre/lib/amd64/server:/opt/java/sapjvm_4/jre/lib/amd64:/opt/java/sapjvm_4/jre/../lib/amd64:/usr/sap/O SM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/tmp/sapinst_exe.26924.1310559612:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib:/u sr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/OSM/DVEBMGS00/j2ee/os_libs:/usr/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/DVEBMGS00/exe:/us r/sap/OSM/DVEBMGS00/exe:/usr/sap/OSM/SYS/exe/run:/sapdb/programs/lib
139 -> arg[ 19]: -Dmemory.manager=2048M
140 -> arg[ 20]: -Xmx2048M
141 -> arg[ 21]: -Xms2048M
142 -> arg[ 22]: -DLoadBalanceRestricted=no
143 -> arg[ 23]: -Djstartup.mode=JCONTROL
144 -> arg[ 24]: -Djstartup.ownProcessId=5639
145 -> arg[ 25]: -Djstartup.ownHardwareId=H0868704103
146 -> arg[ 26]: -Djstartup.whoami=server
147 -> arg[ 27]: -Djstartup.debuggable=no
148 -> arg[ 28]: -DSAPINFO=OSM_00_server
149 -> arg[ 29]: -DSAPSTART=1
150 -> arg[ 30]: -DCONNECT_PORT=60140
151 -> arg[ 31]: -DSAPSYSTEM=00
152 -> arg[ 32]: -DSAPSYSTEMNAME=OSM
153 -> arg[ 33]: -DSAPMYNAME=atl-osm-01_OSM_00
154 -> arg[ 34]: -DSAPPROFILE=/usr/sap/OSM/SYS/profile/OSM_DVEBMGS00_atl-osm-01
155 -> arg[ 35]: -DFRFC_FALLBACK=ON
156 -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
157 -> arg[ 37]: -DSAPSTARTUP=1
158 -> arg[ 38]: -DSAPSYSTEM=00
159 -> arg[ 39]: -DSAPSYSTEMNAME=OSM
160 -> arg[ 40]: -DSAPMYNAME=atl-osm-01_OSM_00
161 -> arg[ 41]: -DSAPDBHOST=atl-osm-01
162 -> arg[ 42]: -Dj2ee.dbhost=atl-osm-01
163 **********************************************************************
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,
Error which you pasted above does not seems to be related to problem you are facing.
Please try to restart the system manually and see if system comes up. If not, request you to please paste dev_server0 and std_server0 logs.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- How to use AI services to translate Picklists in SAP SuccessFactors - An example in Technology Blogs by SAP
- Improvising Time Management in SAP S/4HANA Cloud: A Co-Innovation Solution in Technology Blogs by SAP
- ABAP Cloud Developer Trial 2022 Available Now in Technology Blogs by SAP
- SAP Solution Manager System Availability Reports in Technology Q&A
- Upgrade solution manager tool ST release 720 from SP 0009 to SP15 in Technology Q&A
| User | Count |
|---|---|
| 85 | |
| 10 | |
| 10 | |
| 9 | |
| 6 | |
| 6 | |
| 6 | |
| 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.