Stephen Repetski wrote:
Yes, I applied that fix, rebooted and did a utrestart -c for good measure.
/var/opt/SUNWut/log/message log after resetting the ray:
<snip>
Aug 12 17:21:40 domU-12-31-39-06-49-33 utdtsession: [ID 702911 user.info]
Add (,pseudo.00144fc8a1a2,normal)
Aug 12 17:21:40 domU-12-31-39-06-49-33 utdtsession: [ID 702911 user.error]
Error: No display numbers available
Aug 12 17:21:40 domU-12-31-39-06-49-33 utauthd: [ID 741085 user.info]
Worker2 UNEXPECTED: SESSION_ERROR pseudo.00144fc8a1a2 exitCode=2
Aug 12 17:21:40 domU-12-31-39-06-49-33 utauthd: [ID 902801 user.info]
Worker2 NOTICE: DISCONNECT IEEE802.00144fc8a1a2, pseudo.00144fc8a1a2 cannot
init session
Aug 12 17:21:40 domU-12-31-39-06-49-33 utauthd: [ID 226395 user.info]
SessionManager0 NOTICE: TERMINATE: ACTIVE session
Aug 12 17:21:40 domU-12-31-39-06-49-33 utauthd: [ID 283604 user.info]
Worker2 NOTICE: DESTROY pseudo.00144fc8a1a2 lifetime=311
Aug 12 17:21:40 domU-12-31-39-06-49-33 gdm-XKeepsCrashing: [ID 702911
user.notice] GDM can't start X server.
...with this last line being the one I'm interested in. This bit of log
repeats itself several times.
I'm most concerned about the "No display numbers available" error, that
could be the root cause of the rest. When a new session is created
SRSS attempts to find a free display, starting at display 2 and going up
to 1000. For each display number, it performs the following checks:
- the display isn't listed as allocated in the
/tmp/SUNWut/config/xconfig/Xservers file
- the port 6000+DISPLAY is not accepting connections
If the above criteria are met, the display number is assumed to be
available and is allocated.
So that error implies either that the Xservers file is corrupted (a
utrestart -c should clean it up and start fresh) or something is
allocating all the TCP ports in the 6002-7000 range.
After applying the patch for bug 6807063 (on the wiki as well), the Sun
Ray's status now alternates between 14B and 26B.
Was the above log taken before or after applying the patch?
-Bob
On Wed, Aug 12, 2009 at 12:54 PM, Joerg Barfurth <[email protected]> wrote:
Stephen Repetski schrieb:
Hi all,
I'm having this same problem on an Osol 2009.06 box with SRSS 5 EA 1.
Could someone send me this isGdmSyncedWithSRSS script?
Did you apply the sock2path fix mentioned elsewhere in this thread and
described somewhere on the Wiki?
- Jörg
_______________________________________________
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
