Jim Klimov wrote:
Hello Hana,
As a random shot: there was a blog entry about a rare problem linked
to overflow of an SRSS log file (i.e. limited to 50Mb) in some of the
older releases. I believe that after hitting this limit, the Sun Ray
Server won't write to the log, and won't work because it can't log.
When your problem strikes again, check if this condition fits?
Hello,
this morning three X servers on SunRays crashed again, but they managed
to recover "by themselves". SunRay logs are O.K., but I got messages
Mar 18 09:38:35 chomsky gdm-binary[21840]: WARNING: Failed to start X
server sev
eral times in a short time period; disabling display :16
and the same for display :12 and :13. After the recovery, the affected
SunRays got new numbers of displays, 12, 13 and 16 are not used any more:
$ ll /tmp/SUNWut/config/displays/
total 24
-rw-r----- 3 root utadmin 240 2008-03-18 09:39 11
-rw-r----- 3 root utadmin 240 2008-03-17 10:35 14
-rw-r----- 3 root utadmin 240 2008-03-18 10:05 15
-rw-r----- 3 root utadmin 240 2008-03-18 09:51 17
-rw-r----- 3 root utadmin 224 2008-03-18 04:04 18
-rw-r----- 3 root utadmin 240 2008-03-18 09:50 19
I suspect that the files 12, 13 and 16 disappeared from
/tmp/SUNWut/config/displays/, because gdm complains about it:
$ cat /var/log/gdm/:12.log
Fatal server error:
SunRay Session map does not exist (display 12)!
I think that if gdm(?) can make a new display (with new number), the
server recovers, but if it can't do that I have to restart X server(s)
manually. Any idea why this is happening and how to prevent it?
Hana
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
