Hi,
Just a quick update on this (I've not resolved it unfortunately)....
I thought I'd try the git version RPMs rather than the EPEL el7 versions, so I'm now running:
x2goserver-extensions-4.0.1.19-0.0x2go2.1.git20160621. 1064.main.el7.centos.x86_64 x2goserver-xsession-4.0.1.19-0.0x2go2.1.git20160621.1064. main.el7.centos.x86_64 x2goserver-4.0.1.19-0.0x2go2.1.git20160621.1064.main.el7.centos.x86_64 x2goagent-3.5.0.32-0.0x2go1.1.git20160615.734.main.el7.centos.x86_64
Again, just trying to start xterm. When I try connecting the client 'hangs' and on the server (with log set to debug) I get the following, which continues until I start killing pids:
Aug 24 10:35:31 login02 sshd[12844]: Accepted publickey for chris from <my machine> Aug 24 10:35:31 login02 systemd-logind: New session 3776 of user chris Aug 24 10:35:31 login02 systemd: Started Session 3776 of user chris Aug 24 10:35:31 login02 systemd: Starting Session 3776 of user chris Aug 24 10:35:31 login02 sshd[12844]: pam_unix(sshd:session): session opened for user chris by (uid=0) Aug 24 10:35:31 login02 /usr/bin/x2golistsessions[12942] x2golistsessions has been called with no option Aug 24 10:35:32 login02 /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 adsl 16m-jpeg-9 unix-kde-depth_32 us auto 1 R xterm both Aug 24 10:35:32 login02 /usr/bin/x2gostartagent: client announced itself as ,,<my IP>' Aug 24 10:35:32 login02 /usr/bin/x2gosessionlimit[13005] x2gosessionlimit has been called Aug 24 10:35:32 login02 /usr/bin/x2golistsessions[13008] x2golistsessions has been called with options: --all-servers Aug 24 10:35:32 login02 /usr/lib64/x2go/x2gogetdisplays[ db_getdisplays called, server: login02; return value: Aug 24 10:35:32 login02 /usr/lib64/x2go/x2gogetports[130 db_getports called, server: login02; return value: Aug 24 10:35:33 login02 /usr/lib64/x2go/x2gogetdisplays[ db_getdisplays called, server: login02; return value: Aug 24 10:35:33 login02 /usr/lib64/x2go/x2gogetports[130 db_getports called, server: login02; return value: Aug 24 10:35:33 login02 /usr/lib64/x2go/x2gogetdisplays[ db_getdisplays called, server: login02; return value: Aug 24 10:35:33 login02 /usr/lib64/x2go/x2gogetports[131 db_getports called, server: login02; return value: <etc etc>
So this is a CentOS7 system using SSSD for AD authentication, but using SSH keys
Any ideas would be appreciated!
Thanks,
Chris
Am 25.08.2016 um 11:01 schrieb Chris Collins: ...
So this is a CentOS7 system using SSSD for AD authentication, but using SSH keys
Any ideas would be appreciated!
First idea: Set up an identical test system that uses plain user/password or ssh pubkey auth only, see if it occurs there, too.
Second idea: Try to run a desktop environment instead of a single app.
I have a demo server here that runs CentOS7, plain user/pass or SSH pubkey auth, and am running MATE as DE on it, no issues.
-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
On 25 August 2016 at 10:07, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 25.08.2016 um 11:01 schrieb Chris Collins: ...
So this is a CentOS7 system using SSSD for AD authentication, but using SSH keys
Any ideas would be appreciated!
First idea: Set up an identical test system that uses plain user/password or ssh pubkey auth only, see if it occurs there, too.
Second idea: Try to run a desktop environment instead of a single app.
I have a demo server here that runs CentOS7, plain user/pass or SSH pubkey auth, and am running MATE as DE on it, no issues.
Hi Stefan,
Thanks for responding:
A few tests based on your suggestions:
I should point out that SSH works fine. It does look then like it is related to SSSD / AD, and as I say it seems like the known fixed bug http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=688
Looking at the following part of the logs
/usr/lib64/x2go/x2gogetdisplays[ db_getdisplays called, server: login02; return value:
I don't know what this should be returning exactly, but if I run x2gogetdisplays login02 when x2go is 'running' (client hung) I got nothing returned. Without any x2go processes, I get
[root@login02 ~]# /usr/lib64/x2go/x2gogetdisplays login02 |50|
On a test VM I get the following response whether there are any x2go processes or not:
[root@wikitest ~]# /usr/lib64/x2go/x2gogetdisplays wikitest |50| |51|
Thanks,
Chris
Final update, in case anyone else ever bumps into this:
After digging deeper around what turned out to be a bit of a red herring (SSSD), I stumbled across a rather simple issue relating to using numeric only usernames, with a solution detailed at http://lists.x2go.org/pipermail/x2go-user/2015-April/003159.html
That one quick change to support numeric usernames in x2gosqlitewrapper.pl later and everything started working.
Thanks,
Chris
On 25 August 2016 at 15:41, Chris Collins <ccatcmp@googlemail.com> wrote:
On 25 August 2016 at 10:07, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 25.08.2016 um 11:01 schrieb Chris Collins: ...
So this is a CentOS7 system using SSSD for AD authentication, but using SSH keys
Any ideas would be appreciated!
First idea: Set up an identical test system that uses plain user/password or ssh pubkey auth only, see if it occurs there, too.
Second idea: Try to run a desktop environment instead of a single app.
I have a demo server here that runs CentOS7, plain user/pass or SSH pubkey auth, and am running MATE as DE on it, no issues.
Hi Stefan,
Thanks for responding:
A few tests based on your suggestions:
- enabling password logins I get the same behaviour (client hang, lots of looping logs).
- Trying a desktop (this box is streamlined so I'm limited, but I installed Openbox), again exactly the same behaviour
- I can't easily add local accounts, but was able to permit root logins via SSH for a moment to test and suddenly x2go works for root.
I should point out that SSH works fine. It does look then like it is related to SSSD / AD, and as I say it seems like the known fixed bug http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=688
Looking at the following part of the logs
/usr/lib64/x2go/x2gogetdisplays[ db_getdisplays called, server: login02; return value:
I don't know what this should be returning exactly, but if I run x2gogetdisplays login02 when x2go is 'running' (client hung) I got nothing returned. Without any x2go processes, I get
[root@login02 ~]# /usr/lib64/x2go/x2gogetdisplays login02 |50|
On a test VM I get the following response whether there are any x2go processes or not:
[root@wikitest ~]# /usr/lib64/x2go/x2gogetdisplays wikitest |50| |51|
Thanks,
Chris