User unlock problem in Tru64 4.0F Server


 
Thread Tools Search this Thread
Operating Systems HP-UX User unlock problem in Tru64 4.0F Server
# 1  
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.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

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. 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

7. 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

8. 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

9. 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
Login or Register to Ask a Question
logger(1)						      General Commands Manual							 logger(1)

NAME
logger - Makes entries in the system log SYNOPSIS
/usr/bin/logger [-f file] [-i] [-p[facility.]priority] [-t tag] [message...] logger [-b] [message...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: logger: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
[Tru64 UNIX] Logs the informational message to the binary event logger instead of the syslog() subroutine and enters information in the binary event log file. The uerf command with the -r 250 option reports the informational messages that are in the binary event log file, which is used for system maintenance and troubleshooting. The -b option cannot be used with any other options. [Tru64 UNIX] Logs all lines in file. [Tru64 UNIX] Logs the process ID (PID) of the logger process with each line. [Tru64 UNIX] Enters the message with the specified priority and, if specified, from the specified facility. [Tru64 UNIX] You can specify priority as either an alphabetic string or its integer equivalent. You can specify the following val- ues for the priority variable: [Tru64 UNIX] (0) [Tru64 UNIX] The system is unusable. (0) [Tru64 UNIX] Action must be taken imme- diately. (1) [Tru64 UNIX] Critical conditions. (2) [Tru64 UNIX] Error conditions. (3) [Tru64 UNIX] (3) [Tru64 UNIX] (4) [Tru64 UNIX] Warning conditions. (4) [Tru64 UNIX] Normal but significant condition. (5) [Tru64 UNIX] Informational. (6) [Tru64 UNIX] Debug-level messages. (7) [Tru64 UNIX] You can also specify a value for the facility variable, which indicates the source of the event. You can specify facility as either an alphabetic string or its integer equivalent. The integer values appear in parentheses. You can specify the following values for the facility variable: [Tru64 UNIX] Kernel messages. (0) [Tru64 UNIX] Random user-level messages. (8) [Tru64 UNIX] Mail system. (16) [Tru64 UNIX] System daemons. (24) [Tru64 UNIX] Security/authorization messages. (32) [Tru64 UNIX] (32) [Tru64 UNIX] Messages syslogd generates internally. (40) [Tru64 UNIX] Line printer subsystem. (48) [Tru64 UNIX] Network news subsystem. (56) [Tru64 UNIX] UUCP subsystem. (64) [Tru64 UNIX] Clock daemon. (72) [Tru64 UNIX] (128) [Tru64 UNIX] (136) [Tru64 UNIX] (144) [Tru64 UNIX] (152) [Tru64 UNIX] (160) [Tru64 UNIX] (168) [Tru64 UNIX] (176) [Tru64 UNIX] (184) [Tru64 UNIX] Precedes each entry in the log with tag. OPERANDS
You can specify the message to be used for entries on the command line or with the -f file option, which specifies that each line in file be logged as an entry. If you do not specify message or -f, logger reads standard input. DESCRIPTION
The logger command makes the specified entries in the system log file. The logger command provides a program and shell script interface to the syslog() subroutine. The file in which entries are made depends on the current system log configuration; see syslog and syslogd for more information. NOTES
The effects of the environment variable LC_MESSAGES apply only to diagnostic messages generated by logger, and not to any messages written by the use of the command. EXIT STATUS
The following exit values are returned: Successful completion. An error occurred. EXAMPLES
To log the system reboot, including the process ID of the process running logger, enter: logger -i System rebooted To log each line in the file build.events with the tag trial build preceding them, enter: logger -f build.events -t "trial build" The following commands are equiv- alent and enter events of warning priority to the log: logger -p warning logger -p 4 The following commands are equivalent and enter events from the daemon facility of warning priority: logger -p daemon.warning logger -p 24.4 To specify the debug priority with a priority name, enter: logger -p debug my message To specify the debug priority with a priority number, enter: logger -p 7 my message To specify both debug priority and the user facility, enter: logger -p user.debug my message To specify the same facility/priority pair using numeric values, enter: logger -p 8.7 my message You can also combine alphabetic and numeric specifications: logger -p user.7 my message logger -p 8.debug my message ENVIRONMENT VARIABLES
The following environment variables affect the execution of logger: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). Determines the locale for the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: binlogd(8), syslogd(8), uerf(8) Functions: syslog(3) Standards: standards(5) logger(1)