Hi, I have SRSS 4.0 installed on CentOS 4.6 (RH AS 4 clone) running on
an VMWAre ESX 3.5 server. This works great but for two things.

After about a week of uptime the system seems to lock up. I've
configurued SRSS to require smartcards for logon, but when I insert a
card into one of the SunRay clients the client gets stuck showing one of
the status icons 26D or sometimes 11D. I've looked this up, and
according to http://www.sun-rays.org/lib/sunsolve/77966.html it
translates into: "The Sun Ray has connected to the server and is waiting
for graphics traffic (this is the GNC state)" and "Server is
authenticated by the Sun Ray and the graphic/keyboard network connection
is encrypted. [snip]...." Which doesn't tell me much, besides that a
connection is established, but then hangs. I'm still able to login
locally, so it's something wrong with SRSS.

If I reboot the CentOS installation everything works fine for another
week or so. Has anyone experienced similar behaviour?

My auth_log files are filled with entries like:

/opt/SUNWut/lib/utdtsession[602]: cannot create
/var/opt/SUNWut/displays/.tmp.17690: No such file or directory
Error: couldn't create display file
05/19/2008 02:11:43 Cannot stat displays directory
mkdir: cannot create directory `/var/opt/SUNWut/tokens': File exists
mkdir: cannot create directory `/var/opt/SUNWut/tokens': File exists
mkdir: cannot create directory `/var/opt/SUNWut/displays': File exists
mkdir: cannot create directory `/var/opt/SUNWut/dispinfo': File exists
file: No such file or directory
Lock file  exists

which indicates that somehow some lock file doesn't get removed, but why?

Secondly, when I've been trying to analyse the above problem I've been
using the web management GUI for looking at the log files. I could just
as well have done it any other way, but I figured that the management
GUI would list the most relevant log files. When trying to access some
of the files I'm _sometimes_ returned to the login page. Unfortunately
I've not been able to reproduce this just now. The detailed error
message states something about Java being out of memory. Is this a known
problem? This isn't a big issue, but I gets me a bit worried as the
whole thing seem rather flaky...

Regards,
Øystein

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to