- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- how to solve memery fault?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 07:44 PM
06-22-2005 07:44 PM
how to solve memery fault?
Pid 29244 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz.
Memory fault(coredump)
OS:HP-UX11.0
how to solve the fault?
thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 08:22 PM
06-22-2005 08:22 PM
Re: how to solve memery fault?
with
'swapinfo -tam'
you can check your memory usage.
If it's too high (90%-100% for example) you need more RAM or SWAP.
But I think it's your kernel - maxssiz.
You can change it in SAM - Kernel Konfiguration - Configurable Parameters.
maxssiz is 100610048 at my server for example.
After modifying the workstation will reboot!
HTH
Volkmar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 08:37 PM
06-22-2005 08:37 PM
Re: how to solve memery fault?
Usually there will be a core file generated when that message coming. You can check the file with command below :
# file core
# strings core
Let me know the output from the command above.
Cheers,
AW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 08:58 PM
06-22-2005 08:58 PM
Re: how to solve memery fault?
1,
# swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 2048 676 1372 33% 0 - 1 /dev/vg00/lvol2
reserve - 1372 -1372
memory 1529 1387 142 91%
total 3577 3435 142 96% - 0 -
2,
# kmtune
Parameter Value
===============================================================================
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 0
bootspinlocks 256
bufcache_hash_locks 128
bufpages (NBUF*2)
chanq_hash_locks 256
create_fastlinks 0
dbc_max_pct 50
dbc_min_pct 5
default_disk_ir 0
desfree 0
disksort_seconds 0
dnlc_hash_locks 64
dontdump 0
dskless_node 0
dst 1
eisa_io_estimate 0x300
eqmemsize 15
fcp_large_config 0
file_pad 10
fs_async 0
ftable_hash_locks 64
hdlpreg_hash_locks 128
hfs_max_ra_blocks 8
hfs_ra_per_disk 64
hpux_aes_override 0
initmodmax 50
io_ports_hash_locks 64
iomemsize 40000
km_disable 0
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*10)
maxdsiz 0X040000000
maxdsiz_64bit 2147483648
maxfiles (60*10)
maxfiles_lim 1024
maxqueuetime 0
maxssiz 0x00800000
maxssiz_64bit 0X0040000000
maxswapchunks (1024*16)
maxtsiz 0X04000000
maxtsiz_64bit 0x0000000040000000
maxuprc (75*8)
maxusers ((32*4)*4)
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 (16+NPROC)
ncdnode 150
nclist (100+16*MAXUSERS)
ncsize (NINODE+VX_NCSIZE)
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 (((NPROC*7)/4)+16)
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)
num_tachyon_adapters 0
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*2-2)
semmap (SEMMNI+2)
semmni ((64*4)*4)
semmns ((128*4)*4)
semmnu ((30*4)*4)
semmsl_override 2048
semume ((10*4)*4)
semvmx (32767*2)
sendfile_max 0
shmem 1
shmmax 0X40000000
shmmni (200*4)
shmseg (120*6)
st_ats_enabled 1
st_fail_overruns 0
st_large_recs 0
streampipes 0
swapmem_on 1
swchunk 2048
sysv_hash_locks 128
tcphashsz 0
timeslice (100/10)
timezone 420
unlockable_mem 0
vnode_cd_hash_locks 128
vnode_hash_locks 128
vps_ceiling 16
vps_chatr_ceiling 65536
vps_pagesize 4
vx_maxlink 32767
vx_ncsize 1024
vx_ninode 0
vx_noifree 0
vxfs_max_ra_kbytes 1024
vxfs_ra_per_disk 1024
3,
# dmesg
Jun 23 15:59
gate64: sysvec_vaddr = 0xc0002000 for 1 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: nfs3_link(): File system was registered at index 5.
0 sba
0/0 lba
0/0/0/0 btlan3
0/0/1/0 c720
0/0/1/0.7 tgt
0/0/1/0.7.0 sctl
0/0/1/1 c720
0/0/1/1.2 tgt
0/0/1/1.2.0 sdisk
0/0/1/1.7 tgt
0/0/1/1.7.0 sctl
0/0/2/0 c720
0/0/2/0.7 tgt
0/0/2/0.7.0 sctl
0/0/2/1 c720
0/0/2/1.2 tgt
0/0/2/1.2.0 sdisk
0/0/2/1.7 tgt
0/0/2/1.7.0 sctl
0/0/4/0 asio0
0/0/5/0 asio0
0/1 lba
0/2 lba
0/3 lba
0/4 lba
0/4/0/0 td
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 0/4/0/0
0/4/0/0.8 fcp
0/4/0/0.8.0.110.0 fcparray
0/4/0/0.8.0.110.0.0 tgt
0/4/0/0.8.0.110.0.0.0 sdisk
0/4/0/0.8.0.110.0.0.1 sdisk
0/4/0/0.8.0.110.0.0.2 sdisk
0/4/0/0.8.0.110.0.0.3 sdisk
0/4/0/0.8.0.110.0.0.4 sdisk
0/4/0/0.8.0.110.0.0.5 sdisk
0/4/0/0.8.0.110.0.0.6 sdisk
0/4/0/0.8.0.110.0.0.7 sdisk
0/4/0/0.8.0.110.0.1 tgt
0/4/0/0.8.0.110.0.1.0 sdisk
0/4/0/0.8.0.110.0.1.1 sdisk
0/4/0/0.8.0.110.0.1.2 sdisk
0/4/0/0.8.0.110.0.1.3 sdisk
0/4/0/0.8.0.255.6 fcpdev
0/4/0/0.8.0.255.6.14 tgt
0/4/0/0.8.0.255.6.14.0 sctl
0/5 lba
0/6 lba
0/7 lba
8 memory
160 processor
166 processor
btlan3: Initializing 10/100BASE-TX card at 0/0/0/0....
System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 4194304
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x12000; start = 158560, size = 2097152
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PST 1997
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 2097152 Kbytes, lockable: 1561212 Kbytes, available: 1800460 Kbyte
s
btlan3: NOTE: MII Link Status Not OK - Switch Connection to AUI at 0/0/0/0....
btlan3: Reset looper timeout: DMA timeout occurred at 0/0/0/0
btlan3: reset state is 550 at 0/0/0/0....
btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....
btlan3: NOTE: MII Link Status Not OK - Switch Connection to AUI at 0/0/0/0....
btlan3: Reset looper timeout: DMA timeout occurred at 0/0/0/0
btlan3: reset state is 550 at 0/0/0/0....
btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....
btlan3: NOTE: MII Link Status Not OK - Switch Connection to AUI at 0/0/0/0....
btlan3: Reset looper timeout: DMA timeout occurred at 0/0/0/0
btlan3: reset state is 550 at 0/0/0/0....
btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....
btlan3: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0
/0/0/0....
NFS server (pid897@/net) not responding still trying
vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
btlan3: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0
/0/0/0....
btlan3: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0
/0/0/0....
Deferred swap reservation failure pid: 17741
Deferred swap reservation failure pid: 17741
Deferred swap reservation failure pid: 17741
Deferred swap reservation failure pid: 17741
Deferred swap reservation failure pid: 24057
Deferred swap reservation failure pid: 24057
Deferred swap reservation failure pid: 24057
Deferred swap reservation failure pid: 24057
Deferred swap reservation failure pid: 11418
Deferred swap reservation failure pid: 11418
Deferred swap reservation failure pid: 11418
Deferred swap reservation failure pid: 27221
Deferred swap reservation failure pid: 27221
Deferred swap reservation failure pid: 27221
Deferred swap reservation failure pid: 27221
Deferred swap reservation failure pid: 29413
Deferred swap reservation failure pid: 29413
Deferred swap reservation failure pid: 29413
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 09:16 PM
06-22-2005 09:16 PM
Re: how to solve memery fault?
well - very much informations ...
your maxssiz is the default value: 0x00800000 is 8388608 - so one tipp is to increase this value.
Then:
/dev/vg00/lvol4 file system full
make a 'bdf' - what is in
/dev/vg00/lvol4? your swap? or /tmp?
you have to delete files there!!
Also your RAM is used to 91% - so you should think about buying more.
And one more command: 'vmstat -n' tells you if your system uses much SWAP - under pi and po you see if your system is swapping.
Then you also should buy RAM.
V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 09:42 PM
06-22-2005 09:42 PM
Re: how to solve memery fault?
maybe also change dbc_max_pct to 9 or 10 and put the dbc_min at maybe 4 or 5
as mentioned from Rita Workman here:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=641435
If you search for 'swap reservation failure' with the ITRC search, you will find many threads with problems like yours.
HTH
Volkmar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 09:54 PM
06-22-2005 09:54 PM
Re: how to solve memery fault?
'ps -el | sort -r -k10 | head -5'
to recognize the 5 processes which need most of your memory.
V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2005 12:44 AM
06-23-2005 12:44 AM
Re: how to solve memery fault?
Then use swapon to add that space temporarily (it will be unused after a reboot) and see if the problem goes away. As mentioned, you are severely short on RAM and if you can't add at least another 1500 megs, at least add more swap space. Note that swapping can impact performance as much as 100:1.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2005 12:52 AM
06-23-2005 12:52 AM
Re: how to solve memery fault?
HP's general recommendation is to have device swap = to at least 2 x RAM.
So I would add 2 GB of swap to your system to fix this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2005 12:27 PM
06-23-2005 12:27 PM
Re: how to solve memery fault?
After much troubleshooting the following steps were used to prevent the error
from occuring:
# cd /usr/lib
# /sbin/ln libc.2 libc.2.saved
# /sbin/rm libc.2; /sbin/ln /usr/lib/pa11_32/libc.2 libc.2
NOTE: The above commands can affect a live production system. There is a small
window between when libc.2 is removed and linked that can cause programs
calling libc.2 to fail. The above procedure should only be performed during a
scheduled downtime or maintenence window.
Regards
Vinod K