We are running SRSS 4.2 on SLES 10 SP3 32-bit with 3 hosts in a FOG and
49 SunRay2-P8-DTUs, FW 4.2_77_2009.10.19.17.01 on a dedicated interconnect.
We do not use kiosk-functionality, all sessions (smartcard and
non-smartcard) are default UNIX sessions on the SunRay-server.

Since our recent upgrade to SRSS 4.2 we observe the following problem:
when a DTU moves to a new server (by load-balance policy or after a user
logout) the corresponding device-directory IEEE802.<mac-address> is not
moved by the utdevmgr to the /tmp/SUNWut/units-directory of the new
host, but stays on the host which first got in contact with this
specific DTU.

So every single DTU has a correct device directory on one of the servers
in the FOG, but unfortunately not necessarily on the particular one the
DTU-session is currently connected to.

This leads to at least the following bad behaviour:
- $UTDEVROOT is invalid due to missing link target.
- DTU-Hardware, especially USB-Thumbdrives cannot be used.
- utdiskadm -l gives: utdiskadm: Cannot locate device root directory

When explicitly using utswitch/utselect, the device directory DOES get
moved to the target host and everything works fine, but logging out from
this switched session does not move the directory back to the original host.

When we stop Core Services on a host via /etc/init.d/utsvc stop, all
DTU-device-dirs are immediately redistributed and new greeter sessions
are started on the other two FOG-hosts.

Since SRSS 4.2 we also notice a different load-balance behaviour:
load-balance redirection now sometimes occurs at user-login-time,
eventually disconnecting a running idle-session on a DTU and choosing a
new lower loaded host; the disconnected idle-sessions get discarded
after a timeout (~15 minutes) if not reused.
This is presumably intended behaviour to make the balancer more
accurate, but may be related to our problem.

The issue may be similar to what is observed here:
http://www.mail-archive.com/[email protected]/msg15431.html
but we made sure that it is not a permission problem on /tmp, neither on
/tmp/SUNWut (we removed /tmp/SUNWut on all hosts and restarted the farm,
thus creating the tree by scratch).
We don't have any sort of firewall or packetfilter running between the
hosts, utgstatus permanently reports TN/UAM for all servers on the
interconnect.

We also tried running the utdevmgrd with the -d(ebug) option but were
unable to spot any errors in the output due to missing in-depth knowledge.

It's also notable that this problem did not exist when using SRSS 4.1.

So we are a bit lost here,
any hints or ideas are strongly appreciated,
thanks in advance,

Nico
-- 
                      Nico Behrent  |  University of Kaiserslautern
           IT Administration - CTO  |  Department of Mathematics
      [email protected]  |  Building 14 - Room 428
 phone +49 631 205-3925, fax -4737  |  D-67653 Kaiserslautern
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to