I think it happens on Insert of the card not in the middle.
below  is the log example.

Unfortunately it happens on many DTU's. We first noticed on the users who
more frequently change cards, but then after a while we noticed it  also
happens to users who leave for lunch or a meeting. This are all new Sunray 3
units and it happened on at least 10 different ones.

i will do some more testing with different cards tomorrow. i know a payflex
card froze once also but it was not on insert or removal but in middle of
work, which might be cause of some flash or so.



Nov  4 07:23:47 ra utauthd: [ID 775283 user.info] Worker7
CONFIG_ERROR: Property [d643] not found (caught)
Nov  4 07:23:48 ra utauthd: [ID 551619 user.info] Worker7 NOTICE:
whichServer GEMPLUS-MPCOS_8K.010000017e15006300ff0010:
Nov  4 07:23:48 ra utauthd: [ID 215233 user.info] Worker7 NOTICE:
CLAIMED by StartSession.m7 NAME:
GEMPLUS-MPCOS_8K.010000017e15006300ff0010 PARAMETERS:
{stealProtected=true, terminalIPA=192.168.128.32,
type=GEMPLUS-MPCOS_8K,
fw=GUI4.2_140993-06_2010.10.08.21.53,Boot:MfgPkg_4.2_27_2010.05.25.16.31,
state=disconnected, cause=insert, doamgh=true, barrierLevel=422,
lockaction=disconnect, rawId=010000017e15006300ff0010,
terminalCID=IEEE802.0021288fed39, MTU=1500, tokenSeq=1,
firstServer=c0a88001, atr.hist_len=0a, namespace=IEEE802,
keyTypes=dsa-sha1-x1,dsa-sha1, ddcconfig=1,
clientRand=PmNZMUzJMlmiXRKJZUaSPTqarMRc4T3Aj6eBt9oiGSm,
id=010000017e15006300ff0010, realIP=c0a88020,
startRes=1680x1050:1680x1050, useReal=true,
atr=3b2a008065a20101014072d643, event=insert, atr.hs=03,
sn=0021288fed39, rawType=GEMPLUS-MPCOS_8K, hw=SunRayP10, initState=1,
usersession=false, _=1}
Nov  4 07:23:48 ra utauthd: [ID 542210 user.info] Worker7 NOTICE:
CONNECT IEEE802.0021288fed39,
GEMPLUS-MPCOS_8K.010000017e15006300ff0010, all connections allowed
Nov  4 07:23:48 ra utauthd: [ID 118801 user.info] Worker7 NOTICE: MTU = 1500
Nov  4 07:23:48 ra utdtsession: [ID 702911 user.info] Add
(4,GEMPLUS-MPCOS_8K.010000017e15006300ff0010,normal)
Nov  4 07:23:49 ra utauthd: [ID 473100 user.info] Worker7 NOTICE:
SESSION_OK GEMPLUS-MPCOS_8K.010000017e15006300ff0010
Nov  4 07:23:51 ra dtlogin[22212]: [ID 118685 user.info]
pam_sunray_amgh::[DPY=4] AMGH_SUMMARY:
token=GEMPLUS-MPCOS_8K.010000017e15006300ff0010, username=,
AMGH_Done?=NO(Local Session), Details=AMGH is not configured.,
AMGH_Target=*NONE*
Nov  4 07:23:51 ra dtlogin[22212]: [ID 976841 user.info] pam_kiosk:
pam_sm_authenticate: Initiating Kiosk session with user utku48
Nov  4 07:23:51 ra kioskcritd[22354]: [ID 190395 user.info] kioskcritd started




2010/11/4 Bob Doolittle <[email protected]>

> Hi,
>
> I'm adding back in the CC's because yes, I could believe this could cause
> things like "black screen". It depends on when it happens.
> If it happens immediately upon inserting a smartcard, then this is a
> candidate. If it happens in the middle of working in a session than probably
> not.
>
> When this error occurs, an exception is thrown in utauthd. I am not
> familiar enough with the code to say at this time but if that exception were
> not handled gracefully then symptoms such as you describe on card insertion
> are at least plausible. This is happening at a critical time while utauthd
> is attempting to construct a token name for the inserted smartcard. It's
> *supposed* to generate an "unknown token" name in this case, which would
> result in a special OSD session displaying an error icon, but maybe there's
> a bug - this code path is not exercised much. It would have to be either a
> hardware problem, maybe with the reader in a particular DTU (or a damaged
> card?), or a bug probably both in the smartcard config file for this type of
> card as well as the error handling code in the getprop processing of
> SmartCardWordsImpl. I've CC'd Mike Bender who is more familiar with the code
> in SmartCardWordsImpl (and smartcard processing in general) to get his
> opinion.
>
> Do you see this problem on a particular DTU or DTUs?
>
> -Bob
>
>
> On 11/04/10 10:08, Dark Bass wrote:
>
>> Hi Bob
>>
>> no, i did not write a config file
>>
>> you are right, we are using normal sun payflex cards and this ones
>> GEMPLUS-MPCOS_8K.01000001891**********.
>> i've just went over the logs for the last day and it seems that the error
>> is
>> only on this cards not on payflexes.
>>
>> but i guess this is not a significant issue and is not causing screen
>> freeze
>> or black screen ?
>>
>> regards
>>
>> 2010/11/4 Bob Doolittle<[email protected]>
>>
>>   On 11/04/10 06:25, Dark Bass wrote:
>>>
>>> i am seeing this message in logs
>>>
>>> Nov  4 09:10:48 server1 utauthd: [ID 775283 user.info] Worker7
>>> CONFIG_ERROR:
>>> Property [d643] not found (caught)
>>>
>>> any ideas what this is ?
>>>
>>>
>>> This indicates a problem talking to a smartcard.
>>>
>>> Did you write your own smartcard config file?
>>>
>>> What type of smartcards do you use? What do your smartcard token names
>>> look
>>> like?
>>>
>>> If you use more than one type of smartcard, can you isolate which type of
>>> smartcard is in use when this error is seen?
>>>
>>> -Bob
>>>
>>>
>>>  2010/11/3 Ivar Janmaat<[email protected]>  <[email protected]>
>>>
>>>
>>>  I changed the poweroff time in .parms to 8 hours to see it this would
>>> help.
>>> But it did not....so I guess it is not the sleep.
>>>
>>>
>>> Ivar
>>>
>>> [email protected] schreef:
>>>
>>>
>>>  Yeah well i have srss 5.1 so i guess its not fixed.
>>>
>>> Utcapture doesnt show any packet loss but it sometimes shows great
>>> latency, but i was thinking its because sr3 uniits go to sleep or
>>> poweroff.
>>>
>>>
>>>
>>> ------- Original message -------
>>>
>>>
>>>  From: Ivar Janmaat<[email protected]>  <[email protected]>
>>> To: [email protected]
>>> Sent: 3.11.'10,  11:54
>>>
>>> Yes I have seen this too.
>>> Setup was VDI 3.2 with Sun Ray 3 Plus and SR 2 FS.  With Setup VDI 3.2.1
>>> it has not been reported yet but that does not mean it is resolved in
>>> 3.2.1
>>> I hope it is though ;-)
>>>
>>> Ivar
>>>
>>>
>>> [email protected] schreef:
>>>
>>>
>>>  Hi
>>>
>>> i am having issues with session freezing. It displays the last working
>>> screen on windows, i can move the mouse (maybe its the x mouse not
>>> windows
>>> mouse) but windows doesnt respond. Windows is working fine if  i rdp to
>>> it.
>>> I need to kill the session (ctr alt  2bksp doesnt help)  to get it
>>> working
>>> again. Usually it happens after some period of inactivity. Windows screen
>>> saver is disabled and it doesnt go into suspend..
>>> i am running srss 5.1 with vdm 1.2. Sunray 3 clients.
>>> It was happening with srss 5 also.
>>>
>>> any thoughts what i might check?
>>>
>>> regards _______________________________________________
>>> SunRay-Users mailing [email protected]://
>>> www.filibeto.org/mailman/listinfo/sunray-users
>>>
>>>  _______________________________________________
>>> SunRay-Users mailing [email protected]://
>>> www.filibeto.org/mailman/listinfo/sunray-users
>>>
>>>  _______________________________________________
>>> SunRay-Users mailing [email protected]://
>>> www.filibeto.org/mailman/listinfo/sunray-users
>>>
>>>  _______________________________________________
>>> SunRay-Users mailing [email protected]://
>>> www.filibeto.org/mailman/listinfo/sunray-users
>>>
>>>
>>> _______________________________________________
>>> SunRay-Users mailing [email protected]://
>>> 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