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 ;-) 

-- Peter





Brad Lackey <[email protected]>
Sent by: [email protected]
16/11/2009 20:35
Please respond to SunRay-Users mailing list
 
        To:     SunRay-Users mailing list <[email protected]>
        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).
> 
> [email protected] 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
>> [email protected]
>> http://www.filibeto.org/mailman/listinfo/sunray-users
> _______________________________________________
> SunRay-Users mailing list
> [email protected]
> http://www.filibeto.org/mailman/listinfo/sunray-users


Brad Lackey
Datacenter Desktop - Technology Lead
North America
(720) 548-3339


_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

<<attachment: Brad_Lackey.vcf>>

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to