1836226 Members
2982 Online
110096 Solutions
New Discussion

SAM dumps core

 
Venu Raja
Occasional Contributor

SAM dumps core

Hi experts,

Could anyone please tell me why SAM dumps core.

This is what i got from what core:

SAM Infrastructure Version 2.0 - 11/13/96 10:42:14
SAM file editing library $Revision: 72.2 $
HP DCE/9000 1.5 PHSS_19739-40 Module: libdce.sl (Export) Date: Sep 6 19
99 18:22:15
rec_seq.c 8.2 (Berkeley) 9/7/93
libXOM 1.9 (BULL S.A) 7/1/92
$RCSfile: environment.c,v $ $Revision: /main/HPDCE02/2 $ (OSF) $Date: 19
94/12/05 19:53 UTC $
PATCH-PHCO_23684 for 10.20; for 10.30, 11.x compatibility libc.1_ID@@/m
ain/r10dav/libc_dav/libc_dav_cpe//1
/ux/core/libs/libc/shared_pa1/libc.1_ID
May 2 2001 14:37:28
SMART_BIND
92453-07 dld dld dld.sl B.10.12 960426

Thanks in advance
6 REPLIES 6
Steve Steel
Honored Contributor

Re: SAM dumps core

Hi

1)Make sure you have these

PHCO_22268 Cumulative SAM/ObAM Patch
PHCO_25640 libc cumulative patch
PHSS_19739 HP DCE/9000 1.5 cumulative patch

2)What does file core
give

3)what were you doing when it dumped

4)What is in the samlog

sam
view samlog

steve steel
If you want truly to understand something, try to change it. (Kurt Lewin)
harry d brown jr
Honored Contributor

Re: SAM dumps core


Have you contemplated installing the latest patch bundle???

live free or die
harry
Live Free or Die
Cheryl Griffin
Honored Contributor

Re: SAM dumps core

Where did SAM core? When you first started it or by selecting an area within SAM?

If it cores when you first start SAM, you have to look at things like /etc/inittab and ioscan for errors, as SAM does a lot of system checks when it first starts.

If it cores when attempting to access a specific area, you have to look at that area.

Make sure SAM is correctly configured:
# swverify SystemAdmin

# check_patches

If you let us know where it cores, we can assist further.

Cheryl
"Downtime is a Crime."
Venu Raja
Occasional Contributor

Re: SAM dumps core

Thanks for the reply. Our system is HP9000 unix server with 10.20. We have UNIFY 2000 database running in this server. I got that dump when i tried to run the database.

for eg: > unison

And as for installing patches goes swinstall, swverify, sam all these gives me a core dump.

These are the core details i got after swverify:

what core
core:
$Revision: 5.2, SD-OV/A.01.01, SD-UX/B.10.20, CONTROLLER, Optimized, Bu
ilt May 17 1996 16:00:27$
ttadjdsa.c $Date: 96/03/12 15:46:32 $ $Revision: 5.4 $
HP DCE/9000 1.5 PHSS_19739-40 Module: libdce.sl (Export) Date: Sep 6 19
99 18:22:15
rec_seq.c 8.2 (Berkeley) 9/7/93
libXOM 1.9 (BULL S.A) 7/1/92
$RCSfile: environment.c,v $ $Revision: /main/HPDCE02/2 $ (OSF) $Date: 19
94/12/05 19:53 UTC $
PATCH-PHCO_23684 for 10.20; for 10.30, 11.x compatibility libc.1_ID@@/m
ain/r10dav/libc_dav/libc_dav_cpe//1
/ux/core/libs/libc/shared_pa1/libc.1_ID
May 2 2001 14:37:28
Dialog Manager IDMuser.h Version 2.18i
ObAM Version 4.1.8 OBAM4_1_8 product SysV.4 (build date: Thu Apr 23 17:1
9:03 MDT 1998)
HP-UX libm shared PA1.0 C math library 960420 (111936) UX 10.20
SMART_BIND
92453-07 dld dld dld.sl B.10.12 960426

This is what i got after swinstall:

what core
core:
$Revision: 5.2, SD-OV/A.01.01, SD-UX/B.10.20, CONTROLLER, Optimized, Bu
ilt May 17 1996 16:00:27$
ttadjdsa.c $Date: 96/03/12 15:46:32 $ $Revision: 5.4 $
HP DCE/9000 1.5 PHSS_19739-40 Module: libdce.sl (Export) Date: Sep 6 19
99 18:22:15
rec_seq.c 8.2 (Berkeley) 9/7/93
libXOM 1.9 (BULL S.A) 7/1/92
$RCSfile: environment.c,v $ $Revision: /main/HPDCE02/2 $ (OSF) $Date: 19
94/12/05 19:53 UTC $
PATCH-PHCO_23684 for 10.20; for 10.30, 11.x compatibility libc.1_ID@@/m
ain/r10dav/libc_dav/libc_dav_cpe//1
/ux/core/libs/libc/shared_pa1/libc.1_ID
May 2 2001 14:37:28
Dialog Manager IDMuser.h Version 2.18i
ObAM Version 4.1.8 OBAM4_1_8 product SysV.4 (build date: Thu Apr 23 17:1
9:03 MDT 1998)
HP-UX libm shared PA1.0 C math library 960420 (111936) UX 10.20
SMART_BIND
92453-07 dld dld dld.sl B.10.12 960426

When i try to reboot the machine swagentd doesn't start. When i checked rc.log i found out that swagentd has issued a core dump. Type of error: "looks like daemon already running".

I will check whether the patches you guys mentioned has been installed or not, and will reply in a little bit.

Thanks in advance
Cheryl Griffin
Honored Contributor

Re: SAM dumps core

ITRC Knowledge Base doc TFKBRC00004811 says that when multiple commands (SAM. swinstall, swremove, etc) core dump, that a possible cause is a hw failure.

Look at /var/adm/syslog/syslog.log and dmesg for errors. If you have diagnostics (STM) installed, use this as well to uncover the problem.

Cheryl
"Downtime is a Crime."
Venu Raja
Occasional Contributor

Re: SAM dumps core

Thanks again,

Just wanted to feed some more information, this server was working fine before installing
these three patches:

phco_23684
phco_19798
phss_23672

as swremove is not working iam not able to remove 'em.

Iam also copying the output from dmesg, in case if it is of any help (as i found no errors in sys.log and dmesg)

>dmesg
Aug 27 10:47
vuseg=1429000
inet_clts:ok inet_cots:ok 8 bc
8/0 bc
8/0/0 mux2
8/4 c720
8/4.4 tgt
8/4.4.0 sdisk
8/4.7 tgt
8/4.7.0 sctl
8/4.8 tgt
8/4.8.0 sdisk
8/4.9 tgt
8/4.9.0 sdisk
8/4.10 tgt
8/4.10.0 sdisk
8/16 bus_adapter
8/16/5 c720
8/16/5.0 tgt
8/16/5.0.0 stape
8/16/5.2 tgt
8/16/5.2.0 sdisk
8/16/5.7 tgt
8/16/5.7.0 sctl
8/16/6 lan2
8/16/0 CentIf
ps2_readbyte_timeout: no byte after 500 uSec
ps2_readbyte_timeout: no byte after 500 uSec
8/16/7 ps2
8/20 bus_adapter
8/20/5 eisa
8/20/5/1 eisa_mux0
8/20/2 asio0
62 processor
63 memory
HP EISA Mux Device Driver, FILESET EISA-MUX-KRN Version B.10.20.05
Copyright (c) 1997 Hewlett-Packard Company
eisa_mux0: Driver Enabled for board 1 at HW path (8/20/5/1).
Networking memory for fragment reassembly is restricted to 23523328 bytes
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 = 1048576
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x4000; start = 314207, size = 262145
Starting the STREAMS daemons.
9245XB HP-UX (B.10.20) #1: Sun Jun 9 06:31:19 PDT 1996

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 262144 Kbytes, lockable: 192360 Kbytes, available: 223576 Kbytes

Thanks in advance