I'll have to wait for him to arrive today before trying the utswitch or
any of the user specific things.
This indeed happens on a single DTU. Put card in, log in to server
sunray01. Pull card out, put it back in, welcome banner to server
sunray02. I had him try it on several different DTU's, a model 2 and a
170. All of our DTU's are on the same private subnet but he has tried
it on DTU's in different parts of the building (and thus connected to
different switches) with the same results. If I plug my card into the
same DTU, using JDS, it's no problem. Everything works as expected. If
he plugs in using CDE, no problem. I've tried giving him a different
card as well with no effect.
The only unusual thing I can relate about this particular user is that.
When I first put the sunray on his desk he was trying to log in with JDS
and it would just kick him back to the login banner every time. After
some poking around I found that he had prepended an entry to
LD_LIBRARY_PATH that was pointing at some old version of the Gnome
libraries. Once we removed that entry he was able to login with JDS but
with this odd server switching behavior.
We've done nothing to any of the files in /etc/dt/config or made any
customizations to any of Xstartup etc..
utgstatus shows: (I've changed the IP addresses in the output for
paranoia's sake)
host flags interface flags interface flags
191.254.252.0/24 172.3.8.0/24
----------- ------------------- -------------------
sunray01 TN 191.254.252.126 U-- 172.3.8.1 UAM
sunray02 TN 191.254.252.127 U-- 172.3.8.2 UAM
Once the user gets here I'll try utswitch etc..
Thanks for the response!
Elliott
ottomeister wrote:
On 6/4/07, Elliott Peeler <[EMAIL PROTECTED]> wrote:
I have a new user to my sunray system who wants to use JDS as his
desktop. The issue is this: He inserts his smart card, logs in and
everything comes up okay. He pulls his card out, re-inserts it and he is
redirected to the other sunray server in the failover group. No matter
what we do, we cannot get him connected back to the original session on
the original server.
He doesn't get connected back to the first session even if he
does 'utswitch -h <original_server>' ? (Not that that should
be necessary, but if that doesn't work then something very
strange is happening.)
What does 'utswitch -l' show in each of this user's sessions?
What does 'echo $SUN_SUNRAY_TOKEN' show in each of
this user's sessions?
Looking at the Admin interface on the primary server I see his smartcard
has two sessions associated with it after we run through this scenario,
one on each server. This only happens in JDS. CDE works fine. JDS
works fine for me and for the few other users who use it. It's just this
particular user. Obviously something is amiss in his environment but
we've tried moving out every start up file that he has.
Hotdesking really doesn't know or care about what kind of
desktop is running, so JDS versus CDE is probably a red
herring. Startup files don't run at hotdesk time so they
should have no bearing either, unless they've been
customised by the site or the user to have knowledge of
Sun Ray and do something when a hotdesk event
happens.
Have you made any changes to any of the dtlogin session
scripts (Xsetup, Xreset, especially Xstartup) recently? Do
you have site-local versions of those scripts in /etc/dt/config?
What does 'utgstatus' show on each of the servers?
Is there anything unusual about the DTUs that this user
has been using? Which subnet(s) are the DTUs on that
he's trying to use? Can anyone else successfully hotdesk
between those specific DTUs? (Or is this happening even
on a single DTU?)
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
