Here are some notes I took while I was experiencing the problem; hopefully your
situation has some parallels.
-------------------------------
2008/04/10 - Scott Nishimura
This problem has been plaguing us for months: perhaps 30 days after a reboot,
thin clients stop being able to connect to sunray01. The client gets a black
screen with a cursor arrow [the blue screen and an hourglass cursor has the
same symptoms but requires a different solution; see below]. The destination
SRS is always sunray01.
Note that even for DTUs that ultimately connect to a secondary in the FoG, the
first destination is always the primary.
Fix: edit /opt/SUNWkio/lib/utils.sh, comment out lines 190 and 200:
return $KIOSK_RESULT_FAILED
I had a hung TC and when I made the change, within the 60 second retry window
the TC was then able to connect.
Full explanation below:
Bug ID: 6602248
Synopsis: Sun Ray Kiosk mode failed with Kiosk Session Error: Kiosk setup
failed: invalid kiosk session config
Product: sunray
Category: srss
Subcategory: kiosk
Bug-RFE-EOU: Defect
Sub-Area: Availability
State: 11-Closed
Priority: 2-High
Responsible Manager: [email protected]
Responsible Engineer: [email protected]
Description:
Sun Ray Kiosk mode at startup sometimes causes errors on some DTUs saying
Kiosk Session Error: Kiosk setup failed: invalid kiosk session configuration as
a pop-up.
Other DTUs start up normally. Hitting "OK" usually results in a normal kiosk
session (although the error can be repeated)
Investigation shows that the error is produced by the Sun Ray pam module, when
/opt/SUNWkio/lib/initsession fails. This fails when executing cleanupTempFiles
(held in /opt/SUNWkio/lib/utils.sh) when either one of the two find commands, eg
/usr/bin/find /tmp /var/tmp -user utcu5 ! -type d -exec /bin/rm -f {} ;
produces an error message like
/usr/bin/find: stat() error /tmp/sh121760: No such file or directory
Note that the reported file does not belong to the user (utcu5) in this case.
What appears to be happening is that the system with multiple activities going
on, find constructs a list of files to process, and then stat()s each in turn.
If a file vanished between the creation of the list, and using stat(), find
will, on completion, exit with status code 1
This causes an error, and a failure.
Submitted By: [email protected]
Date Modified: 2007-09-07 14:40:24 GMT+00:00
Justification:
Priority changed from [] to [2-High]
New release of Sun Ray Server Product
being rolled out to schools causes dissatisfaction when a proportion of Sun
Rays do not come up cleanly.
[email protected] 2007-09-07 14:40:24 GMT
Submitted By: [email protected]
Date Modified: 2007-09-07 14:40:24 GMT+00:00
Work Around:
Patch file /opt/SUNWkio/lib/utils.sh as follows:
(Note: this will be clobbered by an eventual patch, but the next Kiosk patch
should apply similar changes to that file)
--- utils.sh.orig Fr Sep 7 18:32:36 2007
+++ utils.sh Fr Sep 7 18:33:30 2007
@@ -187,7 +187,7 @@
if [ $? -ne 0 ] ; then
logDebug -m "$_inModule" \
-l "Error: failed to remove temporary files for user '$_inUser'"
- return $KIOSK_RESULT_FAILED
+ #return $KIOSK_RESULT_FAILED
fi
/usr/bin/find ${KIOSK_TMP_DIRS:-$KIOSK_DEFAULT_TMP_DIRS} -user $_inUser \
-depth -exec /bin/rmdir {} \;
@@ -197,7 +197,7 @@
# directory existence should not be security relevant
logDebug -m "$_inModule" \
-l "Warning: failed to remove temporary directories for user
'$_inUser'"
- return $KIOSK_RESULT_FAILED
+ return $KIOSK_RESULT_SUCCESS
else
logDebug -m "$_inModule" \
-l "Success: removed temporary files and directories for user
'$_inUser'"
Submitted By: [email protected]
-------------------------------------
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Devin Nate
Sent: Monday, June 27, 2011 7:25 PM
To: SunRay-Users mailing list
Subject: EXT :Re: [SunRay-Users] uttsc hang
Sorry to reply to my own post, but I have additional information:
MD5.4caf5d91535f917103ff11ec5da3121a is somehow associated with Display 102, as
evidenced by:
cd /tmp; find . -type f -exec grep 4caf5d91535f917103ff11ec5da3121a {}
/dev/null \;
./SUNWut/config/displays/102:TOKEN=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/displays/102:TOKEN_SET=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/displays/102:INSERT_TOKEN=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/ctokens/pseudo.4caf5d91535f917103ff11ec5da3121a:TOKEN=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/ctokens/pseudo.4caf5d91535f917103ff11ec5da3121a:TOKEN_SET=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/ctokens/pseudo.4caf5d91535f917103ff11ec5da3121a:INSERT_TOKEN=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/dispinfo/102:TERMINAL_ID=MD5.4caf5d91535f917103ff11ec5da3121a
./SUNWut/config/xconfig/Xconfig:Dtlogin.*_102.environment:
SUN_SUNRAY_TOKEN=pseudo.4caf5d91535f917103ff11ec5da3121a
CORONA_TOKEN=pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:87/config/policy:raw pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:87/config/policy:token
waitretry.MD5-4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:94/config/policy:raw pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:94/config/policy:token
waitretry.MD5-4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:102/config/policy:raw pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:102/config/policy:token pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:107/config/policy:raw pseudo.4caf5d91535f917103ff11ec5da3121a
./SUNWut/kiosk/:107/config/policy:token
waitretry.MD5-4caf5d91535f917103ff11ec5da3121a
Interestingly, pam_sunray_amgh has DPY=102 in the error message as well. I can
only assume they are related.
Thanks,
Devin
________________________________________
From: Devin Nate
Sent: Monday, June 27, 2011 6:15 PM
To: SunRay-Users mailing list
Subject: RE: [SunRay-Users] uttsc hang
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'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?
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-Windows-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
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
