Alejandro et al:
Looking at loads on our network switch and other network measures seems
to show no network-related issues.
Here is the output of iostat and vmstat at a time with it is taking 2+
minutes to start a new Sunray session. It also seems to take a long
time to exit a session. However, suspending and re-starting an existing
session ... by either removing a SmartCard or suspending a NSCM session
with Shift-Pause respond quickly. That fact would seem to confirm that
network delays between the Sunrays and the server is not the problem.
root@flare # iostat
tty sd2 sd5 nfs1 nfs2 cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us
sy wt id
0 369 0 0 0 72 8 98 0 0 0 248 13 222 7
3 0 90
root@flare # vmstat
kthr memory page disk faults cpu
r b w swap free re mf pi po fr de sr s2 s5 -- -- in sy cs
us sy id
0 0 0 33278716 27659568 695 3582 68 2 2 0 15 -0 8 0 0 3813 19722 4672
7 3 90
Can anyone point me to the list of things that happen when a new session
is created? Is there a way of somehow timing the steps in that process
to see where the delays are occuring?
Nike Waibel wrote:
Hmmm - how about DNS and the authentication service?
Is there a good means of determining how well the authentication service
is performing? Or DNS, for that matter ... I can see that DNS is
working but don't know to determine if it is slow or not. Is DHCP
called each time a new SunRay session is called or does each SunRay only
get a new IP address when the UT services are started?
Thanks for your input,
John
On 2/25/2014 9:18 AM, Alejandro Soler wrote:
Hi, did you check the network speed?
Can you take a iostat and a vmstat ?
Try to restart the server.
regards
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
