I think I remember something like this, too, where the user license wasn't getting released even though the session was gone. Here, we run uvlictool on a regular basis so that takes care of this problem.
BobW -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jordan Sent: Tuesday, June 20, 2006 3:36 PM To: [email protected] Subject: RE: [U2] UV - Users couldn't get into UniVerse Check you licenses with the uvlictool. There is an option to clean licenses. Sometimes a forced logout or fatal issue may not drop the license even though the user is no longer connected. The uvlictool cleans this up Regards David Jordan Managing Consultant [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bertrand, Ron Sent: Wednesday, 21 June 2006 7:57 AM To: [email protected] Subject: RE: [U2] UV - Users couldn't get into UniVerse Solaris 8 Universe 10.0.3 We had the same problem twice last month. We also decided that the uvdlockd.log entries were a red herring. So far it has not happened again. We were no where near our maximum users limit but it acted like it was hitting that limit. If somebody logged off (or just out of Universe) then the next person waiting to login to Universe was able to get in. Ron Bertrand ISD/LIS Group Health Coop -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hennessey, Mark F. Sent: Tuesday, June 20, 2006 1:29 PM To: [email protected] Subject: [U2] UV - Users couldn't get into UniVerse Solaris 8, UV 10.0.8 ... A sister site had a strange error today. Users could successfully login to unix, but once the login script performed an exec uv the user would hang, with no response. Using ps -aef showed "uv" as their last command. Users all ready on were OK. The only apparent errors were in uvdlockd.log (numerous iterations): Tue Jun 20 10:06:50 2006 - Failure in LK_cleanup_pshm Tue Jun 20 10:06:50 2006 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (13100) Tue Jun 20 10:06:50 2006 - ** Cleanup being performed for UserSig(74) I thought it might have been that the login semaphore was locked, but every time they checked it using SEMAPHORE.STATUS it appeared to be in a zero state. The situation may have resolved itself, or the half-panicked executions of uvlictool, UNLOCK LOGINLOCK SEMAPHORE, and HELP ME NOW, plus banging on the console with a half eaten bananna may have resolved it. I'm thinking the errors in the uvdlockd.log are either a red herring or symptoms, not the cause. Other than the login sempahore, what could cause the a user to experience these symptoms? Any random thoughts would be appreciated. Thanks in advance, Mark Hennessey ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
