Users in SAM not displaying

[Christopher McCray_1]

One of my collegues brought this to my attention. She went into SAM to modify a user account and under Accounts for Users and Groups, the Users selection is not displayed. We can still go into Groups --> List --> Users and the user list appears. Has anyone out there experienced this?? ODD!!!

BTW-- HP-UX 10.20 T-520

Thanks in advance

Chris

[Jeff Schussele]

Hi,

I would suspect SAM has suffered some sort of corruption. I would recommend reloading SAM.

If your SAM patches are not up to date this would be a good time to apply the most current cumulative - PHCO_22268 - here's the link:

http://us-support2.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=4a9246dc048fe0071e?PATCH_PATH=/hp-ux_patches/s700_800/10.X/PHCO_22268&HW=s800&OS=10.20

HTH,
Jeff

[Helen French]

Hi,

Is she using a restricted SAM ? what happens if you login as root and invoke SAM ? Does this happens to all users ?

HTH,
Shiju

[S.K. Chan · Accepted solution]

Sound like you "might" have a corrupted /etc/passwd file entry.
Can you run pwck on your passwd file to check for bad entries (eg: missing fields, format, etc). SAM is very particular about this in order for it to see everything in the passwd file.

[pap]

Hi,

It may be a result of unconfigured filesets. Try this:

# swlist -l fileset -a state | grep -v # | grep -v configured

If this command gives any output then you have unconfigured filesets (likely patches).

Correct with swconfig (execute folloing) :
# usr/sbin/swconfig *

Rerun the swlist command above to see if all or most of the unconfigured filesets are now configured.

After this completes rerun SAM and it should no longer exhibit the same problems.

Hope this helps.

[Christopher McCray_1]

Thanks for your responses

I do not have the latest patch, but the one I have, PHCO_21844 isn't a patch with warnings. I will, however, check it out.

She is not using Restricted SAM, she is logged in as root.

The pwck returned 1 bad block in logname for an account created recently, March 3 so that is probably my problem

There are no unconfigured filesets on my server.

Now for the big question, how to get the bad block out of the passwd file?? I haven't come across this before.

Thanks

[Jeff Schussele]

You have two options:

1) Edit the passwd - USE vipw as it will lock the passwd file so no changes can be made while editing. Remove the offending entry & readd the user.

2) Restore the latest good backup copy of passwd & readd any users added since. It's a good idea to keep a "safe" copy of passwd on the system in a secure location & update it regularly - set a cron to do this daily.

Also ensure that / is not approaching 100% full as this condition causes this problem frequently. If it's close clean it up.

HTH,
Jeff

[Christopher McCray_1]

Sorry Jeff for not rewarding your input sooner.

I tried removing and readding the user and it is still not displaying. I have since read some docs that suggest that the pwck information doesn't necessarily effect sam in this case (an _ in the username). I will look into the patch and see if loading it can be approved, since it doesn't take a reboot after all.

Chris