topic Re: SAM does not work. in Operating System - HP-UX

SAM does not work.

Francisco J. Soler — Tue, 19 Sep 2000 09:50:37 GMT

When i try to run sam, i've got the message, memory fault, core dumped.
I need to install some patches, and the swinstall does not run, with the same message. Memory fault, core dumped.
The OS is HP-UX 10.20 and the hardware is an HP9000 715/33.
I've installed the HP-UX from the begining and imediately i try to run sam with no success.
Any sugestions?

Frank.

Re: SAM does not work.

Alex Glennie — Tue, 19 Sep 2000 09:55:29 GMT

first thing i'd do is get the latest sam patches installed , what patches have you on the box, swlist -l fileset grep PH

Re: SAM does not work.

Vincente Fernandes — Tue, 19 Sep 2000 10:04:30 GMT

From root trying stoping/starting swagentd daemon. "/sbin/init.d/swagentd stop/start" and trying running sam again. If that doesn't work try running swconfig too.

Re: SAM does not work.

Alex Glennie — Tue, 19 Sep 2000 10:05:45 GMT

Frank does sam fail when you run it from the command line immediately or when you try to configure something ?

It maybe worth your while :

upping Maxdsiz or posting its size to this forum for confirmation .... ?

Also .....

1. cd /var/adm/sw/queue

2. mv number number.old

3. touch number

Re: SAM does not work.

Cheryl Griffin — Tue, 19 Sep 2000 10:30:34 GMT

Francisco,
When SAM core dumps, it could be for any reason. Look at the message it gave you.

It will be something similar to:
unexpected exit: process LANG=C LC_ALL=C /usr/bin/lbin/samx -C -p3411 /usr/sam/lib//tm.ui exited with non-zero exit status sh:3528 bus error, core dump

The important part of this message is the /usr/sam/lib//tm.ui. If you can give me this portion of your message, I may be able to give you a specific fix.

In many cases, it may be an unconfigured fileset:
# swlist -l fileset -a state (look for installed, transient or corrupt)
# swconfig * (to configure all installed filesets)

Or it may be a patch issue. In the error listed above, it is actually an offending line in /etc/inittab that caused the error.
Without the exact message, we are guessing what the problem is.