My one true talent is finding the weird problems that have no explanation.
David Barron Zencos Consulting LLC david.barron@zencos.com 919-480-2761 (office) 919-995-2356 (mobile)
-----Original Message----- From: Stefan Baur <X2Go-ML-1@baur-itcs.de> Sent: Wednesday, October 31, 2018 4:23 PM To: David Barron <DBarron@zencos.com>; x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Broker and resuming sessions
Am 31.10.18 um 21:10 schrieb David Barron:
Yes, is the problem also present when you try to use the broker via SSH instead of HTTP? I don't know, I've never been able to figure out how to use ssh. The documentation on that is sparse.
That's why we have the Demo environment install scripts, where you get a fully configured setup from which you can copy settings/configs.
E.g. <https://wiki.x2go.org/doku.php/doc:howto:x2gobroker?do=export_code&codeblock=9> creates two desktop entries on the demo client, one for the HTTP, one for the SSH broker access. See the section below "COMMENT: This last step creates an X2GoClient-in-Broker-Mode desktop entry"
As you can tell from there, the ssh broker URL would be something like ssh://x2gobroker1.x2go.example.com:/usr/bin/x2gobroker-ssh In this case it's ssh://<hostname>:22/bin/x2gobroker Using that I can log in but I'm seeing the same behavior
Did you run x2gobroker-keygen on the broker server? Yes. Should I run it again?
At the moment, it doesn't sound like you should.
Did you invoke x2go-pubkeyauthorizer with the proper parameters on all required machines? If so, you should have the same authorized_keys file in /var/lib/x2gobroker/.ssh/ on the three servers as well as on the broker. Yes.
Did you compare the content of the files, or merely verify their existence?
Should I run it again? Again, the documentation is sparse, so what parameters would I use? If the files all have the identical content, no.
If they differ, copy /var/lib/x2gobroker/.ssh/authorized_keys from the broker to the three X2Go servers, that should keep you from having to re-run the command.
Also, please run
x2goclient --debug >x2goclientlog 2>&1
when you try to connect to the suspended session.
Make sure x2goclientlog doesn't contain any information you don't want us to see (i.e. if necessary, replace IPs with dummy IPs, same goes for usernames and passwords that might show up - though passwords shouldn't be visible there), then post the content of the file here.
The x2go client is running on windows so this won't work. I tried installing it on the linux servers but the yum command complained about missing libraries (again) and I gave up on it. I ran x2goclient.debug with the --broker-url and got this output
C:\Users\dbarron>cd "C:\Program Files (x86)\x2goclient"
C:\Program Files (x86)\x2goclient>x2goclient.debug --broker-url=http://agmrkgrid login3:8080/plain/inifile x2go-INFO-1> "Starting X2Go Client..." x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." x2go-INFO-3> "Started X2Go Client." x2go-INFO-8> "Starting connection to server: agmrkgridcomp7:22" Generating public/private rsa key pair. Your identification has been saved in C:/Users/dbarron/.x2go/ssh/gen/key.l12912.
Your public key has been saved in C:/Users/dbarron/.x2go/ssh/gen/key.l12912.pub.
The key fingerprint is: SHA256:D7E8eEDuG1HAPI2skjGuLMM/X9y1rVFOW0q3HBScDZc X2Go Client RSA user key The key's randomart image is: +---[RSA 4096]----+ | +o+. oo=| | o o*.. Eo| | . + .+.. . | | + .. = o . | |o. . + S . + + | |+o .+.+. B * o| |... .o ..o = o | | o . o | | o. . | +----[SHA256]-----+ QProcess: Destroyed while process is still running.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243