- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- can't get to sam ...here is the error message
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 07:11 AM
01-29-2003 07:11 AM
The file "/var/sam/lock/lock_ta" could not be locked (errno = 45,
"Lockf deadlock detection"). This file must be lockable so that this
SAM session can be locked. Otherwise, other SAM sessions won't be able
to detect that this SAM session is running on the system.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 07:19 AM
01-29-2003 07:19 AM
SolutionDo a ps -ef |grep sam and make sure you have no sam sessions running.
Once it is done, go to /var/sam/lock directory
and delete the files in there.
Then you should be able to start sam.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 07:22 AM
01-29-2003 07:22 AM
Re: can't get to sam ...here is the error message
HTH
Marty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 07:22 AM
01-29-2003 07:22 AM
Re: can't get to sam ...here is the error message
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 07:33 AM
01-29-2003 07:33 AM
Re: can't get to sam ...here is the error message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 09:52 AM
01-29-2003 09:52 AM
Re: can't get to sam ...here is the error message
all the permission has been change to 777 ?
is there anything that i should be look at??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 10:00 AM
01-29-2003 10:00 AM
Re: can't get to sam ...here is the error message
#ll -d /var/sam/lock
drwxr-xr-x 2 bin bin 2048 Jan 29 08:57 /var/sam/lock
# ll /var/sam/lock
total 0
When did the permissions change? On what? The directory?
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 10:34 AM
01-29-2003 10:34 AM
Re: can't get to sam ...here is the error message
# ls
# ll
total 0
# ll -d /var/sam/lock
drwxr-xr-x 2 bin bin 1024 Jan 29 11:32 /var/sam/lock
# sam
The file "/var/sam/lock/lock_tc" could not be locked (errno = 45,
"Lockf deadlock detection"). This file must be lockable so that this
SAM session can be locked. Otherwise, other SAM sessions won't be able
to detect that this SAM session is running on the system.
after deleted it..and it is still not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 10:42 AM
01-29-2003 10:42 AM
Re: can't get to sam ...here is the error message
I also notice this error on the syslog
Jan 29 11:23:30 kunu syslog: get_pwhist_config)): Password history is not con
figured in the /etc/default/security file. Default password history depth 1 is
used.
Jan 29 11:23:33 kunu syslog: files_getprpwhist: Failed to lock pwhist file.
Jan 29 11:23:33 kunu syslog: update_passwd_entry: Failed to obtain password h
istory information