Description of problem: When using x2go client from windows to connect to Mga 8 64 (virtual machine) the client logs in with ssh correctly using a password authenticated ssh private key. But the client immediately throws an error message: "Error: The remote NX proxy closed the connection. Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie." The client session log: "Loop: PANIC! The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie." The log file (messages)show the following last events before session closes: Dec 19 20:24:22 mga8virtual /usr/sbin/x2gocleansessions[175856]: per-50-1608405837_stDMATE_dp32: state file for this session does not exist: /tmp/.x2go-per/C-per-50-1608405837_stDMATE_dp32/state (this can be ignored during session startups) Dec 19 20:24:24 mga8virtual /usr/sbin/x2gocleansessions[175856]: per-50-1608405837_stDMATE_dp32: state file for this session does not exist: /tmp/.x2go-per/C-per-50-1608405837_stDMATE_dp32/state (this can be ignored during session startups) Dec 19 20:24:26 mga8virtual /usr/sbin/x2gocleansessions[175856]: per-50-1608405837_stDMATE_dp32: state file for this session does not exist: /tmp/.x2go-per/C-per-50-1608405837_stDMATE_dp32/state (this can be ignored during session startups) Dec 19 20:24:29 mga8virtual /usr/bin/x2goumount-session[177444]: x2goumount-session has been called with options: per-50-1608405837_stDMATE_dp32 Dec 19 20:24:52 mga8virtual /usr/sbin/x2gocleansessions[175856]: per-50-1608405837_stDMATE_dp32: found stale X-server process (177101), sending SIGKILL Dec 19 20:24:52 mga8virtual /usr/bin/x2goumount-session[177654]: x2goumount-session has been called with options: per-50-1608405837_stDMATE_dp32 Version-Release number of selected component (if applicable): 4.0.1.20-4.mga8 How reproducible: Steps to Reproduce: 1. 2. 3.
Thank you for this report. Not easy for us to reproduce, so assigning immediately globally because this SRPM has no fixed maintainer.
Source RPM: x2goserver ver. 4.0.1.20-4.mga8 => x2goserver-4.0.1.20-4.mga8.src.rpmAssignee: bugsquad => pkg-bugs
The version of x2go in Mga 7 and Mga 8 is the same. In Mga 7 x2goagent gets installed with x2go. However, in the repository for Mga 8 x2goagent version 3.5.0.33 is missing. I think this might be the explanation for the problems.
Tried to install x2goagent-3.5.0.33-3.mga7.x86_64.rpm with urpmi. The output was: "Installation failed: x2goagent < 3.5.99.0-1 is obsoleted by (installed) nxagent-3.5.99.25-1.mga8.x86_64"
I have the same problem In the session.log on the server, we have /usr/bin/x2gostartagent: ligne 443: x2goagent : commande introuvable x2goagent was created by the nxagent src.rpm, but is is not the case in mga8 version. If i try to use nxagent as x2goagent as in mga7, it fails Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-fboyrie/C-fboyrie-50-1615218947_stDXFCE_dp24/options:50''. If i try to copy all the x2goagent from mageia7 to mageiea8. I can connect, but the session closes immediately.
CC: (none) => fboyrie
x2goagent doesn't exist any more with the current version of nx. x2goserver and/or x2goclient probably just need to be updated to match.
CC: (none) => fri
I have a similar problem after yesterday upgrade. I was able to pinpoint some strange ssh behaviour. To clean things up, I uninstalled x2goserver and x2goserver-sqlite and cleaned up the configuration as my test system is upgraded from a lot of previous versions. This is the log I obtain (I get the same at log level info and debug): Apr 9 13:21:44 ******-wks3 /usr/bin/x2gostartagent: successfully started X2Go agent session with ID ******-50-1617967298_stDLXDE_dp24 Apr 9 13:21:46 *******-wks3 sshd[260661]: error: connect_to localhost port 34396: failed. Apr 9 13:21:46 *******-wks3 sshd[260661]: error: channel 0: protocol error: close rcvd twice Apr 9 13:21:47 *******-wks3 sshd[260661]: Received disconnect from 10.232.42.173 port 41510:11: Bye Bye Apr 9 13:21:47 *******-wks3 sshd[260661]: Disconnected from user ******* 10.232.42.173 port 41510 It seems that x2gostartagent doesn't listen to the port sshd is forwarding to or crashes just before sshd has any way to talk to it. I checked and the sqllite database get created (I did not make any query as I'm not familiar but based on the strings command the session is there). Netstat and ps do not show any x2go processes running. Any idea?
CC: (none) => g.merigo
So I came to the same conclusion as David, x2goagent is missing, but why the missing package? It was there in mga7... and the x2go version is the same.
I did further research, in mga7 the x2goagent was packaged as x2goagent-3.5.0.33-3.mga7.x86_64, I force installed it and got a broken link in /usr/libexec/nx: x2goagent -> ../../../usr/libexec/nx/nxagent I tried to correct it (at least now it was not broken) to: x2goagent -> ../../../usr/libexec/nx/nxagent Now x2goagent seems to work, but the x2go session still fails with the same error. It seems strange as the x2go software is the same, maybe something changed in the nxagent package.
I finally found a “dirty” **workaround**. Since it seems everything broken comes from nxagent, I tried to install the mga7 version of both nxagent and x2go agent and I got a working setup. These are the packages I used: nxagent-3.5.0.33-3.mga7.x86_64.rpm x2goagent-3.5.0.33-3.mga7.x86_64.rpm x2goserver-4.0.1.20-4.mga8.x86_64.rpm Is something wrong on the new nxagent? Maybe it has to be packaged into x2goagent because it's now incompatible?
Thanks. I assume the packages also need be added to skip list to not get updated until fixed. In https://wiki.mageia.org/en/Mageia_8_Errata#Various_upgrade_issues I now added link to comment 9.
Keywords: (none) => IN_ERRATA8
Yes, I added /^nxagent/ to my /etc/urpmi/skip.list at least for now.
CC: (none) => doktor5000
CC: (none) => thomas.bigot
(In reply to Giuseppe Merigo from comment #9) > I finally found a “dirty” **workaround**. Since it seems everything broken > comes from nxagent, I tried to install the mga7 version of both nxagent and > x2go agent and I got a working setup. > > These are the packages I used: > > nxagent-3.5.0.33-3.mga7.x86_64.rpm > x2goagent-3.5.0.33-3.mga7.x86_64.rpm > x2goserver-4.0.1.20-4.mga8.x86_64.rpm > > > Is something wrong on the new nxagent? Maybe it has to be packaged into > x2goagent because it's now incompatible? For me, this workaround works only if I uninstall the package "lib64nxX11_6-3.5.99.25-1.mga8.x86_64" and install "lib64xcompext3-3.5.0.33-3.mga7.x86_64.rpm" and "lib64nxX11_0-3.5.0.33-3.mga7.x86_64.rpm" from Mageia 7. Otherwise, I have a segfault in libx11-xcb.
CC: (none) => grograg
It seems that x2go server is in 4.1.0 release since 2018 https://code.x2go.org/releases/source/x2goserver/ x2goclient in 4.1.2 since 2020-02 They probably need to be updated.
CC: (none) => yves.brungard_mageia
Any new information on this bug? Are there any plans to fix this?
(In reply to Per Nelvig from comment #14) > Any new information on this bug? Are there any plans to fix this? I'm still using my own workaround from comment #9, I currently don't see anything improving in the packages, but if someone wants to try on their system or on a brand new VM, nice.
There is an update in Testing: x2goserver-sqlite-4.1.0.3-1.mga8 x2goserver-postgresql-4.1.0.3-1.mga8 x2goserver-4.1.0.3-1.mga8 nxagent-3.5.99.26-1.1.mga8 lib64nxX11_6-3.5.99.26-1.1.mga8 lib64xcomp3-3.5.99.26-1.1.mga8 lib64xcompshad3-3.5.99.26-1.1.mga8 nxproxy-3.5.99.26-1.1.mga8 nxdialog-3.5.99.26-1.1.mga8 Sources: x2goserver-4.1.0.3-1.mga8.src.rpm nx-3.5.99.26-1.1.mga8.src.rpm
Assignee: pkg-bugs => qa-bugs
I updated and I now receive this error in the dialog box: ``` x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") /usr/lib64/x2go/x2gocheckport: line 131: connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") Unable to find free display port or insert new session into database; parameters: port (50), hostname (servernuc.palin.dummy) and session name (). ``` and this is getting logged into syslog (I anonymized the IP only): ``` Jan 4 09:23:38 servernuc sshd[3751829]: Accepted keyboard-interactive/pam for palin from xxx.xxx.xxx.xxx port 41746 ssh2 Jan 4 09:23:38 servernuc dbus-daemon[794]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.378' (uid=500 pid=3751847 comm="/usr/bin/hostnamectl --transient") Jan 4 09:23:38 servernuc dbus-daemon[794]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 4 09:23:39 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 1). Jan 4 09:23:40 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 2). Jan 4 09:23:40 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 3). Jan 4 09:23:40 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 4). Jan 4 09:23:40 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 5). Jan 4 09:23:41 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 6). Jan 4 09:23:41 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 7). Jan 4 09:23:41 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 8). Jan 4 09:23:41 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 9). Jan 4 09:23:42 servernuc /usr/bin/x2gostartagent: no free display number available, cannot start new session. Retrying (run 10). Jan 4 09:23:42 servernuc /usr/bin/x2gostartagent: Unable to find free display port or insert new session into database; parameters: port (50), hostname (servernuc.palin.dummy) and session name (). ```
@Guiseppe Try, as root: x2godbadmin --createdb on the server side. Then retry for a session. I have also in my notes, but I don't know if this is needed: chown root:x2gouser /usr/lib/x2go/libx2go-server-db-sqlite3-wrapper chmod 2755 /usr/lib/x2go/libx2go-server-db-sqlite3-wrapper
I always do a new createdb when upgrading, i changed the permissions and added the g+s flag to these files: /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper.pl /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper (note the lib**64**) Now the dialog error changed (it seems like a string with a single quote is passed instead of a port number): ``` Connection failed. /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") /usr/lib64/x2go/x2gocheckport: line 131: HAVEN'T: syntax error: invalid arithmetic operator (error token is "'T") Unable to find free display port or insert new session into database; parameters: port (50), hostname (servernuc.palin.dummy) and session name (). ``` The syslog message is the same, so I won't paste it again.
Just an addendum: the new error appears AFTER the (empty) section list appear, and AFTER pressing the NEW session button.
@Guiseppe: Did you install also x2goserver-sqlite-4.1.0.3-1.mga8 ?
No I didn't, urpmi didn't pull the upgrade dependency. I installed it right now, initialized the db brand new and restarted x2goservice but the error is still the same when I hit the “new session” button.
Can you look for the session.log in/tmp/.x2go-<username>/<session> on the serverside?
That's the whole point, there's no session log because the session is not created.
Have you open ssh port in the firewall configuration (server side)?
Yes of course, if I downgrade to the mga7 version everything works again.
CC: (none) => antonin.roussel
You server should have a name different from localhost, too. I have configured one, with the creation of the DB, modification of credentials on above files, opening ssh, and this is OK.
My server name is not localhost as you can see in the log I pasted ;)
The word "HAVEN'T" is the start of a error message I would like to have completely. Don't you see it in journal of the server ? As root: journalctl -b |grep x2go
(In reply to Lewis Smith from comment #1) > .../... Not easy for us to reproduce .../... To ease testing I suggest to set a single computer with both server and client. Then just set a x2go session to local host. Looks like it is possible with ICEWM, ssh port open (or not because localhost), and your x2go user member of group x2gouser ("sometimes" it seems helping, "others times" it appears useless), mind creating db.
(In reply to papoteur from comment #29) > The word "HAVEN'T" is the start of a error message I would like to have > completely. > Don't you see it in journal of the server ? > As root: > journalctl -b |grep x2go As I said I have no more logs that those on syslog, this is the result of your command: Dec 26 12:23:41 servernuc.palin.dummy systemd[15805]: tmp-.x2go\x2dpalin-spool-C\x2dpalin\x2d50\x2d1672053804_stDXFCE_dp24.mount: Succeeded. Dec 26 12:23:41 servernuc.palin.dummy systemd[474197]: tmp-.x2go\x2dpalin-spool-C\x2dpalin\x2d50\x2d1672053804_stDXFCE_dp24.mount: Succeeded. Dec 26 12:23:41 servernuc.palin.dummy systemd[1]: tmp-.x2go\x2dpalin-spool-C\x2dpalin\x2d50\x2d1672053804_stDXFCE_dp24.mount: Succeeded. Jan 04 09:15:31 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 04 09:15:31 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 19h 25min 1.296s CPU time. Jan 04 09:19:59 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 04 09:19:59 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 26.288s CPU time. Jan 04 09:22:57 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 04 09:22:57 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 14.327s CPU time. Jan 04 09:23:33 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 04 09:23:33 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 3.689s CPU time. Jan 04 09:28:38 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 04 09:28:38 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 26.740s CPU time. Jan 04 10:11:34 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 04 10:11:34 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 4min 10.493s CPU time. Jan 05 09:10:57 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 05 09:10:57 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 3h 4min 29.310s CPU time. Jan 05 12:46:36 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 05 12:46:36 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 28min 47.159s CPU time. Jan 05 12:59:17 servernuc.palin.dummy systemd[1]: x2goserver.service: Succeeded. Jan 05 12:59:17 servernuc.palin.dummy systemd[1]: x2goserver.service: Consumed 21.291s CPU time.
(In reply to Antonin Roussel from comment #30) > (In reply to Lewis Smith from comment #1) > > .../... Not easy for us to reproduce .../... > > To ease testing I suggest to set a single computer with both server and > client. Then just set a x2go session to local host. > > Looks like it is possible with ICEWM, ssh port open (or not because > localhost), and your x2go user member of group x2gouser ("sometimes" it > seems helping, "others times" it appears useless), mind creating db. I can do this, but not right now. And it would be a regression, since with the older packages everything is fine. Maybe there is some configuration which is not done properly by the rpm scripts and that I'm not aware of.
Hello, I have submitted a new build which should
Assignee: qa-bugs => yves.brungard_mageia
Hello, I have submitted a new build which should set the credentials on /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper x2goserver-postgresql-4.1.0.3-1.1.mga8 x2goserver-sqlite-4.1.0.3-1.1.mga8 x2goserver-4.1.0.3-1.1.mga8
Assignee: yves.brungard_mageia => qa-bugs
It works perfectly now, thank you very much!
Thank you Papoteur and Guiseppe! Errata 8 to be updated when this is pushed to updates. @Papoteur: Advisory?
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Advisory ================ The x2go system was broken, clients can't open sessions, because of nxagent looking for libs in /usr/local/ After updating nxagent, compiling it with fixes, and updating x2goserver, the sessions can now be opened from the client. The new package fixes also credentials on /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper ================ x2goserver-sqlite-4.1.0.3-1.1.mga8 x2goserver-postgresql-4.1.0.3-1.1.mga8 x2goserver-4.1.0.3-1.1.mga8 nxagent-3.5.99.26-1.1.mga8 lib64nxX11_6-3.5.99.26-1.1.mga8 lib64xcomp3-3.5.99.26-1.1.mga8 lib64xcompshad3-3.5.99.26-1.1.mga8 nxproxy-3.5.99.26-1.1.mga8 nxdialog-3.5.99.26-1.1.mga8 Sources: x2goserver-4.1.0.3-1.1.mga8.src.rpm nx-3.5.99.26-1.1.mga8.src.rpm
CC: (none) => davidwhodginsKeywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0001.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
Errata 8 updated.
Thank you all for finally fixing this!
Depends on: (none) => 31426
Depends on: 31426 => (none)