Re: [X2Go-User] Server/Client Timeout

[Stefan Baur]

Am 21.05.20 um 18:44 schrieb brian:
> I'm using x2go to log into a server that I have woken from a suspended
> state using a wake-on-lan command.
> 
> It appears that the server pc is not aware of the x2go connection, and
> returns to a suspended state shortly after I connect with the x2go
> client. About 10 minutes.
> 
> Are there keep-alive settings or time-out parameters, or other means
> that can be configured is x2go to prevent this from happening?

So it seems you have some kind of mechanism in place that checks for
active users/connections, and suspends the server if there are none.

Maybe a cron job that checks the output of "w" or "who"?
You will need to amend that to check the output of "x2golistsessions"
for sessions that are in state "R" (which stands for "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
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] ICE default IO error handler doing an exit(), pid = xxxxxx, errno = 32, Fedora 32

[Robert Kudyba]

Pardon the cross post from x2go dev list perhaps someone as seen this. Only
affecting 1 workstation.

On Fedora 32 with both MATE and XFCE, X2Go immediately quits with
> Connection failed. This stackexchange question
> 
>  suggests
> running x2godbadmin --createdb but that doesn't help.
>
> x2goagent-4.1.0.3-6.fc32.x86_64
> x2goserver-xsession-4.1.0.3-6.fc32.noarch
> x2goserver-common-4.1.0.3-6.fc32.noarch
> x2goserver-4.1.0.3-6.fc32.x86_64
>
> Connection failed.
>
> /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 (ourdomain) and session name ().
>
> May 26 07:35:33 ourhostname /usr/bin/x2gostartagent[95534]: no free
> display number available, cannot start new session. Retrying (run 10).
> May 26 07:35:33 ourhostname /usr/bin/x2gostartagent[95535]: Unable to find
> free display port or insert new session into database; parameters: port
> (50), hostname (ourdomain) and session name ().
>
> cat .xsession-x2go-ourdomain.edu-errors
> XSession-x2go: X session started for ouruser at Sun May 24 15:26:31 EDT
> 2020
> ** Message: 15:26:33.626: couldn't access control socket:
> /run/user/1200/keyring/control: No such file or directory
> SSH_AUTH_SOCK=/run/user/1200/keyring/ssh
> mate-session[141487]: WARNING: AT-SPI: Could not obtain desktop path or
> name
>
> mate-session[141487]: WARNING: atk-bridge: GetRegisteredEvents returned
> message with unknown signature
> mate-session[141487]: WARNING: atk-bridge: get_device_events_reply:
> unknown signature
> mate-session[141487]: WARNING: atk-bridge: get_device_events_reply:
> unknown signature
>
> ** (mate-settings-daemon:141818): WARNING **: 15:26:34.517: Could not open
> RFKILL control device, please verify your installation
>
> ** (mate-panel:141832): WARNING **: 15:26:34.586: AT-SPI: Could not obtain
> desktop path or name
>
> ** (mate-panel:141832): WARNING **: 15:26:34.608: atk-bridge:
> GetRegisteredEvents returned message with unknown signature
>
> ** (mate-panel:141832): WARNING **: 15:26:34.608: atk-bridge:
> get_device_events_reply: unknown signature
>
> ** (mate-panel:141832): WARNING **: 15:26:34.608: atk-bridge:
> get_device_events_reply: unknown signature
>
> ** (mate-settings-daemon:141818): WARNING **: 15:26:35.152: AT-SPI: Could
> not obtain desktop path or name
>
>
> ** (mate-settings-daemon:141818): WARNING **: 15:26:35.154: atk-bridge:
> GetRegisteredEvents returned message with unknown signature
>
> ** (mate-settings-daemon:141818): WARNING **: 15:26:35.154: atk-bridge:
> get_device_events_reply: unknown signature
>
> ** (mate-settings-daemon:141818): WARNING **: 15:26:35.154: atk-bridge:
> get_device_events_reply: unknown signature
> SSH_AUTH_SOCK=/run/user/1200/keyring/ssh
> vmware-user: could not open /proc/fs/vmblock/dev
> SSH_AUTH_SOCK=/run/user/1200/keyring/ssh
> SSH_AUTH_SOCK=/run/user/1200/keyring/ssh
>
> (caja:141846): Gtk-WARNING **: 15:26:36.752: Failed to register client:
> GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
> client
> Failure: Module initialization failed
>
> ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.825:
> AT-SPI: Could not obtain desktop path or name
>
>
> ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.829:
> atk-bridge: GetRegisteredEvents returned message with unknown signature
>
> ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.829:
> atk-bridge: get_device_events_reply: unknown signature
>
> ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.829:
> atk-bridge: get_device_events_reply: unknown signature
> (uint32 1,)
> *** ERROR ***
> TI:15:26:39 TH:0x55bef6378ad0   FI:gpm-manager.c
>  FN:gpm_manager_systemd_inhibit,1786
>  - Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.AccessDenied:
> Permission denied
> Traceback:
> mate-power-manager(+0x1d304) [0x55bef5347304]
> mate-power-manager(+0x1478b) [0x55bef533e78b]
> /lib64/libgobject-2.0.so.0(g_type_create_instance+0x311)
> [0x7f90fcf0b1b1]
> /lib64/libgobject-2.0.so.0(+0x193f5) [0x7f90fceed3f5]
> /lib64/libgobject-2.0.so.0(g_object_new_with_properties+0x275)
> [0x7f90fceeeb05]
> /lib64/libgobject-2.0.so.0(g_object_new+0xc1) [0x7f90fceef6b1]
> mate-power-manager(+0x15e26) [0x55bef533fe26]
> mate-power-manager(+0xb20a) [0x55bef533520a]
> /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f90fcaa01a3]
> mate-power-manager(+0xb58e) [0x55bef533558e]
> Traceback (most recent call last):
>   File "/usr/bin/seapplet", line 34, in 
> from setroubleshoot.config import get_config
> ModuleNotFoundError: No mod

Re: [X2Go-User] x2goversion problem affecting pyhoca-cli, and a solution

[Mike Gabriel]

Hi Michael, hi Mihai,

On  Do 21 Mai 2020 00:15:20 CEST, Michael Ashley wrote:


Hi folks,

While trying to get pyhoca-cli to work, I noticed that x2goversion  
on the server was printing out the version numbers without the  
leading component names. E.g.,


: 4.1.0.3
: 4.1.0.3
: 4.1.0.3
: 4.1.0.3
: 4.1.0.3
: 3.5.99.23
: 4.1.0.3

instead of:

x2goserver: 4.1.0.3
x2goserver-common: 4.1.0.3
x2goserver-extensions: 4.1.0.3
x2goserver-fmbindings: 4.1.0.3
x2goserver-printing: 4.1.0.3
x2goserver-x2goagent: 3.5.99.23
x2goserver-xsession: 4.1.0.3

The problem was that my X2GO_VERSIONS_BASEPATH had a ".." in it,  
which caused the following line in x2goversion to fail:


X2GO_COMPONENT="$(echo "${compfile}" | cut -d '.' -f '2')"

A fix is to replace the line with:

X2GO_COMPONENT=${compfile#*VERSION.}

Finally, to have a working pyhoca-cli, you need to use the version  
from 11 March 2020 or later  
https://code.x2go.org/gitweb?p=pyhoca-cli.git;a=tree


Regards,
Michael


This is a know issue and needs to be addressed by a new upstream  
release of X2Go Server. In Debian and recent Ubuntu, I have fixed this  
issue a while back.


@Mihai, reading this, could you prepare a new release of pyhoca-cli,  
to get the fix for #1445 out?


Thanks+Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpz4sEm55gxT.pgp
Description: Digitale PGP-Signatur
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user