Re: [X2Go-User] connection failed.

2021-11-18 Thread Ilaria Sani
Dear All,

I am following up with my previous post as I am still stuck and unable to use 
X2go.

I have a crashed session and I am unable to close.

Does anyone have any suggestion?

Thanks!
Ilaria

From: x2go-user  On Behalf Of Ilaria Sani
Sent: Monday, November 15, 2021 12:06 PM
To: Ulrich Sibiller 
Cc: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] connection failed.


Thank you for your prompt reply!!!

Please, find my answers below




On Mon, Nov 15, 2021 at 10:57 AM Ilaria Sani 
mailto:ilaria.s...@unige.ch>> wrote:
> I have used it successfully for a couple of weeks.
>
> Then, once, I got the following error message while attempting login 
> (windows10):
>
> Failed to start X2Go Agent session with ID xxx. X2Go Agent terminated 
> unexpectedly. Aborting session startup.
>
> I tried to
>
> restart PC
> unistall-reinstall
> delete session-recreate session
> exit putty-re-entering
>
> I have no more attempts to do.
>
> I have used other clients before, and for one of those this sometimes would 
> happen.

Sometime vcxsrv crashes and leaves the remote x2goagent in a bad state
which results in another crash of vcxsrv on reconnect. The only way to
fix that is to kill the remote session (the remote x2goagent process)
and start a new one. From your text it is unclear if you have tried
that.

I did the following in the x2go GUI: Session-session management-terminate 
session
I also uninstall and re-install X2go, but the crashed session was still there.

> What I was doing was to -kill geometry in putty and then re-do one.

What do you mean by that?
I was using a command line in putty terminal that would kill anything pending 
and then I was re-configuring the geometry upon the next re-start.
I do not remember exactly what the command line was about, but I remember it 
was using -kill and -geometry flag.
Sorry I wish I could be more specific. Anyway I was using TightVNC and not 
X2go. Likely it does not applies.

> Is there something similar I can do here?

You can try to use mobaxterm to connect to your server and see if you
can run "x2goagent :1" there.  If that does not work, that's the
reason for the connection problems. If  it works, then we need to
search the problem elsewhere.

I cannot use mobaxterm, because my institution (and relative cluster I am 
trying to connect to) only supports X2go.

> I tried to visualize the Archive of this mailing list but I could not find a 
> way to search previous posts.

see https://lists.x2go.org/listinfo/x2go-user respectively
https://lists.x2go.org/pipermail/x2go-user/

I had seen the list of Archived posts 
(https://lists.x2go.org/pipermail/x2go-user/).
I started searching by clicking on the first Thread or Subject, then the 
second, third, and so on...
I was wondering is there was a way to visualize them all in a long list so that 
one can ctrl-F keywords.


Thank you again for your kind support.

Ilaria
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


[X2Go-User] X2Go TCE pxe complications

2021-11-18 Thread MacGregor Family
Hello,

I have been given a couple of Termtek TK-3550 thin clients and I am
trying to set them up to open into my Ubuntu 20.04 server at my home
over our ethernet LAN. These devices don't have much memory so I have
been following the instructions to install the "Classic, NFS-
filesystem-based X2Go TCE". I have setup a Virtual Box VM, running
Ubuntu 20.04 with a bridged network adapter and a permanent IP address,
to be the pxe server. I have followed the instructions as best I was
able but I am still having difficulties.

I think one problem is likely to be that our cheap router, which
provides our DHCP server, does not allow me to nominate the "next-
server" or the filename. In an attempt to address this I have installed
dnsmasq on the pxe server VM and am running dnsmasq. The dnsmasq.conf
is as follows:
port=0
log-dhcp
dhcp-range=192.168.1.0,proxy
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/srv/tftp  (I have also tried tftp-
root=/opt/x2gothinclient/chroot on this line)


The thin client is set to boot over LAN and the dhcp-log on the pxe
server looks like this when I turn the thin client on:

I'm clearly a complete novice but it seems the thin client is finding
its way to the pxe server. Unfortunately the thin client trys to boot
until it times out, reporting:
"No boot filename received". It then just boots its decades old version
of Windows CE. Note that when I changed the tftp-root path in dnsmasq
from /opt/x2gothinclient/chroot to /srv/tftp it had some effect on the
dhcp log (it nominated its terminal id in a second line) but the nett
result did not change. I should add that I have exported both
/opt/x2gothinclient/chroot and /srv/tftp with the NFS server. I only
switched to /srv/tftp because that's where pxelinux.0 is and I assume
that is the file it is looking for and failing to find.

Basically I have been trying to get this working for a couple of days
without success, I have decided to seek expert help. I apologise for my
ignorance, I understand that hobbists like myself are probably
incredibly annoying.

Regards
Stuart MacGregor
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user