[This same problem was briefly discussed back in 2006 with no resolution.] At 04:07, /var/opt/SUNWut/log/messages started showing
Apr 8 04:07:49 rsunsu-is-sr02 utauthd: [ID 580773 user.info] Worker1 NOTICE: readMessage::socket looping limit exceeded.Close it. This was accompanied by other messages like Apr 8 04:07:38 rsunsu-is-sr02 utauthd: [ID 668639 user.info] Worker4 NOTICE: DISCONNECT IEEE802.00212812eff7, pseudo.00212812eff7 discReq-or-terminated The auth_log showed stuff like Couldn't connect to the Sun Ray datastore Couldn't connect to the Sun Ray datastore Warning: Unknown override session type '' - using default policy Warning: Unknown override session type '' - using default policy Error: export: Could not connect to the data store: Internal system error Couldn't connect to the Sun Ray datastore Error: export: Could not connect to the data store: Internal system error Error: Failed to retrieve Kiosk configuration Error: Failed to retrieve Kiosk configuration Warning: No valid session data for kiosk session on display ':3' Warning: No valid session data for kiosk session on display ':2' But since auth_log has no internal timestamps, I can't tell exactly when these messages occurred; the timestamp on the file itself was just before I rebooted so it likely captured events when I was having problems. An independent machine on another subnet, which does periodic pings, lost contact with this server at 04:07. It re-established contact 3 minutes later. But all morning this monitoring box reported losing and re-establishing contact many times until I rebooted the SunRay servers [not the monitoring server]. Note that the server itself was up: uptime showed "49 days". I was in via SSH and would lose my session when the server went "down" but from all indications, the server never actually went down. It seems like some corruption in SunRay software services caused the network sub-system to choke [it couldn't even respond to a "ping" request]. There are 2 machines in the FOG and both were doing it and both started doing it at the same time. TCs were rebooting as a result. Anyone successfully dealt with this [besides a reboot, which seems to have fixed things]? T5140 [2 in a FOG] SRSS 4.1/SRWC 2.1 w/139548-01 Solaris 10, update 6 ~300 clients running in kiosk mode I've never run into this before. I also have a separate infrastructure that's been running for 2.5 years without running into this problem. This other infrastructure is running 4.0, however.
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
