topic Re: SAM in Operating System - HP-UX

SAM

Michael J Adrian — Wed, 20 Sep 2000 21:13:57 GMT

James:
The scripts are working fine after the link problem.

I did the 'swlist -l fileset -a state|grep -i SystemAdmin'. Nothing was displayed as "configured". Do I reinstall SAM from the "Core-OS" cdrom??

Mike.

Re: SAM

Tim Malnati — Wed, 20 Sep 2000 21:53:49 GMT

Michael, I tried to do a quick search for your original question and found nothing. Is this a continuation of a support call? If it is, there is little chance that 'James' will find it unless he happens to be watching the forums himself. Or maybe the forum system has lost the original thread somehow?

From what I can see, it seems that SAM might not be installed on your system (very unusual) or maybe it's broke? Or maybe the INDEX of SD is corrupted? With a little more info we might be able to help.

Re: SAM

James R. Ferguson — Wed, 20 Sep 2000 23:31:25 GMT

Hi:

Thanks, TIM. The thread to which Michael refers is from the 9000 board:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xf0ea6c96588ad4118fef0090279cd0f9,00.html

I asked Michael to (re)post here to allow more contributions than mine. It looks to me like there may have been several problems, the first of which were missing links (now solved).

It now looks from Michael's last post (summarized here) that SAM may not be configured.

MICHAEL: Please post the output of the swlist I requested. Thanks, Jim.

...JRF...

Re: SAM

Tim Malnati — Thu, 21 Sep 2000 02:59:42 GMT

I've run into a variety of problems created as a result of having a umask set with the swinstall process (in many cases it is inherited). The permissions showing on the link in the other thread suggests that his umask is currently not allowing permission for 'other'. Not that a link controls permissions, but it is a good indication of what the umask was at the time of creation. If I recall correctly, SAM is one of the processes that is somewhat sensitive to permissions. I've had more than one support call related to swinstall with a umask, and seem to recall one I made that showed similar behavior after installing a SAM cumulative. I would suggest 'umask 0' instead. A while back (> year) I suggested an SR to correct this behavior, but I have no idea where it went. After this is corrected, it might be a good idea to perform an swverify which will check installed permissions. swverify is not infalible though. Some of the permissions and ownerships are not always consistent (or correct). But it's better than nothing.

Re: SAM

James R. Ferguson — Thu, 21 Sep 2000 08:06:33 GMT

Michael:

Another question for you. Was your server a 10.x server on which you did an upgrade (not cold install) to 11.x ?

...JRF...

Re: SAM

Michael J Adrian — Thu, 21 Sep 2000 14:30:31 GMT

James:

SAM was working up until around Sep 11th.

Now the screen simply displays 'Initializing Sam...'

The 'swlist -l fileset -a state|grep -i SystemAdmin' yields nothing.

Our server was not a 10.x, it was initially installed as 11.0

Mike.

Re: SAM

James R. Ferguson — Thu, 21 Sep 2000 15:46:49 GMT

Michael:

Please issue the following and post the results:

# swlist -l fileset -a state|grep -i SystemAdmin;echo $?

Something happened on the 11th as your post indicates. From our previous thread, someone or something appears to have obliterated some key links which we think are now fixed.

What else have you found besides SAM that isn't working or doesn't appear to be working?

...JRF...