SunRays only connect after reboot.
I'm having a problem where I can only get my SunRays to work if they were physically powered up when the server boots. If I have one unplugged while the server is booting, it will just hang on the "26b" screen until I reboot the server again!
Tends to be a problem since if someone's in the office while I do the updates that require reboots, they often get tired of hearing that terrible clicking sound the SunRays make while the server is not available. So, they pull the power to the SunRay. Server boots up, they plug the SunRay in later when they want to use it. SunRay won't connect until I reboot again!
[626 byte] By [
DoxBriana] at [2007-11-26 17:57:07]
# 1
Sounds like your X display manager might be hanging or dying shortly after the reboot. SRSS depends on the Display Manager to launch X servers for new Sun Rays as they make contact with the server. At least that's the case for sessions that are given traditional logins. If you're using the CAM kiosk feature then the Display Manager is not involved, and if you're using the NSCM feature the Display Manager is not involved until after the NSCM greeters have been satisfied. In those cases the problem would be someplace else.
What release of SRSS are you using, on what Operating System, and what are you expecting to see on these Sun Rays? (A normal login greeter, an NSCM greeter, a CAM session, something else?)
Whatever the answers are my first step would be to make sure that I was up to date on patches for SRSS and the Display Manager. The Display Manager is 'dtlogin' on Solaris, and Sun Ray's own build of GDM on Linux.
# 2
AFAIK, it's the latest version, just downloaded and installed maybe 4-6 weeks ago. No special configs at all (essentially everything's in default mode, just as it installed). Did find out about a patch for USB devices on SunRays and installed that recently, but it didn't fix anything (not even my USB problems). This is on Solaris 11/06, patched with all the current stuff (except for 5 of the ones that JUST came out that won't install, but they won't install on any of the machines I admin...).
I should be seeing the normal login greeter thing. Another interesting note is that SunRays that have cards in them when started won't work if the card is removed, and if they don't have a card in during boot, they won't work if a card is stuck in. However, once a session is ON a card, you can carry it to a SunRay that didn't have a card and login fine...
# 3
More than likely you set the secure feature in the install of sol10 11/06. Its the last question that asks if you want to disable non secure services. I did the same thing and apparently that shuts down the dtlogin in a way that causes what you are experiencing. I did a
# netservices open
and everything worked fine after that.
# 4
Hmmm, very interesting. I'll have to compare service lists between an older install that I have and this one. I'm hesitant to just blow all the services open like that... VERY helpful information though, gives me a place to start!Thanks!
# 5
There's a very good chance that this is the result of a bug that was introduced into dtlogin in S10 update 3. (The bug is also in Solaris Express and in OpenSolaris.) The bug causes dtlogin to fail to start new X servers if it has been instructed to not listen for XDMCP requests, as happens when 'netservices limited' is in force. The fix will be available in a patch but in the meantime you can apply one of the workarounds discussed at http://blogs.sun.com/ThinkThin/entry/sun_ray_on_opensolaris_work.
The bug ID for the fix is 6524040 if you'd like to log a support call against it.
# 6
Thanks for the info!Unfortunately, that machine suffered a hard drive failure Friday morning, so this is the least of my problems... However, this info will come in handy once I get it going again!
