"Lost session; trying to reconnect ..." implies that the X server is
unable to establish a connection with utsessiond.
Are there two copies of utsessiond running? One should be the parent,
and acts as a restart daemon - if the utsessiond child dies it will
simply restart it.
If you see them running, try and see if the child is sane. You should
be able to connect to utsessiond using telnet, and simply issue an
"exit" command, and it should respond with "OK/exit":
% telnet localhost utsessiond
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
exit
OK/exit
Connection to localhost closed by foreign host.
utsessiond's job is to broker between utauthd and Sun Ray desktop
services to pass along hotdesking events (connect/disconnect). Without
it services (like the X server, or utaudio) can't know when they're
supposed to service Sun Rays.
-Bob
Knut Talman wrote:
The same happens when I terminate a session (e.g. via Web interface).
Xnewt is being terminated not restarted. Unfortunately I don't know
how to debug it. I always have to reboot the server to get it working
:-(
Knut
2008/5/1 Knut Talman <[EMAIL PROTECTED]>:
After some playing we now see a different picture:
After booting everything seems fine, all DTU's are getting their logon
screens. When I then e.g. configure kiosk mode or anything else which
needs a cold restart of the servers in my FOG I then have all DTU's
hanging in 26 D after the cold restart. When I look at the processes
there are no Xnewt running. The logfile of gdm /var/log/gdm/:20 shows
------------------------------------------------------------------------------------------------------------
Could not init font path element /opt/kde3/share/fonts, removing from list!
Can't open /var/dt/bw.20
Can't open /var/dt/st.20
Server pid 7644
Lost session; trying to reconnect ...
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Connection refused
connect: Interrupted system call
Fatal server error:
Session Error - retry limit
------------------------------------------------------------------------------------------------------------
If I then start Xnewt :20 manually I get a grey screen on my the DTU
(but no gdm of course). I'm totally lost here...
There is no firewall installed on the SLES machine.
Best regards, Knut
2008/5/1 Lars Tunkrans <[EMAIL PROTECTED]>:
hi,
>
> Weird indeed , I start thinking that maybe SLES is doing some form
> of blacklisting the DTU mac or ipadress .
>
> Is there an O/S level firewall installed ?
> What happends if you change the IP address of the DTU ( use the menu
> in the GUI-firmware )
>
> //Lars
>
>
>
> Knut Talman wrote:
>
> >
> >
> >
> > Hi all,
> >
> > we are running (or testing) SRSS 4.0 with patches 127555-01 on SLES 10
> > SP1. After installation of two servers and running through all
> > configuration tasks (utconfig, utadm, utreplica, utfwsync) on both
> > hosts we see logon screens. After some seconds or minutes we have a
> > 26D on some DTU and the following entry in /var/log/messages:
> >
> > Apr 30 22:40:48 sles10host java: utadt:: username={admin}
> > hostname={sles10host.mydom.dom} service={Sessions} cmd={}
> > message={Session with token=pseudo.00144f7dd59e and display number=17
> > on sles10host has been terminated} status={0} return_val={0}
> >
> > and we can't get it alive again until a reboot of both servers. Even a
> > cold restart would do nothing, only a reboot helps.
> >
> > Has anyone any idea? At least where to start searching?
> >
> > Thanks,
> >
> > Knut
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
