Hello,
I believe the comments about headless systems and 26D are incorrect, and
you should not be misled by them. Your problem lies elsewhere.
I would look at your /var/dt/Xerrors file to see if there are any error
messages indicating your X server is crashing.
I would configure coreadm to ensure that Xnewt core dumps get put in
some global directory where you can find them if they occur.
I would verify that you have not restricted 'ulimit -c' to prevent core
dumps of Xnewt.
If you can isolate an Xnewt core dump run pstack on it and send us the
output.
Good luck,
Bob
Mohamed Ali Abdullah wrote:
Dear all,
Thanks for your reply.
I would like to share information based on my sunray environment here.
Currently, our users are seeing OSD26D on their SR270. Not all the
users sees 26D at one time But it's randomly appears to users.
Can provide me any thought on my case?
Regards,
Alisampras
Mohamed Ali Abdullah schrieb:
> Dear forum users,
> > I came across this document "SRSS-4.1 Installation and
Configuration > Guide for the Solaris OS" and on page 45, it stated
about headless > SunRay server and a file called
Xservers.SUNWut.prototype. I have few > doubts regarding this;
> > 1) My SunRay servers doesn't have a graphic card. Do the
headless > setting is Mandatory for me?
>
It depends.
Even if you server has no conventional graphics card, it may have a
service processor, which provides a remote graphical console. In that
case your server is effectively not headless.
The reason for this setting is that the dtlogin display manager,
which is needed for managing Sun Ray displays may fail trying to
start a graphical session on non-existent hardware. Some recent
versions of the display manager may be resilient against this
condition and not fail when the can't start a configured console
display. If that is the case, you don't need the settings.
> 2) What if i don't set the headless setting, would it going to
impact my > DTUs?
>
If it causes a problem, it will impact the server-side services, in
particular the display manager. You'll notice that right away, as
your DTUs will be stuck without a session, showing OSD code 26 instead.
If everything works without this change you should be fine, but if
the server doesn't work for you, you should apply the change.
> 3) What other problem i will encountered if not set headless?
>
See above
HTH
- Joerg
Bob Doolittle Wrote;
I've never seen such a severe result on a headless system which
leaves :0 in the Xservers file, at least for the last several years.
What typically happens in this case is that dtlogin simply wakes
periodically (every time it gets a HUP? that would be every time a
new display is added or removed by SRSS) and wastes cycles trying to
respawn the server there. The only real deleterious effect is
needless resource consumption, and noise pollution in /var/dt/Xerrors
which might mask a real problem (particularly since that log rolls
off older error messages rather quickly).
-Bob
Craig Bender Wrote;
It stops the Xserver from trying to start on display 0, which since
you don't have a graphics card will result in unnecessary error
messages in your log files.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
