Ah, no, I didn't realize that was necessary at upgrade.  I did it on the
secondary (because it was otherwise acting funny before the upgrade so
I'd done a wipe-and-reinstall), but not the primary.

Done now.  Should I post more logs?  Or a grepcerpt?  Other stuff...?




On Thu, Sep 02, 2010 at 11:30:55AM -0700, Craig Bender wrote:
> Hi Michael,
> 
> Whether an upgrade or a fresh install, you are required to run:
> 
> /opt/SUNWuttsc/sbin/uttscadm -c
> 
> Did you do that?
> 
> I'm guessing no, since that is what is responsible for updating the 
> schema and putting the service in /etc/services.
> 
> I'm saying it's the root cause, but will clear up a lot of errors for 
> easier trouble shooting.
> 
> http://wikis.sun.com/display/SRWC2dot2/How+to+Upgrade+SRWC
> 
> 
> 
> On 9/2/10 11:10 AM, Michael Jinks wrote:
> > We run about 135 DTU's connecting to a FOG of two servers, running the
> > Windows Connector in kiosk mode.  Servers are Fire x4600's running
> > Solaris 10 (x86).  Until a week ago we were on SRSS 4.1.
> >
> > Last week I upgraded the secondary in the FOG to SRSS 4.2, Windows
> > Connector 2.2, with the latest patch cluster, and Sun Ray patches
> > (140994-03, 143215-03, and 143535-01).  Two nights ago I updated the
> > primary identically.
> >
> > This morning, we got word that a number of our users are having their
> > Windows sessions dropped after some period of inactivity.  I've asked
> > for more details (how much inactivity?) but so far that's all I know.
> > Apparently it's a widespread problem -- a whole classroom of users, or a
> > sizable number of them, not just one or two here and there.
> >
> > In order to eliminate the usual culprit, I've been running remote
> > desktop sessions from my Linux desktop to our Windows servers, and those
> > appear to be running fine indefinitely, so I don't think the problem is
> > on the Windows side.
> >
> > The Sun Ray logs are showing a lot of traffic; looks like a lot of
> > clients are cycling, more than we'd expect given the relatively low
> > population on our campus right now.
> >
> > Since upgrading, I've noticed that the output of utsession -p has looked
> > a little funky.  Current excerpt:
> >
> >    pseudo.00144fea37bd            ???                  utku126    89   U
> >    pseudo.00144fea380e            ???                  ???        21   DI
> >    pseudo.00144fea388b            ???                  utku128    90   U
> >    pseudo.00144fea390f            ???                  utku109    76
> >    pseudo.00144fea3eba            ???                  utku124    87   U
> >    pseudo.00144fea3f61            ???                  utku159    16   U
> >    pseudo.00144fea3f77            ???                  utku140    12
> >    pseudo.00144fea3fcb            ???                  utku158    28   U
> >    pseudo.00144fea3fe6            ???                  ???        7    DI
> >    pseudo.00144fea40cf            ???                  utku132    49   U
> >    pseudo.00144fea40ea            ???                  utku194    24   U
> >
> > Reading the man page, I came to the conclusion that the "U" flag was
> > new with the latest release and might be normal.  But the "DI" sessions
> > give me pause.  Related to this issue?  Don't know.
> >
> > In case it's helpful, the "Arguments" line in our Kiosk Mode page reads
> > as:
> >
> >    -t 1800 -- -m -b -r disk:u=/tmp/SUNWut/mnt/$USER winders.uchicago.edu
> >
> > (where "winders" is our Windows RDP load balancer.)  That's unchanged
> > from before the update.
> >
> > Below, I'll post the last 50 lines currently in in the Sun Ray messages
> > log.  There may be some red herrings in there, since as luck would have
> > it we're also experiencing some trouble with our Windows licenses right
> > now, and a lot of our uttsc sessions are dying immediately for lack of a
> > CAL.  Repeated attempts to connect do eventually succeed, and once the
> > session is established that issue doesn't seem to matter any more, but
> > it's making it difficult for me to look at the logs and know which
> > sessions are stillborn for lack of a license, and which ones are
> > terminating because of some other cause.
> >
> > I realize this isn't the best bug report in the world, but I'm at a loss
> > for how to narrow down the trouble, so I'm hoping somebody can give me
> > some tips for how to collect better data.
> >
> > Thanks,
> > --Michael
> >
> > [log sample follows]
> >
> > Sep  2 13:00:32 kenwood gconfd (utku16-11204): [ID 702911 user.info] Exiting
> > Sep  2 13:00:34 kenwood Sun Ray Connector proxy:[13008]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:34 kenwood kiosk:uttsc[12959]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:34 kenwood gconfd (utku133-11523): [ID 702911 user.info] GConf 
> > server is not in use, shutting down.
> > Sep  2 13:00:34 kenwood gconfd (utku133-11523): [ID 702911 user.info] 
> > Exiting
> > Sep  2 13:00:35 kenwood Sun Ray Connector proxy:[13284]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:35 kenwood kiosk:uttsc[13234]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:37 kenwood Sun Ray Connector proxy:[4916]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:37 kenwood kiosk:uttsc[4838]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:38 kenwood Sun Ray Connector proxy:[13292]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:38 kenwood kiosk:uttsc[13261]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:42 kenwood Sun Ray Connector proxy:[13369]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:42 kenwood kiosk:uttsc[13326]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:42 kenwood Sun Ray Connector proxy:[5578]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:42 kenwood kiosk:uttsc[5544]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:44 kenwood Sun Ray Connector proxy:[5831]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:44 kenwood kiosk:uttsc[5803]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:45 kenwood Sun Ray Connector proxy:[5713]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:45 kenwood kiosk:uttsc[5654]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:45 kenwood Sun Ray Connector proxy:[13422]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:45 kenwood kiosk:uttsc[13399]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:46 kenwood Sun Ray Connector proxy:[6010]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:46 kenwood kiosk:uttsc[5988]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:49 kenwood Sun Ray Connector proxy:[13529]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:49 kenwood kiosk:uttsc[13506]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:50 kenwood Sun Ray Connector proxy:[13494]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:50 kenwood kiosk:uttsc[13469]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:50 kenwood utdtsession: [ID 702911 user.info] Delete 
> > (65,pseudo.080020f8405d)
> > Sep  2 13:00:50 kenwood dtlogin[1278]: [ID 691260 user.notice] 
> > pam_sunray_hotdesk:pam_sm_auth: ut_getTokenByDisplay failed -1 for display 
> > :65
> > Sep  2 13:00:50 kenwood last message repeated 1 time
> > Sep  2 13:00:51 kenwood gconfd (utku17-12923): [ID 702911 user.info] GConf 
> > server is not in use, shutting down.
> > Sep  2 13:00:51 kenwood gconfd (utku17-12923): [ID 702911 user.info] Exiting
> > Sep  2 13:00:53 kenwood Sun Ray Connector proxy:[13581]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:53 kenwood kiosk:uttsc[13544]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:55 kenwood Sun Ray Connector proxy:[6308]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:55 kenwood kiosk:uttsc[6284]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:56 kenwood Sun Ray Connector proxy:[13672]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:56 kenwood kiosk:uttsc[13650]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:57 kenwood Sun Ray Connector proxy:[13740]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:57 kenwood kiosk:uttsc[13716]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:00:57 kenwood Sun Ray Connector proxy:[6382]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:57 kenwood kiosk:uttsc[6358]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:00:58 kenwood Sun Ray Connector proxy:[6565]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:00:58 kenwood kiosk:uttsc[6543]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:01:00 kenwood Sun Ray Connector proxy:[6607]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:01:00 kenwood kiosk:uttsc[6577]: [ID 702911 user.notice] No entry 
> > for connector proxy found in /etc/services, using default port 7014 ...
> > Sep  2 13:01:00 kenwood Sun Ray Connector proxy:[13774]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:01:00 kenwood kiosk:uttsc[13751]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > Sep  2 13:01:01 kenwood Sun Ray Connector proxy:[13854]: [ID 855542 
> > user.error] Child closed socket prematurely, session shutdown
> > Sep  2 13:01:01 kenwood kiosk:uttsc[13789]: [ID 702911 user.notice] No 
> > entry for connector proxy found in /etc/services, using default port 7014 
> > ...
> > _______________________________________________
> > 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
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to