Can you provide details of the environment? e.g.
production/dr/uat/development or all universe release number of users, type of application (generic) guest operation system and release, kernel, glibc etc vmware tools AND what you mean by the last part. This would be useful information as @ the moment I am planning with a client to a possible move from RHEL 4.0 onto a VMWare platform for all environments, production, dr and dev. Cheers, Phil. > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- > boun...@listserver.u2ug.org] On Behalf Of Augusto Alonso > Sent: Monday, 8 June 2009 11:16 p.m. > To: U2 Users List > Subject: Re: [U2] Tracing UV system calls, linux > > Hi. > We had a similar issue with Universe under Vmware Infraestructure. > But it was a telnet issue. > We solved it after: > - patching the Universe host to the last O.S. patch level, > - installing the last VmwareTools > - AND making sure that the host Operating System was exactly > described > in the ESX server. > > HTH > Augusto > > ----- Original Message ----- > From: "John Hester" <jhes...@momtex.com> > To: "U2 Users List" <u2-users@listserver.u2ug.org> > Sent: Sunday, June 07, 2009 3:51 AM > 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. > > > > Anyone know what might suddenly cause UV tty sessions to hang in an > > ambiguous state on exit? > > > > Thanks, > > John > > _______________________________________________ > > U2-Users mailing list > > U2-Users@listserver.u2ug.org > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
