Operating System - HP-UX
1748065 Members
5268 Online
108758 Solutions
New Discussion юеВ

Re: kmtune: Cannot read number of current kernel parameters

 
J.M. Luo
Occasional Advisor

kmtune: Cannot read number of current kernel parameters

I'm trying to installed OVO 8.1 on HP L2000 Server which has been installed with HP-UX 11.11iv1. But I met the kernel tuning problem. The following are the kmtune output :

#
#
# kmtune
kmtune: Cannot read number of current kernel parameters.
Parameter Current Dyn Planned Module Version
===============================================================================
NSTRBLKSCHED - - 2
NSTREVENT - - 50
NSTRPUSH - - 16
NSTRSCHED - - 0
STRCTLSZ - - 1024
STRMSGSZ - - 65535
acctresume - - 4
acctsuspend - - 2
aio_listio_max - - 256
aio_max_ops - - 2048
aio_physmem_pct - - 10
aio_prio_delta_max - - 20
allocate_fs_swapmap - - 0
alwaysdump - - 1
bootspinlocks - - 256
bufcache_hash_locks - - 128
bufpages - - (NBUF*2)
chanq_hash_locks - - 256
core_addshmem_read - - 0
core_addshmem_write - - 0
create_fastlinks - - 0
dbc_max_pct - - 50
dbc_min_pct - - 5
default_disk_ir - - 0
desfree - - 0
disksort_seconds - - 0
dmp_rootdev_is_vol - - 0
dmp_swapdev_is_vol - - 0
dnlc_hash_locks - - 512
dontdump - - 0
dskless_node - - 0
dst - - 1
effective_maxpid - - ((NPROC<=30000)?30000:(NPROC*5/4))
eisa_io_estimate - - 0x300
enable_idds - - 0
eqmemsize - - 15
executable_stack - - 1
fcp_large_config - - 0
file_pad - - 10
fs_async - - 0
ftable_hash_locks - - 64
hdlpreg_hash_locks - - 128
hfs_max_ra_blocks - - 8
hfs_max_revra_blocks - - 8
hfs_ra_per_disk - - 64
hfs_revra_per_disk - - 64
hp_hfs_mtra_enabled - - 1
hpux_aes_override - - 0
initmodmax - - 50
io_ports_hash_locks - - 64
iomemsize - - 40000
ksi_alloc_max - - (NPROC*8)
ksi_send_max - - 32
lotsfree - - 0
max_async_ports - - 50
max_fcp_reqs - - 512
max_mem_window - - 0
max_thread_proc - - 64
maxdsiz - - 0X40000000
maxdsiz_64bit - - 0X80000000
maxfiles - - 256
maxfiles_lim - - 1024
maxqueuetime - - 0
maxssiz - - 0X8000000
maxssiz_64bit - - 0X40000000
maxswapchunks - - 256
maxtsiz - - 0X04000000
maxtsiz_64bit - - 0X0000000040000000
maxuprc - - 1024
maxusers - - 256
maxvgs - - 10
mesg - - 1
minfree - - 0
modstrmax - - 500
msgmap - - (2+MSGTQL)
msgmax - - 8192
msgmnb - - 16384
msgmni - - 50
msgseg - - 32767
msgssz - - 8
msgtql - - 40
nbuf - - 0
ncallout - - 7500
ncdnode - - 150
nclist - - (100+16*MAXUSERS)
ncsize - - (NINODE+VX_NCSIZE)+(8*DNLC_HASH_LOCKS)
ndilbuffers - - 30
netisr_priority - - -1
netmemmax - - 0
nfile - - (16*(NPROC+16+MAXUSERS)/10+32+2*(NPTY+NSTRPTY+
NSTRTEL))
nflocks - - 4096
nhtbl_scale - - 0
ninode - - ((NPROC+16+MAXUSERS)+32+(2*NPTY))
nkthread - - 7500
nni - - 2
no_lvm_disks - - 0
nproc - - (20+8*MAXUSERS)
npty - - 60
nstrpty - - 60
nstrtel - - 60
nswapdev - - 10
nswapfs - - 10
nsysmap - - ((NPROC)>800?2*(NPROC):800)
nsysmap64 - - ((NPROC)>800?2*(NPROC):800)
o_sync_is_o_dsync - - 0
page_text_to_local - - 0
pfdat_hash_locks - - 128
public_shlibs - - 1
region_hash_locks - - 128
remote_nfs_swap - - 0
rtsched_numpri - - 32
scroll_lines - - 100
scsi_max_qdepth - - 8
scsi_maxphys - - 1048576
sema - - 1
semaem - - 16384
semmap - - (SEMMNI+2)
semmni - - 2048
semmns - - 8192
semmnu - - (SEMMNI-4)
semmsl - - 2048
semume - - 250
semvmx - - 32767
sendfile_max - - 0
shmem - - 1
shmmax - - 2147483648
shmmni - - 512
shmseg - - 400
st_ats_enabled - - 0
st_fail_overruns - - 0
st_large_recs - - 0
st_san_safe - - 0
streampipes - - 0
swapmem_on - - 1
swchunk - - 2048
sysv_hash_locks - - 128
tcphashsz - - 0
timeslice - - (100/10)
timezone - - 420
unlockable_mem - - 0
vas_hash_locks - - 128
vnode_cd_hash_locks - - 128
vnode_hash_locks - - 128
vol_checkpt_default - - 10240
vol_dcm_replay_size - - (256*1024)
vol_default_iodelay - - 50
vol_fmr_logsz - - 4
vol_max_bchain - - 32
vol_max_nconfigs - - 20
vol_max_nlogs - - 20
vol_max_nmpool_sz - - (4*1024*1024)
vol_max_prm_dgs - - 1024
vol_max_rdback_sz - - (4*1024*1024)
vol_max_vol - - (8*1024*1024)
vol_maxio - - 256
vol_maxioctl - - 32768
vol_maxkiocount - - 2048
vol_maxparallelio - - 256
vol_maxspecialio - - 256
vol_maxstablebufsize - - 256
vol_min_lowmem_sz - - (512*1024)
vol_mvr_maxround - - 256
vol_nm_hb_timeout - - (10)
vol_subdisk_num - - 4096
vol_vvr_transport - - (1)
vol_vvr_use_nat - - (0)
volcvm_cluster_size - - 16
volcvm_smartsync - - 1
voldrl_max_drtregs - - 2048
voldrl_min_regionsz - - 512
voliomem_chunk_size - - (64*1024)
voliomem_maxpool_sz - - (4*1024*1024)
voliot_errbuf_dflt - - 16384
voliot_iobuf_default - - 8192
voliot_iobuf_limit - - 131072
voliot_iobuf_max - - 65536
voliot_max_open - - 32
volraid_rsrtransmax - - 1
vps_ceiling - - 64
vps_chatr_ceiling - - 1048576
vps_pagesize - - 4
vx_fancyra_enable - - 0
vx_maxlink - - 32767
vx_ncsize - - 1024
vx_ninode - - 0
vxfs_max_ra_kbytes - - 1024
vxfs_ra_per_disk - - 1024
vxtask_max_monitors - - 32
#
#

IтАЩm use SAM utility to change the kernel parameters values manually and reference to ovo.info.HP-UX.B.11.11 file, after reboot the machine and re-installed OVO still failed at check kernel parameters phase.

Is it HP-UX OS problem or need some patch for it ?

Please help , very thanks !!!

J.M. Luo
12/05/2007
2 REPLIES 2
J.M. Luo
Occasional Advisor

Re: kmtune: Cannot read number of current kernel parameters

Hi, All,

The problem has been solved, please see the following informations:

Defect Description:
PHKL_36362:
( SR:8606451836 CR:JAGag08743 )
The kernel configuration commands, like kmtune are failing
to fetch the current tunable data as the the dynamic
tunable initialization has failed at boot time.
While initializing dyntune, the buffer provided to get
the link stamp from KRS was not enough and there
was no error checking.

Resolution:
Added check to see if the buffer provided is sufficient to
accommodate the link stamp.

PHKL_25368:
( SR:8606205994 CR:JAGad75169 )
The problem was due to an uninitialized variable used to
check the bounds of msgmax. During boot, the value of
msgmax was compared to the uninitialized bounds variable,
and appearing to be out of range, msgmax was reset.

Resolution:
The variable used in bounds checking is now initialized
correctly, prior to its first use.

So, apply PHKL_36362 and reboot machine again, The problem solved.

The orginal information URL is :
http://h50221.www5.hp.com/upassist/itrc_japan/assist2/patchdigest/PHKL_36362.html

regards,

J.M. Luo
12/05/2007
J.M. Luo
Occasional Advisor

Re: kmtune: Cannot read number of current kernel parameters