On Thu, Jun 07, 2012 at 10:30:40PM +0800, Wilkinson, Alex wrote:
> (restore line breaks)
>
> Hi all,
>
> I have recently been doing extensive testing of SRSS 5.3 + RHEL. I have found
> a
> 'show-stopper' problem with a fresh brand new install of RHEL 5.{3,7}-Release
> (with
> no updates) + a fresh install of SRSS 5.3.
>
> All prerequisites for SRSS 5.3 are installed. SRSS installs perfectly. I have
> a
> shared interconnect setup (-A -L on) and firmware is pushed out fine. The
> policy
> is the default "-a -M -d -z pseudo -g". GDM is set to accept remote XDMCP
> connections.
>
> The problem I have is that when the DTU bootstraps and gets to the point of
> loading the GDM login screen all i see is a mouse pointer and a black
> background, after a number of seconds the DTU resets and this loops over and
> over and over again. Note: This is a clean vanilla install with very little
> config done.
>
> So, AFAIK these days I can use the out-of-the-box gdm as long as its greater
> than 2.16 i.e with multi-seat support - which i am: gdm-2.16.0-46.el5. I also
> believe that /etc/gdm/custom.conf doesnt need to be modified as the SRSS
> installer does that for me. Could this be a PAM issue ? I dont see anywhere
> where it tells me I need to modify PAM with SRSS 5.3 (I assume the installer
> does this now).
>
> Here is a snippet of /var/opt/SUNWut/log/messages:
>
>
> Jun 7 16:41:20 lab-box utauthd: Worker2 NOTICE: CONNECT
> IEEE802.0021289031d0, pseudo.0021289031d0, all connections allowed
> Jun 7 16:41:21 lab-box utauthd: Worker2 NOTICE: MTU = 1500
> Jun 7 16:41:21 lab-box utdtsession: Add (11,pseudo.0021289031d0,special)
> Jun 7 16:41:21 lab-box utauthd: Worker2 NOTICE: SESSION_OK
> pseudo.0021289031d0
> Jun 7 16:41:21 lab-box utstoraged[9263]: Restarting ...
> Jun 7 16:41:21 lab-box utdtsession: Delete (11,pseudo.0021289031d0)
> Jun 7 16:41:21 lab-box gdm[2961]: gdm_socket_handler: Accepting new
> connection fd 9
> Jun 7 16:41:21 lab-box gdm[2961]: Handling user message: 'VERSION'
> Jun 7 16:41:21 lab-box gdm[2961]: Handling user message: 'SERVER_BUSY'
> Jun 7 16:41:21 lab-box utauthd: SessionManager0 NOTICE: EMPTY: ACTIVE session
> Jun 7 16:41:22 lab-box gdm[2961]: Connections is 1, max is 15, busy FALSE
> Jun 7 16:41:22 lab-box utauthd: Terminator NOTICE: DISCONNECT
> IEEE802.0021289031d0, pseudo.0021289031d0 session terminated
> Jun 7 16:41:22 lab-box gdm[2961]: Handling user message: 'CLOSE'
> Jun 7 16:41:22 lab-box utauthd: SessionManager0 NOTICE: TERMINATE: ACTIVE
> session
> Jun 7 16:41:22 lab-box gdm[2961]: gdm_socket_handler: Accepting new
> connection fd 9
> Jun 7 16:41:22 lab-box utauthd: Terminator NOTICE: DESTROY
> pseudo.0021289031d0 lifetime=1560
> Jun 7 16:41:22 lab-box gdm[2961]: Handling user message: 'VERSION'
> Jun 7 16:41:22 lab-box gdm[2961]: Handling user message: 'GET_CONFIG
> daemon/ServAuthDir :11'
> Jun 7 16:41:22 lab-box gdm[2961]: Handling user message: 'AUTH_LOCAL
> 9a35770777aa1291bb1769aa3ca36296'
> Jun 7 16:41:22 lab-box gdm[2961]: Handling user message:
> 'REMOVE_DYNAMIC_DISPLAY 11'
> Jun 7 16:41:22 lab-box gdm[2961]: Handling user message: 'CLOSE'
> Jun 7 16:41:23 lab-box utauthd: Worker2 NOTICE: CLAIMED by
> StartxlationSession.m3 NAME: pseudo.0021289031d0 PARAMETERS: {terminalIPA=2
>
>
> Do I need to manually configure GDM still ? Do I need to manually configure
> PAM still ?
>
> Also, I'm experiencing this exact behaviour on RHEL 5.3 and 5.7. I have done
> at
> least 4 clean re-installs of both and can consistently produce the
> aforementioned.
What is in /var/log/gdm/* ?
--
+-------------------------------------------+
| Marcel Telka e-mail: [email protected] |
| homepage: http://telka.sk/ |
| jabber: [email protected] |
+-------------------------------------------+
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
