SAM problem with C locale

[Paulo A G Fessel]

Gents,

I've just applied the most recent QPK, and everytime I try to enter "Users Administation" on SAM I get the following message:

UNEXPECTED EXIT: process LANG=C LC_ALL=C /usr/sam/lbin/samx -C -p 22079 -s users /usr/sam/lib//ug.ui exited with a non zero exit status. Sorry, you must have superuser (root) privilege to enter SAM.

I've checked up /usr/sam/lib and found that /usr/sam/lib/C/ug.ui exists. So, SAM is confusing itself about where to find certain modules.

I've tried with LANG=C with no results. Any suggestions?

TIA,
Paulo Fessel

[Corthouts Carlo]

Hi,

first try it when logged in as superuser (root)
not when you are doing a "su" to root.

If this does not help you the next best thing is to install the latest SAM patch.

[T. M. Louah]

Sam requires super-user privileges (i.e. root); however, you can set up "Restricted SAM" to allow users to perform certain tasks. Check SAM manpages and search for "Restricted SAM" for details.

Remember PAP (a.k.a Please assign points!)

[Paulo A G Fessel]

Gents,

I'm already logged in as root...

[]'s
Paulo Fessel

[S.K. Chan]

I take it then SAM was working fine until you applied the pathces ? Can you run swverify on SAM and then check /var/adm/sw/swagent.log for any errors ..

# swverify -v SystemAdmin
# tail -50 /var/adm/sw/swagent.log

[Paulo A G Fessel]

Gents,

Trying to debug the problem just found that

/opt/tusc/bin/truss -f -o sam.problem sam

makes SAM works absolutely normal.

Without truss, however, I get the following output:

"SAM internal error.
???
"The error handler has gotten the error code -91827364 of type FATAL with the associated strings:
???
"A system error occurred. open(2) failed. SAM was attempting to open /var/sam/TMeHAAa18955. open(2) set errno = 13."

What is this? Kernel parameters? /var/adm/syslog/syslog.log doesn't show nothing.

TIA
Paulo Fessel

[S.K. Chan]

So swverify output looks normal despite some permission error, that should not be the cause. Don't know much about the tool you used (truss - must have been a freeware debugger ?), anyway this is my observation and a few more suggestions ..

1) You mentioned SAM complaint whenever you enter "Users Admin.." , let's check the integrity of password and group file to make sure they are not corrupted in any way. You need to run "pwck" and "grpck".
2) The error "errno = 13", from /usr/include/sys/errno.h files typically means "permission denied" error. Check permission for /var/sam. I got mine set at 555 (bin:bin).

[Paulo A G Fessel]

Hello.

"truss" is part of "tusc" package. It traces all system calls that a program makes while it's being executed. In my case, I've found that we track only the main process SAM continues to fail; OTOH, if I say truss to follow all forks, SAM runs normally.

Also, I've found that changing permissions of /var/sam to 755 makes user administration possible without using tusc; however, every other screen says "Permission denied; you must be super user to access this section of SAM".

I'm thinking about deinstalling SystemAdmin and installing it again...

TIA
Paulo Fessel

[S.K. Chan]

Paulo, I would think that is what I would do when everything is pretty much exhausted .. tips, when you reinstall SystemAdmin ..

1) Do not select
- Autoselect dependencies when marking sfw
- Enforce dependency analysis errors

2) Select
- Reinstall filesets even same rev is there
- Reinstall files even same one already exist

Doing 1) will allow you to reinstall without needing a reboot. 2) is obvious.

[Paulo A G Fessel]

Problem solved.

For some bizarre reason /bin/sh had SUID set, thus disabling SAM.

Question is: why has this turned up when I applied last QPK?

TIA,
Paulo Fessel

[S.K. Chan]

Bizarre indeed, I guess one need to look closely into the list of patches in QPK especially "security" related patches, those kind of patches could be the culprit here. Bottom line you got it resolved !