Thanks again Brad, >> ... don't think this started happening until pretty recently. > I'm pretty sure it's been there since SRWC 2.0 (SRSS 4.0 timeframe)
OK. That could mean we have changed something in our Solaris and/or SRSS
config recently that has brought this to the surface. Perhaps related to
some recent patch updating on our setup, if not the change to SRS-5.
But, also notice this is not showing up in one of our other systems,
currently still running SRSS 4.1 / SRWC 2.1, and not as up-to-date Solaris
patching either.
Could it be the mechanism has been in place since SRWC 2.0, but the actual
logs coming out is new?? A more recent change in either SRS 5 or Solaris
trusted extensions (sounds like more likely the former)?
Data point:
I just opened logs on our design system (the most up to date, running
SRS5) and it has several hundred of these nearly identical logs since
around 03:00 when the logs roll-over occurred -- and absolutely nothing
else. System has been inactive, other than a single DTU left in the
card-in, not logged into Windows state. Expect this is going to be
annoying to some customers unless we can find some way to suppress the
logs, or otherwise make them go away.
Will look into it some more.
-- Peter
Brad Lackey <brad.lac...@sun.com>
Sent by: sunray-users-boun...@filibeto.org
17/11/2009 10:25
Please respond to SunRay-Users mailing list
To: SunRay-Users mailing list <sunray-users@filibeto.org>
cc:
Subject: Re: [SunRay-Users] Annoying Connector proxy logs
(repost, with subject this time)
On Nov 16, 2009, at 5:49 PM, peter_blatherw...@mitel.com wrote:
>
> Thanks Brad,
> OK, that at least confirms Solaris only, and trusted extensions related,
as Craig also suggested.
>
> Do you know if this is new in SRS 5, or perhaps more recent Solaris 10
updates? I don't think this started happening until pretty recently. (It
would have crossed my pain threshold long ago ;-)
I'm pretty sure it's been there since SRWC 2.0 (SRSS 4.0 timeframe)
>
> -- Peter
>
>
>
> Brad Lackey <brad.lac...@sun.com>
> Sent by: sunray-users-boun...@filibeto.org
> 16/11/2009 20:35
> Please respond to SunRay-Users mailing list
>
>
> To: SunRay-Users mailing list <sunray-users@filibeto.org>
> cc:
> Subject: Re: [SunRay-Users] Annoying Connector proxy logs
(repost, with subject this time)
>
>
>
> These are definitely from uttscpd. This was employed specifically for
trusted extensions and is only on Solaris.
>
> Not sure how to stop the messages, or disable uttscpd though.
>
> On Nov 16, 2009, at 5:27 PM, Craig Bender wrote:
>
> > One thing that will help immensely will be to put a loop in the
script. Look at the Sun Ray Windows Connector Kiosk script for an
example.
> >
> > As far as Linux, we may not use the "proxy" as that was devised for
Solaris with Trusted Extensions. Not sure though (but I can check).
> >
> > peter_blatherw...@mitel.com wrote:
> >> [ Darn, previous post forgot the subject line. Please ignore
previous and respond to this one instead. Stupid fingers! Sorry about
that... ]
> >> Hi list,
> >> We are getting a very annoying logs flood in SRSS logs, using SRS-5
GA (SRSS 4.1 + SRWC 2.2), Solaris 10 u6, WTS running on Windows 2003
server. Logs are of the form:
> >> Sun Ray Connector proxy:[2370]: [ID 855542 user.error] Child closed
socket prematurely, session shutdown
> >> Sun Ray Connector proxy:[3266]: [ID 855542 user.error] Child closed
socket prematurely, session shutdown
> >> Sun Ray Connector proxy:[3418]: [ID 855542 user.error] Child closed
socket prematurely, session shutdown
> >> Sun Ray Connector proxy:[3534]: [ID 855542 user.error] Child closed
socket prematurely, session shutdown
> >> etc, etc, etc forever
> >> I believe these are being generated when user cards are left in the
DTUs, but Windows kiosk session (through uttsc) has not actually been
logged into, ie user is sitting in Windows login screen. Every 2 minutes,
Windows Terminal Services kicks out the windows RDP session if it is not
yet logged in, and we restart a few seconds later. Oddly, we do not seem
to see these in RHEL 5.2 setup, nominally identical otherwise. (We are
however seeing some other odd logs I do not yet have a good reproduction
scenario for ... that's a different story.) Is our understanding correct
-- logs triggered as a result of WTS killing the RDP session? Could it be
a sign of some other config issue or something? Is there some way to
suppress these logs?! There are potentially very many, darned annoying,
and are pointless for our purposes. Cheers,
> >> Peter Blatherwick
> >>
------------------------------------------------------------------------
> >> _______________________________________________
> >> 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
>
>
> Brad Lackey
> Datacenter Desktop - Technology Lead
> North America
> (720) 548-3339
>
>
> _______________________________________________
> SunRay-Users mailing list
> SunRay-Users@filibeto.org
> http://www.filibeto.org/mailman/listinfo/sunray-users
>
> <Brad Lackey.vcf>_______________________________________________
> SunRay-Users mailing list
> SunRay-Users@filibeto.org
> http://www.filibeto.org/mailman/listinfo/sunray-users
Brad Lackey
Datacenter Desktop - Technology Lead
North America
(720) 548-3339
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
<<attachment: Brad_Lackey.vcf>>
_______________________________________________ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
