Sponsored Content
Operating Systems HP-UX User unlock problem in Tru64 4.0F Server Post 302303633 by madanmb on Friday 3rd of April 2009 06:45:03 AM
Old 04-03-2009
Data User unlock problem in Tru64 4.0F Server

Hi Friends

We have two node trucluster Tru64 4.0F Alpha Servers,In one of Tru64 4.0F Unix Server I am unable to unlock users, when I issue usermod command I will get following error

/usr/sbin/usermod -x administrative_lock_applied=0 username
account manager has exited unexpectedly - please file a problem report
Resources lost(coredump)


I am also unable to open Account Manager in Xmanager I am getting the same error message as usermod command.

When I view my /etc/passwd file it's showing some garbage values, I have also rebooted my server but the problem remains same.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Tru64 UNIX log in problem

I'm using Tru64 UNIX 4.0 . I restarted the machine and I tried to log in again as an user I get a message saying No directory!. The system log me in as a superuser. I checked and the directory actually is not there. I'm pretty sure that i didn't deleted it. If someone have a clue of what is... (1 Reply)
Discussion started by: iigp1974
1 Replies

2. UNIX for Advanced & Expert Users

Please Help with Tru64 CDE problem

When using the GUI we are unable to bring up the window for printer. We go through Applications/configuration/print this is the window that will not work all the other windows work ! Would anyone have any idea how to correct this and make the print window appear ???? (0 Replies)
Discussion started by: mlucas
0 Replies

3. Solaris

how to unlock user ID in solaris?

I only able to lock user ID with passwd -l username It seems there is no option for me to unlock ID in solaris? Is there any command as below? passwd -u username Appreciate someome can share with me the way to do it. (1 Reply)
Discussion started by: dwarf007
1 Replies

4. HP-UX

Tru64 How to identify what causes the server to go down?

Hi All, I need some pointers, advice, tips & anything that can help me figure out what's causing our OSF1 xxx.xx.xxx.xxx V5.1 2650 alpha to go down unexpectedly. It's gone down 3 times in the past 5 days. I'm still new to unix administration, so appreciate if you could share your wealth of... (2 Replies)
Discussion started by: rahzzbietel
2 Replies

5. UNIX for Dummies Questions & Answers

Tru64 User administration

Hey guys how do you check if an account is locked in tru64, and how do you unlock it? (1 Reply)
Discussion started by: sbn
1 Replies

6. UNIX for Dummies Questions & Answers

Unable to unlock users in Tru64

Hi Friends We have two node trucluster Tru64 4.0F Alpha Servers,In one of Tru64 4.0F Unix Server I am unable to unlock users, when I issue usermod command I will get following error /usr/sbin/usermod -x administrative_lock_applied=0 username account manager has exited unexpectedly - please... (0 Replies)
Discussion started by: madanmb
0 Replies

7. HP-UX

not able to unlock user

Hi, not able to unlock user eventhough executed /usr/lbin/modprpw -k username Thanks in advance (2 Replies)
Discussion started by: bpsunadm
2 Replies

8. HP-UX

Problem with vdump command on TRU64

Hi all, I have a system with TRU64 system (quite old). I use to run script to make save of important system partitions. The command to save the partition "/" is : /sbin/vdump -0uDf /mnt/Sauvegarde/dump/slash.dump.0 /. (/mnt/Sauvegarde is NFS mounted, but this is no matter) This script ran for... (0 Replies)
Discussion started by: aribault
0 Replies

9. Red Hat

PAM: Unlock user account after 30mins

Hi We have these specific requirements for a bunch of servers we have and cannot seem to get pam to behave in this way. We would like: PAM locks accounts if pam tally reaches 10. PAM unlocks the account after 30mins from locking it, and resets the pam_tally. The key is that we don't... (0 Replies)
Discussion started by: snoop2048
0 Replies
PWCK(8) 						    System Management Commands							   PWCK(8)

NAME
pwck - verify integrity of password files SYNOPSIS
pwck [-q] [-s] [passwd [ shadow ]] pwck [-q] [-r] [passwd [ shadow ]] DESCRIPTION
The pwck command verifies the integrity of the users and authentication information. It checks that all entries in /etc/passwd and /etc/shadow have the proper format and contain valid data. The user is prompted to delete entries that are improperly formatted or which have other uncorrectable errors. Checks are made to verify that each entry has: o the correct number of fields o a unique and valid user name o a valid user and group identifier o a valid primary group o a valid home directory o a valid login shell shadow checks are enabled when a second file parameter is specified or when /etc/shadow exists on the system. These checks are the following: o every passwd entry has a matching shadow entry, and every shadow entry has a matching passwd entry o passwords are specified in the shadowed file o shadow entries have the correct number of fields o shadow entries are unique in shadow o the last password changes are not in the future The checks for correct number of fields and unique user name are fatal. If the entry has the wrong number of fields, the user will be prompted to delete the entire line. If the user does not answer affirmatively, all further checks are bypassed. An entry with a duplicated user name is prompted for deletion, but the remaining checks will still be made. All other errors are warning and the user is encouraged to run the usermod command to correct the error. The commands which operate on the /etc/passwd file are not able to alter corrupted or duplicated entries. pwck should be used in those circumstances to remove the offending entry. OPTIONS
The options which apply to the pwck command are: -q Report errors only. The warnings which do not require any action from the user won't be displayed. -r Execute the pwck command in read-only mode. -s Sort entries in /etc/passwd and /etc/shadow by UID. By default, pwck operates on the files /etc/passwd and /etc/shadow. The user may select alternate files with the passwd and shadow parameters. CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool: PASS_MAX_DAYS (number) The maximum number of days a password may be used. If the password is older than this, a password change will be forced. If not specified, -1 will be assumed (which disables the restriction). PASS_MIN_DAYS (number) The minimum number of days allowed between password changes. Any password changes attempted sooner than this will be rejected. If not specified, -1 will be assumed (which disables the restriction). PASS_WARN_AGE (number) The number of days warning given before a password expires. A zero means warning is given only upon the day of expiration, a negative value means no warning is given. If not specified, no warning will be provided. FILES
/etc/group Group account information. /etc/passwd User account information. /etc/shadow Secure user account information. EXIT VALUES
The pwck command exits with the following values: 0 success 1 invalid command syntax 2 one or more bad password entries 3 can't open password files 4 can't lock password files 5 can't update password files 6 can't sort password files SEE ALSO
group(5), grpck(8), passwd(5), shadow(5), usermod(8). System Management Commands 06/24/2011 PWCK(8)
All times are GMT -4. The time now is 03:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy