> -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Hester > Sent: Saturday, June 06, 2009 6:51 PM > To: U2 Users List > Subject: Re: [U2] Tracing UV system calls, linux > > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Hester > Sent: Friday, June 05, 2009 11:35 AM > To: U2 Users List > Subject: [U2] Tracing UV system calls, linux > > Does anyone know of a way to trace system calls made by UV as > a non-root > user? Here's the problem we have: > > UV on RH ES 5.1 joined to an W2K3 native mode AD domain. We > have an AD > issue that causes UV to either fail to execute, or die before the user > can enter the environment. This doesn't happen to all users, and > appears to be random, but affects more users over time. > Usually a user > can get into UV eventually after repeated attempts. Once > they're logged > in, everything's fine. > > --- > > Update - turns out this is not an AD issue after all (at least not > directly, anyway), it's an issue with specific /dev/pts/... terminal > device files. I wasn't seeing it with non-AD UOJ connections because > they don't use a tty device. Once I realized it only affected a > specific tty device, I was able to reproduce it with any login, > including root. I noticed that 2 UV sessions were showing in > PORT.STATUS with ? as their PID and a blank tty device. "uvlictool > clean_lic -a" got back 2 seats. I restarted UV after that, > and now the > problem's gone. Unfortunately I didn't think to try to reproduce the > problem before restarting, so I'm not sure if cleaning up the > licencing > alone fixed it.
Update #2 - problem resolved Turns out uvdlockd normally cleans up any orphaned memory segments. The uvdlockd.log file in the uv home directory hit the 2GB file size limit sometime between mid April and mid May, preventing uvdlockd from doing its job. When a user was assigned the same UV user # as the previous owner of the orphaned memory segment, UV would fail to execute. IBM U2 support also discovered that UV 10.2.7 installed as root on linux doesn't have the suid bit set on a number of executables that it should. When the suid bit is set on the correct files, a user's UV session will clean up a prior orphaned memory segment on its own if uvdlockd hasn't already (assuming uvdlockd.log isn't full - the process immediately dies in this case since it also tries to write to the log). Without the suid bit set on these files, the process will loop until uvdlockd removes the segment. The suid issue is resolved in the current 10.3.1 release (not sure if it was resolved in this release or a prior one). These are the files in `cat /.uvhome`/bin that should have suid set: -rwsr-x--x 1 root bin 1351096 Dec 5 2007 clean -rwsr-x--x 1 root bin 3040420 Dec 5 2007 convchar -rwsr-x--x 1 root bin 1378924 Dec 5 2007 list_readu -rwsr-x--x 1 root bin 42016 Dec 5 2007 uv -rwsr-x--x 1 root bin 3035716 Dec 5 2007 uvadmsh -rwsr-x--x 2 root bin 3134936 Dec 5 2007 uvbackup -rwsr-x--x 1 root bin 1371152 Dec 5 2007 uvdlockd -rwsr-x--x 1 root root 5199327 Dec 5 2007 uvdlockd.d -rwsr-x--x 1 root bin 41888 Dec 5 2007 uvdls -rwsr-x--x 1 root bin 1358008 Dec 5 2007 uvlictool -rwsr-x--x 1 root bin 3928 Dec 5 2007 uvpset -rwsr-x--x 2 root bin 3134936 Dec 5 2007 uvrestore -rwsr-x--x 1 root bin 3252 Dec 5 2007 uvsetacc -rwsr-x--x 1 root bin 1354924 Dec 5 2007 uvtl_helper The IBM U2 support engineer gave me this script to correct the suid problem: #!/bin/sh # Add suid bit to the necessary executables. # Based on the executables in group MAIN from 10.3.1 release. # ECase: 11963 Cmds='uvtl_helper uvsetacc uvdlockd uvdlockd.d uv uvpset convchar uvlictool uvadmsh list_readu uvdls convencfile uvrestore uvbackup clean' for Cmd in $Cmds do if [ -f `cat /.uvhome`/bin/$Cmd ] then chmod u+s `cat /.uvhome`/bin/$Cmd fi done -John _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
