Hi,
well, how should I "escalate" it? Please provide a link or something
like that.
We are really interested in finding a solution for our problems as the
SR3 we bought are currently useless for us. And if the situation doesn't
change quickly we are about to send them back as they are not working in
our understanding, thus broken. And if there are beta firmwares or
something similar we could try out, please send them.
regards,
jens
Am 12.01.11 13:37, schrieb P.S.M Swamiji:
> You might be hitting CR#6985280 . Please escalate it .
>
> [6985280 SR3 (Venice) DTUs suddenly reset after receiving specific types
> of network traffic]
>
> Thanks
> P.S.M.Swamiji
>
> Note: These are my personal opinions, nothing to do with my employer
>
> Jens Langner wrote:
>> Hi,
>>
>> I would like to bring a serious problem to your attention that we are
>> here facing since we have a bunch of SunRay 3 and SunRay 3+ in our
>> hands. We do have a setup of about 150 SunRays (mostly 2 and 2FS)
>> running with about 3 SunRay servers (Solaris10 and Linux). This setup is
>> now running for about 2-3 years without a single problem so far.
>>
>> However, since we have the SunRay 3 and SunRay 3+ in our hands and have
>> already distributed them to some of our users we are facing quite a
>> serious problem. While the older SunRays are working fine and 24/7, the
>> SunRay 3 clients (no matter if 3 or 3+) are suddenly disconnected after
>> a random time of use. Then the "Oracle logo" is shown and suddenly the
>> connection comes back. No matter if we connect these SunRays with 1000F
>> or 100F, we are always facing these kind of problems. I know that this
>> sounds a bit odd, so I tried to find some usable information for the
>> reason why only the SunRay3 clients behave like that. However, I didn't
>> find anything on google&Co. So I looked into the
>> /var/opt/SUNWut/logs/messages logfile and found the following:
>>
>> -- cut here --
>> Jan 12 04:02:22 betty utauthd: [ID 559038 user.info] Worker4 NOTICE:
>> DISCONNECT IEEE802.0021288fbbc7, pseudo.0021288fbbc7
>> reauthenticatingDuplicateTID
>> Jan 12 04:02:22 betty utauthd: [ID 623334 user.info] Worker4 UNEXPECTED:
>> during send to: java.net.socketoutputstr...@4cba66
>> error=java.net.SocketException: Broken pipe
>> Jan 12 04:02:22 betty utauthd: [ID 168201 user.info] Worker4 NOTICE:
>> DESTROY pseudo.0021288fbbc7 lifetime=6449521
>> Jan 12 04:02:22 betty utauthd: [ID 164586 user.info] Worker4 NOTICE:
>> whichServer pseudo.0021288fbbc7:
>> Jan 12 04:02:22 betty utauthd: [ID 185812 user.info] Worker4 NOTICE:
>> CLAIMED by StartSession.m6 NAME: pseudo.0021288fbbc7 PARAMETERS:
>> {stealProtected=true, terminalIPA=149.220.11.138, type=pseudo,
>> fw=GUI4.2_140993-05_2010.08.25.23.16,Boot:MfgPkg_4.2_27_2010.05.25.16.31,
>> state=disconnected,
>> cause=insert, doamgh=true, barrierLevel=422, lockaction=disconnect,
>> rawId=0021288fbbc7, terminalCID=IEEE802.0021288fbbc7, MTU=1500,
>> tokenSeq=1, firstServer=95dc0a0b, namespace=IEEE802,
>> keyTypes=dsa-sha1-x1,dsa-sha1, ddcconfig=1,
>> clientRand=dPCwGO.I1/nVCFJdtspQmCUPmqN69uShGCprghc8/1q, id=0021288fbbc7,
>> realIP=95dc0b8a, startRes=1600x1200:1600x1200, useReal=true,
>> event=insert, sn=0021288fbbc7, rawType=pseudo,
>> clientKeyStatus=unconfirmed, hw=SunRayP10, initState=1,
>> usersession=false, _=1}
>> Jan 12 04:02:22 betty utauthd: [ID 956772 user.info] Worker4 NOTICE:
>> CONNECT IEEE802.0021288fbbc7, pseudo.0021288fbbc7, all connections
>> allowed
>> Jan 12 04:02:22 betty utauthd: [ID 118799 user.info] Worker6 NOTICE: MTU
>> = 1500
>> Jan 12 04:02:22 betty utdtsession: [ID 702911 user.info] Hotdesk
>> (12,pseudo.0021288fbbc7,default)
>> Jan 12 04:02:22 betty utauthd: [ID 355798 user.info] Worker6 NOTICE:
>> SESSION_OK pseudo.0021288fbbc7
>> -- cut here --
>>
>> So you can see that in the middle of the night (4 am) a SunRay 3 was
>> suddenly disconnected and that the reason for it seems to be a "Broken
>> pipe" comming out of an Java Exception.
>>
>> Now the question to the SRSS experts in here: Is that behaviour known
>> for SunRay 3 clients and what would be the proposed fix for that? I also
>> did a walk through all of the log files of our various SRSS and I only
>> found that "Broken pipe" exception for SunRay3 clients. In addition, we
>> are running SRSS 5.0 + the latest SRSS patches.
>>
>> Any help would be highly appreciated as we are currently unable to use
>> any of the 10+ SunRay3 clients in our environment.
>>
>> regards,
>> jens
>>
>
> _______________________________________________
> SunRay-Users mailing list
> SunRay-Users@filibeto.org
> http://www.filibeto.org/mailman/listinfo/sunray-users
--
Dr. Jens Langner Ph: +49-351-2602757
Helmholtz-Zentrum Dresden-Rossendorf e.V.
Institute of Radiopharmacy - PET Center j.lang...@hzdr.de
Germany http://www.hzdr.de/
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
