I had been running SRSS 3.1 for a while on older Nevada builds, then I upgraded (fresh install) to snv_117 (x86). I couldn't get SRSS 3.1 (also a fresh install) to work - all the DTUs just sit in state 26 D.
So I installed and configured SRSS 4.1 (10/08) instead, and the behavior is exactly the same (modulo the different graphics on the OSD) - state 26 D. I observed that dtlogin and Xnewt are running (and not dumping core or otherwise being restarted) for each DTU, and each DTU shows up in utwho -a and utsession -p. The most suspicious thing in /var/dt/Xerrors is a lot of "connect: Connection refused" messages but they are all from when I was still running SRSS 3.1. Since installing and configuring SRSS 4.1 and rebooting, I don't see any message there that looks like a fatal error. There are messages about SO_KEEPALIVE and SO_LINGER: Option not supported by protocol. A complete copy is here: http://www.omnicron.com/~ford/Xerrors I did change the dtlogin args to eliminate the "-udpPort 0" args as is supposedly needed on some (older?) Nevada builds. Is there any other configuration I need to do for running on OpenSolaris? What should I do next to diagnose the "26 D" state? Thanks in advance, -=] Mike [=- _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
