Hi Craig;
Thanks for the follow up.
1. Unless a solaris patchset added a /tmp cleaner, we absolutely do not do
this. Our kiosk code requires readonly access to a perfect copy of /tmp/SUNWut
- anything that messes with that would be horrible for us.
2. Yes, I was personally working on a station, uttsc kiosk session active and
usable, and 26B floating around. However, today, we watched a different similar
scenario, where a user was working, GOT the 26B floating around and unable to
proceed. Removed card, the solaris dtlogin came up. Re-inserted their card and
got back to their session as normal, no more 26B. It's not consistent.
3. Java was upgraded from 1.5 to 1.6.0_23 Solaris x86 32-bit.
4. Will review utsession -p when we get our next 26B. We may have one, have a
remote user who left for lunch with one but I can't reach right now.
5. All of our sessions are kiosk sessions, so I'd say yes.
6. /etc/opt/SUNWut/jre points to /usr/java, which is the newly installed
1.6.0_23:
/etc/opt/SUNWut/jre/bin/java -version
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Server VM (build 19.0-b09, mixed mode)
7. Yes, updated all dtu's to GUI4.2_140993-06_2010.10.08.21.53.
Both members of FOG equally updated. Just double checked. Just checked on
version info on DTU's and they do represent that level.
8. Don't believe we have any disk space issues. Our 'smallest' member of the
fog reports no more than 25% disk utilization.
9. Very custom kiosk script in perl. However, it essentially runs 2 utactions
and completes with it essentially calls uttsc. The final perl is:
system("/opt/SUNWuttsc/bin/uttsc ...");
10. Again, no /tmp cleanup processes at all.
Thanks,
Devin
-----Original Message-----
From: sunray-users-boun...@filibeto.org
[mailto:sunray-users-boun...@filibeto.org] On Behalf Of Craig Bender
Sent: Tuesday, January 11, 2011 12:22 PM
To: SunRay-Users mailing list
Subject: Re: [SunRay-Users] Bob, Craig - Sun Ray 26B - several models - SRS
5.1.1
Hi Devin,
Just to be clear, users are actively using the client and can continue to do so
when the On Screen Display pops up with 26B? OSD code of 26 is basically
telling you the DTU is waiting on the Xserver to start sending it traffic.
I've seen a few different causes for code 26. Wrong Java version, crashing
Xservers, a cron job that cleans out /tmp periodically and deletes critical
session files /tmp/SUNWut. But I don't think I've ever seen a case where the
user could keep on using the session.
A few questions.
What does utsession -p report when the OSD is on the screen?
Does it only happen to kiosk sessions?
Does /etc/opt/SUNWut/jre point to a 32 bit version of the 1.6 JRE?
Did you update the DTUs with the new firmware image?
No disk space issues?
No cleanup scripts in crontab that might be clearing out /tmp Are you using the
built-in Kiosk Script for SRWC? Any customizations there?
On 1/11/11 10:30 AM, Devin Nate wrote:
> Dear SunRay users (hopefully Bob, Craig also?);
>
> We're continuing to have problems with random 26B's, and don't even know
> where to begin to help debug.
>
> We don't see any particular errors in log files, besides several pam
> messages. The 26B's are happening on new sun ray 3's and older sun ray 2's.
>
> So far, our only theory is a PAM problem ... we appear to have many of the
> following style messages.
>
> dtlogin[990]: [ID 691260 user.notice] pam_sunray_hotdesk:pam_sm_auth:
> ut_getTokenByDisplay failed -1 for display :51
>
> We run fully stock PAM, no customizations.
>
> In any event, does anyone have any theories as to how to debug 26B's? In the
> most recent case, card removal corrected (went back to solaris login screen),
> and card insert worked exactly as expected and 26B was gone.
>
> Please, any ideas on trouble shooting? We don't even really know what likely
> candidates for a 26B are to start a process.
>
> Thanks,
> Devin
>
>
>
>
>
> From: sunray-users-boun...@filibeto.org
> [mailto:sunray-users-boun...@filibeto.org] On Behalf Of Devin Nate
> Sent: Tuesday, January 04, 2011 6:00 PM
> To: 'sunray-users@filibeto.org'
> Subject: [SunRay-Users] Sun Ray 26B - several models - SRS 5.1.1
>
> Hi Folks;
>
> We recently applied some sun ray patches, and are now experiencing some new
> problems. In particular, the following updates:
>
> 1. Applied all patches from smpatch for Solaris 10, x86-64. Approx 300
> patches were applied.
> a. Performed prescribed reboots, single user patching, and configuration
> reboots.
>
> 2. Applied Java SDK 1.6.0_23, and activated as default java instance.
> Previously, we were at 1.5 (for some unknown reason).
>
> 3. Applied SRS 5.1.1. We were previously at patch level -03 (now -06 it
> seems), as well as SRWC 2.3 (previously 2.2).
>
>
>
> The new undesirable behavior we are seeing:
>
> 1. Our users all use a Kiosk app to access windows terminal servers using
> uttsc. Intermittently, with card inserted and the kiosk app running (i.e.
> uttsc), the sun ray will display a 26B dialog box floating around for no
> apparent reason. The user is still able to fully use the system, just the
> annoyance of the 26B window floating around.
> a. Our policy requires full encryption + client authentication. These dtu's
> are all authenticated and have worked continuously for a long time without
> this symptom.
> b. A stop-A tends to be able to make it go away. It ?sometimes? comes back
> after ?some? unknown period of time, and doesn't impact all users.
> c. Removal of the card properly takes the user back to the standard login
> solaris login screen. Re-insertion of the card back to the terminal server
> session.
> d. Seen on SunRay 2 DTU and new SunRay 3.
>
> 2. Possibly related: When in the srs management website, after first patching
> (and still viewable), sessions show as disconnected that are clearly
> connected. In the most extreme case, I was in a OVDC session logged into a
> kiosk session (into a terminal server). I was on that terminal server looking
> at the srs website, at my session, which was identified as 'disconnected'.
> Further investigation showed that on initial login, the session shows as
> connected for a few minutes, after which it goes to disconnected, even though
> nothing becomes disconnected (i.e. still using the session). Likewise,
> reconnection works just fine.
>
>
> Any feedback helpful, thanks,
> Devin
>
> _______________________________________________
> SunRay-Users mailing list
> SunRay-Users@filibeto.org
> http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
