on 06-27-2007 10:28 AM
Can anyone help?
I am installing Solution manager 4.0 on a Solarsi 9 unix system and the installation has errored at step 25 Start Instance. I have done a retry but still the same.
The error in the log file is :
ERROR 2007-06-27 09:59:55
CJSlibModule::writeError_impl()
CJS-30105 Instance SM1/DVEBMGS00 reached state UNKNOWN after having state STARTING. Giving up.
ERROR 2007-06-27 09:59:55 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|1|0|start was executed with status ERROR .
Thanks
Steve
Here are my /etc/system file settings.
I am going to change the shmmax setting to the lower one and reboot. My assumption is that since this is a new install the kernel support package in the sap note 499759 won't have been applied. I hope that when I restart the installation it is still able to continue on from where it left off.
ident "@(#)system 1.18 97/06/27 SMI" / SVR4 1.5 */
*
SYSTEM SPECIFICATION FILE
*
moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
SAP settings for all Solaris releases
set msgsys:msginfo_msgmax=8192
set msgsys:msginfo_msgmnb=16384
set msgsys:msginfo_msgmni=50
set msgsys:msginfo_msgtql=2048
set semsys:seminfo_semmns=16384
set semsys:seminfo_semmni=1024
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semopm=100
set semsys:seminfo_semume=64
set semsys:seminfo_semmsl=2048
set shmsys:shminfo_shmmni=256
SAP settings for Solaris in 64-bit mode
set shmsys:shminfo_shmmax=0xffffffffffffffff
OR, if support package for SAP note 499759 has not been implemented
set shmsys:shminfo_shmmax=8589934590
only for Solaris 8 and lower (Solaris 9 and higher: default is 65535)
set rlim_fd_max=8192
for all Solaris releases
set rlim_fd_cur=8192
Tune the TCP stack for EP 6.0 on 64bit Solaris
set tcp:tcp_conn_hash_size=32768
set tcp_tcp_time_wait_interval=60000
End of SAP specific settings
Begin MDD root info (do not edit)
forceload: misc/md_trans
forceload: misc/md_raid
forceload: misc/md_hotspares
forceload: misc/md_sp
forceload: misc/md_stripe
forceload: misc/md_mirror
forceload: drv/pcipsy
forceload: drv/glm
forceload: drv/sd
rootdev:/pseudo/md@0:0,0,blk
End MDD root info (do not edit)
Thanks
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Markus
Looking in the dev_w0 trace file I find the following :
M SHM_PRES_BUF (addr: 0xffffffff7517a000, size: 4400000)
I *** ERROR => shmget(10009,134217728,992) (12: Not enough space) [shmux.c 1543]
M *** ERROR => ThShMCreate: ShmCreate SHM_ROLL_AREA_KEY failed [thxxhead.c 2538]
M *** ERROR => ThIPCInit: ThShMCreate [thxxhead.c 2037]
M ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c 1494]
M in_ThErrHandle: 1
M *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c 10156]
Do you have any idea how I can correct this please?
Thanks
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> M SHM_PRES_BUF (addr: 0xffffffff7517a000, size:
> 4400000)
> I *** ERROR => shmget(10009,134217728,992) (12: Not
> enough space) [shmux.c 1543]
> M *** ERROR => ThShMCreate: ShmCreate
> SHM_ROLL_AREA_KEY failed [thxxhead.c 2538]
> M *** ERROR => ThIPCInit: ThShMCreate [thxxhead.c
> 2037]
> ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001)
> [thxxhead.c 1494]
> in_ThErrHandle: 1
> *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17,
> action 3, level 1) [thxxhead.c 10156]
>
What are your settings in /etc/system?
--
Markus
You ABAP instance is not coming up.
check dev_disp and dev_w0 for possible errors and if in doubts, copy them here.
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
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.