[SunRay-Users] SLES10SP2 and SRSS 4.2EA2 issues
Bob Doolittle
Robert.Doolittle at Sun.COM
Fri Oct 9 22:56:54 EEST 2009
Marc,
Do you have a headless server? If so, the last few lines are normal with
EA2 - it will keep trying to spawn display :0 and fail.
There's a fix which went in after EA2 which causes it to stop trying
after a couple of iterations, but the looping in EA2 is harmless other
than consuming some CPU cycles. XKeepsCrashing is what GDM calls after
it tries to spawn a display a few times and fails.
The gdm_config_parse line is more alarming (and may be the cause of the
following failures if your server isn't headless).
Take a look at your /etc/X11/gdm/custom.conf file and see if you can
spot it specifying some executable that's not on your system. If all
else fails, send a copy of that file to the list.
You don't mention it, but I presume you ran "utadm" with either the -A,
-a, or "-L on" options? I don't think you'd get as far as 26 if you
didn't...
-Bob
Juarez, Marc wrote:
> Bob,
>
> Thanks for your quick reply.
>
> This morning I ran utinstall -u and cleared out the links that I created
> manually. I rebooted before and after the reinstall and the daemons have
> started and utconfig ran without issue. Although, I am still stuck at error
> code 26? It seems that my machine is unable to start an X server?
>
> Did I miss a critical step during installation?
>
> Tried from softray, 2FS, and now a tadpole unit all giving the same 26 error
> code?
>
> Oct 9 12:22:02 src at display-san-linux-01 utauthd: Worker3 NOTICE:
> whichServer pseudo.001b3873f1c4:
> Oct 9 12:22:02 src at display-san-linux-01 utauthd: Worker3 NOTICE: CLAIMED by
> StartSession.m7 NAME: pseudo.001b3873f1c4 PARAMETERS: {stealProtected=true,
> terminalIPA=10.50.202.17, type=pseudo, fw=Tadpole-mb02-V3.6.1-0101,
> state=disconnected, cause=insert, doamgh=true, barrierLevel=3.0.0,
> lockaction=disconnect, rawId=001b3873f1c4, terminalCID=IEEE802.001b3873f1c4,
> MTU=1420, tokenSeq=1, firstServer=0a2b188f, namespace=IEEE802, ddcconfig=1,
> clientRand=o44IiS3kHyXtKFTCnRVjLDeBU75aL4y/tUMmno4Kv8K, id=001b3873f1c4,
> realIP=0a32ca11, startRes=1280x800:1280x800, useReal=true, event=insert,
> sn=001b3873f1c4, rawType=pseudo, hw=Tadpole-mb02, initState=1,
> usersession=false, _=1}
> Oct 9 12:22:02 src at display-san-linux-01 utauthd: Worker3 NOTICE: CONNECT
> IEEE802.001b3873f1c4, pseudo.001b3873f1c4, all connections allowed
> Oct 9 12:22:02 src at display-san-linux-01 utauthd: Worker3 NOTICE: MTU = 1420
> Oct 9 12:22:02 src at display-san-linux-01 utdtsession: Hotdesk
> (14,pseudo.001b3873f1c4,default)
> Oct 9 12:22:03 src at display-san-linux-01 utauthd: Worker3 NOTICE: SESSION_OK
> pseudo.001b3873f1c4
>
>
> grep gdm /var/log/syslog
>
> Oct 9 09:58:24 src at display-san-linux-01 shadow[8838]: group already exists
> - group=gdm, by=0
> Oct 9 10:03:48 src at display-san-linux-01 gdm[6741]: gdm_config_parse:
> Chooser not found or it can't be executed by the GDM user
> Oct 9 10:03:49 src at display-san-linux-01 gdm[6816]:
> gdm_slave_xioerror_handler: Fatal X error - Restarting :0
> Oct 9 10:03:54 src at display-san-linux-01 gdm[7164]:
> gdm_slave_xioerror_handler: Fatal X error - Restarting :0
> Oct 9 10:03:58 src at display-san-linux-01 gdm[8121]:
> gdm_slave_xioerror_handler: Fatal X error - Restarting :0
> Oct 9 10:03:58 src at display-san-linux-01 gdm[6741]: deal_with_x_crashes:
> Running the XKeepsCrashing script
>
> Your assistance is greatly appreciated.
>
> Thanks
>
> -Marc
>
>
>
> On 10/9/09 2:00 AM, "sunray-users-request at filibeto.org"
> <sunray-users-request at filibeto.org> wrote:
>
>
>> Date: Fri, 09 Oct 2009 01:04:41 -0400
>> From: Bob Doolittle <Robert.Doolittle at Sun.COM>
>> To: SunRay-Users mailing list <sunray-users at filibeto.org>
>> Subject: Re: [SunRay-Users] SLES10SP2 and SRSS 4.2EA2 issues
>> Message-ID: <4ACEC469.4070708 at Sun.COM>
>> Content-Type: text/plain; format=flowed; charset=windows-1252
>>
>> It appears that you forgot the mandatory reboot after running utinstall.
>>
>> After utinstall the product is installed, but not yet activated.
>> Activation occurs currently during the subsequent reboot.
>> One of the activation scripts is responsible for creating these links.
>>
>> -Bob
>>
>> Juarez, Marc wrote:
>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> SunRay-Users mailing list
>>> SunRay-Users at filibeto.org
>>> http://www.filibeto.org/mailman/listinfo/sunray-users
>>>
>>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> SunRay-Users mailing list
>> SunRay-Users at filibeto.org
>> http://www.filibeto.org/mailman/listinfo/sunray-users
>>
>>
>> End of SunRay-Users Digest, Vol 69, Issue 16
>> ********************************************
>>
>
> _______________________________________________
> SunRay-Users mailing list
> SunRay-Users at filibeto.org
> http://www.filibeto.org/mailman/listinfo/sunray-users
>
More information about the SunRay-Users
mailing list