[SunRay-Users] SLES10SP2 and SRSS 4.2EA2 issues

Juarez, Marc mjuarez at qualcomm.com
Fri Oct 9 07:27:42 EEST 2009


SR Admins,

I am attempting to standup a Linux Sunray server and I have seem to have hit a wall.  I am running SLES10SP2 and SRSS 4.2EA2. To complete the installation and to successfully run utconfig I needed to make the following modifications...

In /usr/lib/

 *   lrwxrwxrwx   1 root bin         30 2009-10-06 21:27 liblber.so.199 -> /usr/lib/liblber-2.2.so.7.0.20
 *   lrwxrwxrwx   1 root bin         19 2009-10-06 21:22 libldap.so.199 -> /usr/lib/libldap.so

In /etc/opt/SUNWut/
lrwxrwxrwx  1 root bin       20 2009-10-08 14:45 jre -> /usr/bin/jre1.6.0_13

Did I miss a step? Shouldn’t the installer taken care of this for me? If not, can this be documented in the final release documentation?

Also, in our environment the default runlevel is 3 as the majority of our machines are lsf compute nodes using blade hardware.  I noticed that the sunray services in linux are set to start on boot at runlevel 5?  Is this needed even if we are using headless servers?  Watching the console I see X errors after every reboot at runlevel 5 as the default, not really a big deal just want to make sure my config is correct.

On to the real issue at hand, after a reboot of my 2FS dtu and softray client both are stuck at error code 26.  Log states the following...

Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: DISCONNECT IEEE802.00144f7fcf98, pseudo.00144f7fcf98 reauthenticatingDuplicateTID
Oct  8 19:06:03 src at display-san-linux-01 utauthd: SessionManager0 NOTICE: TERMINATE: ACTIVE session
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 UNEXPECTED: during send to: java.net.SocketOutputStream at eb017e error=java.net.SocketException: Connection reset
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: DESTROY pseudo.00144f7fcf98 lifetime=2081102
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: whichServer pseudo.00144f7fcf98:
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: CLAIMED by StartSession.m7 NAME: pseudo.00144f7fcf98 PARAMETERS: {stealProtected=true, terminalIPA=10.43.172.205, type=pseudo, fw=GUI4.2_49_2009.08.27.18.08,Boot:MfgPkg_4.15_2006.07.20.16.57; 2006.07.20-17:04:56-PDT, state=disconnected, cause=insert, doamgh=true, barrierLevel=420, lockaction=disconnect, rawId=00144f7fcf98, terminalCID=IEEE802.00144f7fcf98, MTU=1500, tokenSeq=1, firstServer=0a2b188f, namespace=IEEE802, keyTypes=dsa-sha1-x1,dsa-sha1, ddcconfig=1:0, clientRand=lGGNDUdCHbjnPIvY5ldvHa4plesqvh1VddV60RschZe, id=00144f7fcf98, realIP=0a2baccd, startRes=1600x1200:1600x1200, useReal=true, event=insert, sn=00144f7fcf98, rawType=pseudo, clientKeyStatus=unconfirmed, hw=SunRayP8-FS, initState=1, usersession=false, _=1}
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: CONNECT IEEE802.00144f7fcf98, pseudo.00144f7fcf98, all connections allowed
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: MTU = 1500
Oct  8 19:06:03 src at display-san-linux-01 utdtsession: Hotdesk (15,pseudo.00144f7fcf98,default)
Oct  8 19:06:03 src at display-san-linux-01 utauthd: Worker7 NOTICE: SESSION_OK pseudo.00144f7fcf98

I am thinking that this is a GDM issue as it seems that X does not want to start.  What script starts up GDM?  It seems to be running on my system:

ps aux | grep gdm
root      6375  0.0  0.0  45136  3176 ?        S    18:30   0:00 /usr/sbin/gdm-binary

/etc/X11/gdm/custom.conf  looks good:

# SUNWut BEGIN - do not edit
VTAllocation=false
DynamicXServers=true
Greeter=/usr/libexec/gdmgreeter
BaseXsession=/etc/opt/SUNWut/gdm/Xsession.source_wrapper
RebootCommand=
HaltCommand=
XKeepsCrashing=/etc/opt/SUNWut/gdm/XKeepsCrashing.sunray
# SUNWut END

Syslog errors

Oct  8 18:30:05 src at display-san-linux-01 gdm[6375]: gdm_config_parse: Chooser not found or it can't be executed by the GDM user
Oct  8 18:30:07 src at display-san-linux-01 gdm[6480]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Oct  8 18:30:11 src at display-san-linux-01 gdm[7573]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Oct  8 18:30:15 src at display-san-linux-01 gdm[7757]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Oct  8 18:30:15 src at display-san-linux-01 gdm[6375]: deal_with_x_crashes: Running the XKeepsCrashing script
Oct  8 18:30:28 src at display-san-linux-01 gdm[6375]: Failed to start X server several times in a short time period; disabling display :0

I have setup/configured many sunray FOGs under solaris and never really experienced this much grief under solaris.

Lastly, does anyone know the official release date of SRSS 4.2?  Any plans of NSCM being supported under LINUX?

Thanks

-Marc














-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.filibeto.org/pipermail/sunray-users/attachments/20091008/12d3441d/attachment-0001.html>


More information about the SunRay-Users mailing list