Hello,
I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.
I’ve attached screen shots of the client session details. The last messages in the session are:
x2go client: v4.0.4.0 xquarts: v2.7.7
Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.
Please advise.
Thank you, Liz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Liz!
Am 24.09.2015 um 18:12 schrieb Real, Elizabeth (392K):
I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.
I’ve attached screen shots of the client session details. The last messages in the session are:
- Info: Your session was closed before reaching a usable state. * Info: This can be due to the local X server refusing access to the client. * Info: Please check authorization provided by the remote X application. * Session: Session terminated at
x2go client: v4.0.4.0 xquarts: v2.7.7
Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.
Please advise.
I've had a quick chat with Mihai regarding this and his guess is that it is an issue with xquartz/X.Org settings. Which would explain why reinstalling X2GoClient didn't help. So please check/compare the xquartz/X.org settings and try a reinstall of that.
Kind Regards, 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJWB9kgAAoJEG7d9BjNvlEZH/kH/0nsPR9QiW7lAdAzuOvJpwJu J5CZpMo9l2yU5StYbZmBa0ibah6vOJgESqG6Dqig1Vpk/k2HhO7R00Wq7+favNNd T+2D4rcTKaHdqbhyM6/9cdvuPmljWOcUfO2zao/39wgQHya++jjejJExMIB1pjk3 abYzd2hasC72Y2R8DJWLzjUoD7iUhitBoDn4z28IrTqTBeVAsP0IsG1YMnAXEx6D E3+O2Ho10lpQ46AglBoG5BTe75PcxOvHm8EFE3FchYH/Rske2WmA7R6/vYz1O8aI rtxesT+PNhg6rM5LIQ/pvUqfRwAOINP9vinCCWWSz/mWzHXhjABaN+ooy7GjVQU= =UkIr -----END PGP SIGNATURE-----
Stephan,
I reinstalled xquartz 2.7.7 and x2goclient 4.0.5 and verified the settings are set to those recommended.
The behavior is happening when regular users attempt to connect to an x2go server. This leads me to believe it could be a permissions issue?
When I attempt to connect as a regular linux user, I get kicked back to the login scree. However when I connect as ‘root’ there are no problems.
CLIENT LOGIN AS REGULAR USER: I noticed that if I attempt to login as a regular linux user (real), that user gets kicked back to the login screen, here’s the session output: "Protocol mismatch or no X authentication data”
SERVER: The /var/log/secure reports: Sep 28 15:11:34 **** sshd[27639]: Accepted keyboard-interactive/pam for real from 137.79.38.166 port 52380 ssh2 Sep 28 15:11:34 **** sshd[27639]: pam_unix(sshd:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session closed for user real
When I check the status of x2gocleansessions.service: Sep 28 15:11:36 ******* /usr/sbin/x2gocleansessions[769]: real-50-1443478272_stDKDE_dp32: state file for this session does not exist: /tmp/.x2go-real/C-real-50-1443478272_stDKDE_dp32/state (this can be ignored during session startups)
CLIENT LOGIN AS ROOT: As root there are no issues.
SERVER: /var/log/secure shows: Sep 28 15:21:04 node4 sshd[6137]: Accepted password for root from ********* port 52504 ssh2 Sep 28 15:21:04 node4 sshd[6137]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 28 15:21:15 node4 polkitd[1516]: Registered Authentication Agent for unix-session:46638 (system bus name :1.102126 [/usr/libexec/kde4/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale C) Sep 28 15:21:17 node4 sshd[7291]: Accepted publickey for rmdc from ********** port 50161 ssh2: RSA 81:72:dd:4f:3d:a2:18:ba:ed:77:2a:1d:2e:72:f6:4b Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session opened for user rmdc by (uid=0) Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session closed for user rmdc Sep 28 15:21:23 node4 sshd[7347]: Accepted publickey for root from ********** port 49422 ssh2: RSA 23:2c:8c:a6:fd:aa:80:ae:7e:fa:60:57:5f:e4:c2:98 Sep 28 15:21:23 node4 sshd[7347]: pam_unix(sshd:session): session opened for user root by (uid=0)
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Thursday, September 24, 2015 at 9:12 AM To: "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: x2go client session kicks user back to the session login screen
Hello,
I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.
I’ve attached screen shots of the client session details. The last messages in the session are:
x2go client: v4.0.4.0 xquarts: v2.7.7
Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.
Please advise.
Thank you, Liz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hey Liz,
first, your two server logfiles were anonymized in different locations. One showed the IP, but not the node name, the other the node name, but not the IP.
So now I'm confused - are you trying to connect to the same server, from both clients? Or are these two different servers, not only two different clients?
Second, the screenshots in your original message showed a firewall popup. It doesn't look like you allowed incoming connections for x2goclient.app yet? Judging from what Mihai (one of our resident Mac experts here on the list) told me, you have to, or X2GoClient won't work .
Third, could you run the following four tests on the terminal of both the affected and the unaffected machine and compare the output for each test between affected and unaffected?
ssh non-root-user@x2goserver
See if the connection works and if you see a banner message. Make a copy of the banner message if there is one, so you can compare it.
ssh root@x2goserver
See if the connection works and if you see a banner message. Make a copy of the banner message if there is one, so you can compare it.
ssh -X non-root-user@x2goserver
type "xterm" after you see the shell prompt, see if XTerm comes up and there are no error messages on the console
ssh -X root@x2goserver
type "xterm" after you see the shell prompt, see if XTerm comes up and there are no error messages on the console
Fourth, another hint from Mihai, in the xquartz settings, there's a "Security" tab. Could you take a screenshot of the current settings there, please, and post the screenshots for both machines?
Last, it would be interesting to know if the affected machine is in the same IP network as the unaffected one, or not. To find out, run
ifconfig -a
in each Mac's terminal and compare the results.
Kind Regards, Stefan
Am 29.09.2015 um 00:26 schrieb Real, Elizabeth (392K):
Stephan,
I reinstalled xquartz 2.7.7 and x2goclient 4.0.5 and verified the settings are set to those recommended.
The behavior is happening when regular users attempt to connect to an x2go server. This leads me to believe it could be a permissions issue?
When I attempt to connect as a regular linux user, I get kicked back to the login scree. However when I connect as ‘root’ there are no problems.
CLIENT LOGIN AS REGULAR USER: I noticed that if I attempt to login as a regular linux user (real), that user gets kicked back to the login screen, here’s the session output: "Protocol mismatch or no X authentication data”
SERVER: The /var/log/secure reports: Sep 28 15:11:34 **** sshd[27639]: Accepted keyboard-interactive/pam for real from 137.79.38.166 port 52380 ssh2 Sep 28 15:11:34 **** sshd[27639]: pam_unix(sshd:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session closed for user real
When I check the status of x2gocleansessions.service: Sep 28 15:11:36 ******* /usr/sbin/x2gocleansessions[769]: real-50-1443478272_stDKDE_dp32: state file for this session does not exist: /tmp/.x2go-real/C-real-50-1443478272_stDKDE_dp32/state (this can be ignored during session startups)
CLIENT LOGIN AS ROOT: As root there are no issues.
SERVER: /var/log/secure shows: Sep 28 15:21:04 node4 sshd[6137]: Accepted password for root from ********* port 52504 ssh2 Sep 28 15:21:04 node4 sshd[6137]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 28 15:21:15 node4 polkitd[1516]: Registered Authentication Agent for unix-session:46638 (system bus name :1.102126 [/usr/libexec/kde4/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale C) Sep 28 15:21:17 node4 sshd[7291]: Accepted publickey for rmdc from ********** port 50161 ssh2: RSA 81:72:dd:4f:3d:a2:18:ba:ed:77:2a:1d:2e:72:f6:4b Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session opened for user rmdc by (uid=0) Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session closed for user rmdc Sep 28 15:21:23 node4 sshd[7347]: Accepted publickey for root from ********** port 49422 ssh2: RSA 23:2c:8c:a6:fd:aa:80:ae:7e:fa:60:57:5f:e4:c2:98 Sep 28 15:21:23 node4 sshd[7347]: pam_unix(sshd:session): session opened for user root by (uid=0)
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov <mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Thursday, September 24, 2015 at 9:12 AM To: "x2go-dev@lists.x2go.org <mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org <mailto:x2go-dev@lists.x2go.org>> Subject: x2go client session kicks user back to the session login screen
Hello,
I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.
I’ve attached screen shots of the client session details. The last messages in the session are:
- Info: Your session was closed before reaching a usable state. * Info: This can be due to the local X server refusing access to the client. * Info: Please check authorization provided by the remote X application. * Session: Session terminated at
x2go client: v4.0.4.0 xquarts: v2.7.7
Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.
Please advise.
Thank you, Liz
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJWCc50AAoJEG7d9BjNvlEZduAH/1kEjKJLmnm5gh4WYJOnV5yq R4JGgOh/BnYtaq/C7QcinjKeGZqrz/0FDxGbDyDf1YF0kQPoqvULIUcayrS7ur8X h2qvqZpf8r1JZVivgLXVXyWIxWzerKA/sOf55kp0TLQXTIRlkyKJPGqt4WBEfZVo 6X3aaK+9qRTvkLuYrWMxdwiNYzP8U8ws6jN9xsyGYqXEMMb1Ms+NuaqUDRmfw88v M6Jf0f6BLTQtC/STGRZfjDcqg2hDDMcd8BSDLSi1ese7MZMSYboMFWZt7gLbo6qS IQ8M1oaRPlmBqziFuN3iwE9fR3rvijiT7Nw2A6I0LohjyYkg9DWB2/QA3Qv/yrs= =3xDp -----END PGP SIGNATURE-----
Stefan,
Q1: So now I'm confused - are you trying to connect to the same server, from both clients? Or are these two different servers, not only two different clients? My response: I am trying to connect from one x2go client (Mac 10.10.4) to one x2go server (RHEL7). When I login from the x2go client using a non-root account to the x2goserver the session kicks me back to the login screen. When I login from the x2go client using a root account to the x2goserver I am able to connect without any problems.
Q2: It doesn't look like you allowed incoming connections for x2goclient.app yet? Judging from what Mihai (one of our resident Mac experts here on the list) told me, you have to, or X2GoClient won't work My response: the x2go server is RHEL7, how do you allow incoming connections for x2goclient.app? The x2goserver is installed and the x2gocleansessions.service is running. Here are the rpms installed and the preceding firewall commands tried.
[root@ ~]# rpm -qa | grep x2go x2goserver-4.0.1.19-3.el7.x86_64 x2goserver-xsession-4.0.1.19-3.el7.x86_64 x2goagent-3.5.0.31-1.el7.x86_64 x2goclient-4.0.3.1-1.el7.x86_64 [root@ ~]# firewall-cmd --permanent --add-service=x2go Error: INVALID_SERVICE: x2go [root@ ~]# firewall-cmd --permanent --add-service=x2gocleansessions.service Error: INVALID_SERVICE: x2gocleansessions.service [root@ ~]# firewall-cmd --permanent --add-service=x2goclient.app Error: INVALID_SERVICE: x2goclient.app [root@ ~]# firewall-cmd --permanent --add-service=x2goclient Error: INVALID_SERVICE: x2goclient [root@ ~]# systemctl status x2gocleansessions.service x2gocleansessions.service - X2go session cleanup Loaded: loaded (/usr/lib/systemd/system/x2gocleansessions.service; enabled) Active: active (running) since Tue 2015-09-15 09:04:18 PDT; 4 weeks 0 days ago Main PID: 717 (x2gocleansessio) CGroup: /system.slice/x2gocleansessions.service └─717 /usr/bin/perl /usr/sbin/x2gocleansessions
Q3: run the following 4 tests on the terminal, compare banner messages My response: ran the ssh commands suggested but there are no banner differences. I’m able to connect to the x2goserver without issues. Xterm comes up without issues, no error messages.
Q4: xquartz security tab screen shot My response: both authenticate connections and allow connections from network clients are checked (see attachment)
Q5: are machines on same network My response: yes they are
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Monday, September 28, 2015 at 3:26 PM To: "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: Re: x2go client session kicks user back to the session login screen
Stephan,
I reinstalled xquartz 2.7.7 and x2goclient 4.0.5 and verified the settings are set to those recommended.
The behavior is happening when regular users attempt to connect to an x2go server. This leads me to believe it could be a permissions issue?
When I attempt to connect as a regular linux user, I get kicked back to the login scree. However when I connect as ‘root’ there are no problems.
CLIENT LOGIN AS REGULAR USER: I noticed that if I attempt to login as a regular linux user (real), that user gets kicked back to the login screen, here’s the session output: "Protocol mismatch or no X authentication data”
SERVER: The /var/log/secure reports: Sep 28 15:11:34 **** sshd[27639]: Accepted keyboard-interactive/pam for real from ********** port 52380 ssh2 Sep 28 15:11:34 **** sshd[27639]: pam_unix(sshd:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session closed for user real
When I check the status of x2gocleansessions.service: Sep 28 15:11:36 ******* /usr/sbin/x2gocleansessions[769]: real-50-1443478272_stDKDE_dp32: state file for this session does not exist: /tmp/.x2go-real/C-real-50-1443478272_stDKDE_dp32/state (this can be ignored during session startups)
CLIENT LOGIN AS ROOT: As root there are no issues.
SERVER: /var/log/secure shows: Sep 28 15:21:04 node4 sshd[6137]: Accepted password for root from ********* port 52504 ssh2 Sep 28 15:21:04 node4 sshd[6137]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 28 15:21:15 node4 polkitd[1516]: Registered Authentication Agent for unix-session:46638 (system bus name :1.102126 [/usr/libexec/kde4/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale C) Sep 28 15:21:17 node4 sshd[7291]: Accepted publickey for rmdc from ********** port 50161 ssh2: RSA 81:72:dd:4f:3d:a2:18:ba:ed:77:2a:1d:2e:72:f6:4b Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session opened for user rmdc by (uid=0) Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session closed for user rmdc Sep 28 15:21:23 node4 sshd[7347]: Accepted publickey for root from ********** port 49422 ssh2: RSA 23:2c:8c:a6:fd:aa:80:ae:7e:fa:60:57:5f:e4:c2:98 Sep 28 15:21:23 node4 sshd[7347]: pam_unix(sshd:session): session opened for user root by (uid=0)
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Thursday, September 24, 2015 at 9:12 AM To: "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: x2go client session kicks user back to the session login screen
Hello,
I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.
I’ve attached screen shots of the client session details. The last messages in the session are:
x2go client: v4.0.4.0 xquarts: v2.7.7
Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.
Please advise.
Thank you, Liz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 13.10.2015 um 21:34 schrieb Real, Elizabeth (392K):
This is short, as Mihai will have to take over from here on, but here's a misunderstanding, it seems:
Q2: It doesn't look like you allowed incoming connections for x2goclient.app yet? Judging from what Mihai (one of our resident Mac experts here on the list) told me, you have to, or X2GoClient won't work
My response: the x2go server is RHEL7, how do you allow incoming connections for x2goclient.app? The x2goserver is installed and the x2gocleansessions.service is running. Here are the rpms installed and the preceding firewall commands tried.
You have to allow incoming connections *to* x2goclient.app _on the Mac_. The three screenshots you sent along with your initial message show the Deny/Allow popup from the Mac's built-in firewall, you need to select "Allow" there.
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJWHW7BAAoJEG7d9BjNvlEZjfYH/20wIw04/sKBybZ+XvFYoZwc rJbsyklnIF8mpvYdt97U+s6Jssy1c02n7HOHBvbUaqEyqs2+4VxA3NXJa4tCAf2w n+U2ySr4vI4zZ98IccvWvpWazVJH4UZSFLvVSjV0Qrw4LV5VVoXSceqVnhlUhr66 b41ygwffWuoM11b47dW6hYjzy6QYktaw/R61uv1DmLva7UvqF//MtyQ3hOGnRfl3 18bjjDldbh5Cx+O8rxmVa4e8x0aFZAsH9Kj/j3rRxC3sahpQFNxqyIET7hv6IFOY Fu5uFv+5Vjtt1fWHJbhSxOxXuQik0Y5EPqdPu5oWIgpXt7HHx7kig9KtMtnbPGk= =csus -----END PGP SIGNATURE-----
Hello,
I sent the below message on 10/13. If there was a reply I missed it and will greatly appreciate it if you can resend it.
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Tuesday, October 13, 2015 at 12:34 PM To: "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: Re: x2go client session kicks user back to the session login screen
Stefan,
Q1: So now I'm confused - are you trying to connect to the same server, from both clients? Or are these two different servers, not only two different clients? My response: I am trying to connect from one x2go client (Mac 10.10.4) to one x2go server (RHEL7). When I login from the x2go client using a non-root account to the x2goserver the session kicks me back to the login screen. When I login from the x2go client using a root account to the x2goserver I am able to connect without any problems.
Q2: It doesn't look like you allowed incoming connections for x2goclient.app yet? Judging from what Mihai (one of our resident Mac experts here on the list) told me, you have to, or X2GoClient won't work My response: the x2go server is RHEL7, how do you allow incoming connections for x2goclient.app? The x2goserver is installed and the x2gocleansessions.service is running. Here are the rpms installed and the preceding firewall commands tried.
[root@ ~]# rpm -qa | grep x2go x2goserver-4.0.1.19-3.el7.x86_64 x2goserver-xsession-4.0.1.19-3.el7.x86_64 x2goagent-3.5.0.31-1.el7.x86_64 x2goclient-4.0.3.1-1.el7.x86_64 [root@ ~]# firewall-cmd --permanent --add-service=x2go Error: INVALID_SERVICE: x2go [root@ ~]# firewall-cmd --permanent --add-service=x2gocleansessions.service Error: INVALID_SERVICE: x2gocleansessions.service [root@ ~]# firewall-cmd --permanent --add-service=x2goclient.app Error: INVALID_SERVICE: x2goclient.app [root@ ~]# firewall-cmd --permanent --add-service=x2goclient Error: INVALID_SERVICE: x2goclient [root@ ~]# systemctl status x2gocleansessions.service x2gocleansessions.service - X2go session cleanup Loaded: loaded (/usr/lib/systemd/system/x2gocleansessions.service; enabled) Active: active (running) since Tue 2015-09-15 09:04:18 PDT; 4 weeks 0 days ago Main PID: 717 (x2gocleansessio) CGroup: /system.slice/x2gocleansessions.service └─717 /usr/bin/perl /usr/sbin/x2gocleansessions
Q3: run the following 4 tests on the terminal, compare banner messages My response: ran the ssh commands suggested but there are no banner differences. I’m able to connect to the x2goserver without issues. Xterm comes up without issues, no error messages.
Q4: xquartz security tab screen shot My response: both authenticate connections and allow connections from network clients are checked (see attachment)
Q5: are machines on same network My response: yes they are
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Monday, September 28, 2015 at 3:26 PM To: "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: Re: x2go client session kicks user back to the session login screen
Stephan,
I reinstalled xquartz 2.7.7 and x2goclient 4.0.5 and verified the settings are set to those recommended.
The behavior is happening when regular users attempt to connect to an x2go server. This leads me to believe it could be a permissions issue?
When I attempt to connect as a regular linux user, I get kicked back to the login scree. However when I connect as ‘root’ there are no problems.
CLIENT LOGIN AS REGULAR USER: I noticed that if I attempt to login as a regular linux user (real), that user gets kicked back to the login screen, here’s the session output: "Protocol mismatch or no X authentication data”
SERVER: The /var/log/secure reports: Sep 28 15:11:34 **** sshd[27639]: Accepted keyboard-interactive/pam for real from ********** port 52380 ssh2 Sep 28 15:11:34 **** sshd[27639]: pam_unix(sshd:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session opened for user real by (uid=0) Sep 28 15:11:38 **** su: pam_unix(su:session): session closed for user real
When I check the status of x2gocleansessions.service: Sep 28 15:11:36 ******* /usr/sbin/x2gocleansessions[769]: real-50-1443478272_stDKDE_dp32: state file for this session does not exist: /tmp/.x2go-real/C-real-50-1443478272_stDKDE_dp32/state (this can be ignored during session startups)
CLIENT LOGIN AS ROOT: As root there are no issues.
SERVER: /var/log/secure shows: Sep 28 15:21:04 node4 sshd[6137]: Accepted password for root from ********* port 52504 ssh2 Sep 28 15:21:04 node4 sshd[6137]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 28 15:21:15 node4 polkitd[1516]: Registered Authentication Agent for unix-session:46638 (system bus name :1.102126 [/usr/libexec/kde4/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale C) Sep 28 15:21:17 node4 sshd[7291]: Accepted publickey for rmdc from ********** port 50161 ssh2: RSA 81:72:dd:4f:3d:a2:18:ba:ed:77:2a:1d:2e:72:f6:4b Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session opened for user rmdc by (uid=0) Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session closed for user rmdc Sep 28 15:21:23 node4 sshd[7347]: Accepted publickey for root from ********** port 49422 ssh2: RSA 23:2c:8c:a6:fd:aa:80:ae:7e:fa:60:57:5f:e4:c2:98 Sep 28 15:21:23 node4 sshd[7347]: pam_unix(sshd:session): session opened for user root by (uid=0)
Thank you, Liz
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov<mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Thursday, September 24, 2015 at 9:12 AM To: "x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org<mailto:x2go-dev@lists.x2go.org>> Subject: x2go client session kicks user back to the session login screen
Hello,
I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.
I’ve attached screen shots of the client session details. The last messages in the session are:
x2go client: v4.0.4.0 xquarts: v2.7.7
Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.
Please advise.
Thank you, Liz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 20.10.2015 um 18:19 schrieb Real, Elizabeth (392K):
Hello,
I sent the below message on 10/13. If there was a reply I missed it and will greatly appreciate it if you can resend it.
[...]
From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov <mailto:Elizabeth.Real@jpl.nasa.gov>> Date: Tuesday, October 13, 2015 at 12:34 PM To: "x2go-dev@lists.x2go.org <mailto:x2go-dev@lists.x2go.org>" <x2go-dev@lists.x2go.org <mailto:x2go-dev@lists.x2go.org>> Subject: Re: x2go client session kicks user back to the session login screen [snip]
Indeed there was a reply, see here: http://lists.x2go.org/pipermail/x2go-dev/2015-October/010711.html
Note that you can always look up the thread month by month on our list archive, whenever you fear you missed a reply.
http://lists.x2go.org/pipermail/x2go-dev/2015-October/thread.html Just make sure to adapt the year and month in that link and look for the subject line of your original message.
Kind Regards, 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJWJoQPAAoJEG7d9BjNvlEZ/64H/iCdn4cn87LHHmKD/YfS6lRL kGTznDxD6OYo0znCSMfZs065mWprLfaKvgmYzy2TbW7q77om0S7mJ3YhjWnYkYlB IVZlPWlJHZz+DLNNN5HNaEYQPw6caVYKSiDDL4RT4bQbZM2OfUSRELClEnlMX5mZ JCTJDrzNgDEKZD+dO/ZfeKbBrP19pvObUmDJulQpepe3M29d2glFZZy/T6X68k7w Sn3irBEC5MxMNy+oQl3wV+CeK1J0s1GQZVz7+0bgd9nfYnQoa+4IBpMufTtIVVoS Yakd4rZSVCMl40BAbhpmmbe1Tt6CCtvNZ+KhD4zFA5fclu6n/8kL7SXOcKQ4sKM= =Y1UV -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Liz,
another idea:
Are your regular users part of some central user administration system, like LDAP, a Microsoft Windows Domain or an Active Directory (either natively or emulated via SAMBA)?
In other words, are your systems set up in a way that a particular user account will automatically have permission to log in on several machines and that changing the password on one machine updates it on all the others?
So if your users are centrally administered as described above, the behavior you are seeing would point to an issue with the authentication system in use at your site.
While X2Go uses SSH, it uses a different implementation of SSH than the regular SSH client, so a central authentication system expecting only a regular SSH connection might get confused.
Please also do follow "rpr"s advice in the previous message and check if your users have files named ".Xauthority*" in their home directories that aren't owned by them.
Note that the leading dot in the file name means they are hidden files, so the best way to check for them is: ls -lah ~/.Xauthority* from an SSH session of the user account in question.
Kind Regards, 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJWJ55zAAoJEG7d9BjNvlEZE9kH/jvEHj6fhEYQTgKFdbpMxCli gFk7WgN2MWoeA9P0b5whkXZfFSnmpO3sVyXf+TKOnuT2pvhU/2px5oJdvxmy10PC 14+NYJI363HeZwGxsEFTzNY5JPHRTVzW1p8O0+4UpiplevjiXondAqiPe1d1PW08 PsC58D98dlLxBRX6ShUJY+fOlCkbMipMy8FYppm5jFM6CzPO6XTmAkNRR/FyTz5S 0/OguVTc8R2jyFK3oTlj2p+nR5h6x3x03gSMv5OkW3YHSA1W6Wb3uEqdrYmKC7MO NQqZT3ds4w0Rg2J49N+e+GL/uvEhM/Be+beui9do4tcgYVIVCBssn4N4+NxRNCk= =KeyA -----END PGP SIGNATURE-----