Well; I can now personally confirm I can duplicate repeatedly from my own laptop + ovdc + card reader.
It appears specific to OVDC with a card reader. I'm not thrilled, but glad I can duplicate. Opening a support call with Oracle. Something is clearly wrong...interestingly, once you put the card into an actual SunRay, it seems to correct itself. Pulling card in/out OVDC leaves the session screwed up. I know from our own kiosk code, we used to have things that didn't properly match the MD5 identifier, I'd be willing to bet there's something deep in SRSS missing card reader token formats, but that's just a guess. Thanks all! Devin Nate -----Original Message----- From: P.S.M.Swamiji [mailto:[email protected]] Sent: Wednesday, June 29, 2011 12:29 PM To: SunRay-Users mailing list Cc: Devin Nate Subject: Re: [SunRay-Users] uttsc hang On 6/28/2011 5:45 AM, Devin Nate wrote: > Hi P.S.M.Swamiji; > > Thanks for the response. > > Our logs have many of the following two types of error messages. Based on the > MD5sum identification, I'm guessing OVDC clients. Any idea about them - any > way it could be related to black screens? I doubt. > I've googled both with limited success. > > 1. > Jun 27 18:08:03 srs3.asp.cloudwerxdata.com utdevmgrd[1416]: [ID 515966 > daemon.warning] double mapping: > Jun 27 18:08:03 srs3.asp.cloudwerxdata.com utdevmgrd[1416]: [ID 705620 > daemon.warning] oldSession 0x84dafb0 tid > MD5.4caf5d91535f917103ff11ec5da3121a > Jun 27 18:08:03 srs3.asp.cloudwerxdata.com utdevmgrd[1416]: [ID 687377 > daemon.warning] newSession 0x84bdc30 tid > MD5.4caf5d91535f917103ff11ec5da3121a > > 2. (note, we don't use amgh - I wonder if this is slowing something down? Do > I need to specifically disable it? Remove it from pam altogether? No. Thanks P.S.M.Swamiji Note: These are my personal opinions, nothing to do with my employer > Jun 27 18:09:50 srs3.asp.cloudwerxdata.com dtlogin[14450]: [ID 118685 > user.error] pam_sunray_amgh::[DPY=102] ERROR in _populate_amgh_args > ret = -1 Jun 27 18:09:50 srs3.asp.cloudwerxdata.com dtlogin[14450]: > [ID 118685 user.error] pam_sunray_amgh::[DPY=102] Error getting authd > properties. Cannot proceed with AMGH. Will create a local session > > Thanks, > Devin > > > > ________________________________________ > From: P.S.M.Swamiji [[email protected]] > Sent: Monday, June 27, 2011 5:12 PM > To: SunRay-Users mailing list > Cc: Devin Nate > Subject: Re: [SunRay-Users] uttsc hang > > On 6/28/2011 1:13 AM, Devin Nate wrote: >> Hi Scott; >> >> I have no idea what keyboards our customers are using, especially >> since these are Oracle Virtual Desktop Client (OVDC) installs on >> WinXP and Windows 7 PCs, with card readers. They also have some >> SunRay 3's, but anytime I get to shadow the session it's on OVDC, and >> I've seen exactly what they're talking about from start to finish >> (i.e. I'm remoted in, they put a card in, connects to TS fine, I log >> in using a test account, and then log out, and it goes to black >> screen.) >> >> It is correctable by killing the session in the web gui, and I should note >> that it's not persistent, and on logout / log-back-in only. >> >> >> We've proactively enabled "-X off", but does anyone have a real-life account >> of what a user / admin would notice if they were being affected by what is >> mentioned in the SRS release notes copied below: > Certainly you won't see black screen issue because of this. > This issue occurs while login to W2008 R2 Server. That said after > entering user credentials, it just waits at welcome screen.. > > > Thanks > P.S.M.Swamiji > > Note: These are my personal opinions, nothing to do with my employer > >> http://download.oracle.com/docs/cd/E22662_01/E22660/html/Issues-Windo >> ws-Connector.html >> >> 8.16.4. Windows connector may hang at the Windows welcome screen when >> connecting to a Windows 2008 R2 server >> >> This hang is due to the multi-monitor enumeration process that occurs >> between the server and the Windows connector, and it is caused by the >> Windows server not sending monitor layout data to the Windows connector. >> >> Workaround: Disable the multi-monitor enumeration process using the uttsc -X >> off command. >> >> Reference: CR 12304470 >> >> >> Thanks, >> Devin >> >> >> ________________________________________ >> From: [email protected] >> [[email protected]] on behalf of Nishimura, Scott L >> (ESS) [[email protected]] >> Sent: Monday, June 27, 2011 11:33 AM >> To: SunRay-Users mailing list >> Subject: Re: [SunRay-Users] uttsc hang >> >> I saw this back in the 4.0 days: it turns out there were entries in /tmp >> that had the MAC of the affected TC and once I deleted those entries [even >> editing a file that said "do not edit"], the black screen went away. >> Bizarre, but that's how I remember it. >> >> Another explanation, from Dave Partington: >> >> I'm betting however the problem is most likely related to the USB controller >> on the Type 7 Keyboard. Do you run the mouse from the port on the backside >> of the keyboard? If you are. >> try switching the mouse to the front port on the Sun Ray 2 directly. If it >> stops happening, it will confirm the keyboard USB controller. As you know >> there was a lot of bad keyboards that generated USB Bus errors, what SUN did >> was simply tell the server to ignore the errors. And yes I have seen this >> error, only way to fix to recycle the session. >> >> >> Scott >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Devin Nate >> Sent: Saturday, June 25, 2011 10:59 AM >> To: SunRay-Users mailing list [[email protected]] >> Subject: [SunRay-Users] uttsc hang >> >> Hi folks; >> >> We've recently got a bug report, and I was able to witness through a couple >> remote sessions. >> >> We have: >> - Solaris 10 x86, current patches >> - SRSS 5.1.2 >> - SRWC 2.3 >> >> Basically, what happens is a user logs in to Windows Server 2008 r2. Does >> some work, and logs out. We can see uttsc exiting, and then it just becomes >> a persistent black screen. The mouse cursor style becomes more like >> Solaris/X and less like windows. Removing the card, re-inserting, etc., does >> not correct (in fact, the black screen follows). >> >> It's as though the original uttsc doesn't fully exit, or, a new uttsc spawns >> but doesn't connect. So far in all instances we've seen it has been OVDC >> (which we're deploying more of). Has anyone seen anything similar? thoughts? >> >> I've seen the new SRSS 5.2.1 has a technote (CR 12304470) about a hang on >> Windows Server 2008 r2 that is correctable by uttsc -X off. Does the above >> sound similar to this? >> >> Thanks, >> Devin Nate >> >> >> >> >> >> >> >> >> >> >> >> >> ________________________________ >> >> >> Information contained in this message may be privileged and confidential. If >> the reader of this message is not the intended recipient, be notified that >> any dissemination, distribution or copying of this communication is strictly >> prohibited. If this communication is received in error, please notify the >> sender immediately by replying to the message and deleting it from your >> computer. Thank you! >> _______________________________________________ >> SunRay-Users mailing list >> [email protected] >> http://www.filibeto.org/mailman/listinfo/sunray-users >> _______________________________________________ >> SunRay-Users mailing list >> [email protected] >> http://www.filibeto.org/mailman/listinfo/sunray-users >> >> ________________________________ >> >> >> Information contained in this message may be privileged and confidential. If >> the reader of this message is not the intended recipient, be notified that >> any dissemination, distribution or copying of this communication is strictly >> prohibited. If this communication is received in error, please notify the >> sender immediately by replying to the message and deleting it from your >> computer. Thank you! >> _______________________________________________ >> SunRay-Users mailing list >> [email protected] >> http://www.filibeto.org/mailman/listinfo/sunray-users > > ________________________________ > > > Information contained in this message may be privileged and confidential. If > the reader of this message is not the intended recipient, be notified that > any dissemination, distribution or copying of this communication is strictly > prohibited. If this communication is received in error, please notify the > sender immediately by replying to the message and deleting it from your > computer. Thank you! > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users ________________________________ Information contained in this message may be privileged and confidential. If the reader of this message is not the intended recipient, be notified that any dissemination, distribution or copying of this communication is strictly prohibited. If this communication is received in error, please notify the sender immediately by replying to the message and deleting it from your computer. Thank you! _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
