I've experienced the same thing on CentOS 4.4 and a few times with S10.
It appears to be a hang in something gnome related. If it happens
again, then see if you can ssh to the box and see if there are any gnome
related procs running for that user.
What always remedies this for me is to insert/remove a smart card.
Talman, Knut wrote:
Code was 26D. It happended after a logoff, the Sunray 2 rebooted (if I may
say so) and then ...
Currently there is only one Sunray connected to the server.
Regards,
Knut
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Craig Bender
Gesendet: Dienstag, 26. September 2006 20:24
An: SunRay-Users mailing list
Betreff: Re: [SunRay-Users] Server not responding
There should have been other codes on the OSD besides the hour glass.
Did you take note of those?
Was this after a logoff , was it a brand new session? Did all Sun Rays
display this or just one unit?
Talman, Knut wrote:
Dear all,
we've set up a CentOS 4.3 Server on a X4200 with SRSS 3.1.1. Ran very fine
until 5 minutes ago.
Then we had the following problem:
The client gets an IP adress, finds the Sunray server (shown in the info
box) and displays the sand clock. And thats all. The message log has some
entries:
Sep 26 18:39:34 odumin utauthd: Worker4 NOTICE: DISCONNECT
IEEE802.00144f3c8266, pseudo.00144f3c8266 reauthenticatingDuplicateTID
Sep 26 18:39:34 odumin utauthd: SessionManager0 NOTICE: TERMINATE: ACTIVE
session
Sep 26 18:39:34 odumin utauthd: Worker4 UNEXPECTED: during send to:
[EMAIL PROTECTED] error=java.net.SocketException:
Connection reset
Sep 26 18:39:34 odumin utauthd: Worker4 NOTICE: DESTROY
pseudo.00144f3c8266
lifetime=90681
Sep 26 18:39:34 odumin utauthd: Worker4 NOTICE: whichServer
pseudo.00144f3c8266:
Sep 26 18:39:34 odumin utauthd: Worker4 NOTICE: CLAIMED by StartSession.m2
NAME: pseudo.00144f3c8266 PARAMETERS: {terminalIPA=192.168.32.68,
type=pseudo, fw=MfgPkg_4.08,REV=2006.04.12.14.46, state=disconnected,
cause=insert, doamgh=true, barrierLevel=310, rawId=00144f3c8266, MTU=1500,
tokenSeq=1, firstServer=0ae2e282, namespace=IEEE802, ddcconfig=1,
id=00144f3c8266, clientRand=lGX2yhlK0nwS7s5566k6DNX9PrOG5Q4/i65Le9TFEP4,
realIP=c0a82044, startRes=1280x1024:1280x1024, useReal=true, event=insert,
pn=50120, sn=00144f3c8266, rawType=pseudo, hw=SunRayP8, initState=1, _=1}
Sep 26 18:39:34 odumin utauthd: Worker4 NOTICE: CONNECT
IEEE802.00144f3c8266, pseudo.00144f3c8266, all connections allowed
Sep 26 18:39:34 odumin utauthd: Worker1 NOTICE: MTU = 1500
Sep 26 18:39:34 odumin utauthd: Worker1 NOTICE: SESSION_OK
pseudo.00144f3c8266
A warm restart did not fix the problem, a cold restart did.
Any idea what was happening/where to look at?
Thank you in advance,
Knut
_______________________________________________
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
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
