Hello, I installed ThinLinc server 4.15.0 on openSUSE Leap 15.5. When I tried to connect, the ThinLinc client (4.15.0) reported something like “No agent server was available”. I deleted the version 4.15.0 and installed 4.14.0 instead. The client could connect in this case, and the session worked as expected. I observed the same behaviour on two computers with openSUSE Leap 15.5. Any idea what was wrong?
Hello @alema!
Welcome to the forum!
Without any logs, it’s difficult to give an exact answer. It would be beneficial to see /var/log/tlsetup.log from the ThinLinc 4.15.0 installation.
We set up a leap 15.5 ourselves and tried to install ThinLinc 4.15.0, and while the installation works fine, tl-setup will fail to resolve dependencies:
System Check
============
Analyzing system... done.
Library and Binary Requirements
===============================
ThinLinc requires certain libraries and binaries to work as expected.
This system lacks one or more of them and you need to manually install
the packages which provides:
libX11.so.6, libc.so.6, libcrypt.so.1, libdl.so.2, libgcc_s.so.1,
libm.so.6, libnspr4.so, libnss3.so, libpam.so.0, libpthread.so.0,
librt.so.1, libssl3.so, libutil.so.1, libz.so.1, libgssapi_krb5.so.2,
gs, ss, pgrep, /usr/sbin/sendmail, xauth, xhost
From /var/log/tlsetup.log we can see that it fails to install the xhost package:
2023-12-07 11:05:51,655: '/usr/sbin/sendmail' found
2023-12-07 11:05:51,655: 'xauth' found
2023-12-07 11:05:51,655: 'xhost' not found
I am not sure if this is what happened in your case? We’d appreciate it if you want to give another go, and install xhost manually before attempting to install ThinLinc 4.15.0:
sudo zypper install xhost
In our lab, this server was pre-installed with the KDE Desktop Environment, so many of dependencies
were already met when installing ThinLinc 4.15.0, only xhost was required to install manually.
Kind regards,
Martin
Hello,
I tried to make sure that all required software had been installed. I ran tl-setup several times. Output from the last run is listed below.
Regards,
Alexandr
thinlinc-install.log:
2023-12-05 20:30:14,641: *** ThinLinc installer started ***
2023-12-05 20:30:14,641: Architecture: x86_64
2023-12-05 20:30:14,641: Distribution: None
2023-12-05 20:30:14,641: Package format: rpm
2023-12-05 20:30:24,770: Analyzing upgrade path...
2023-12-05 20:30:24,770: Checking 'thinlinc-server-4.15.0-3358.x86_64.rpm'...
2023-12-05 20:30:24,802: Failed to get information about package 'thinlinc-server':
2023-12-05 20:30:24,802: package thinlinc-server is not installed
2023-12-05 20:30:24,808: Failed to get information about package 'thinlinc-tlmisc-libs32':
2023-12-05 20:30:24,808: package thinlinc-tlmisc-libs32 is not installed
2023-12-05 20:30:24,814: Failed to get information about package 'thinlinc-tlmisc':
2023-12-05 20:30:24,814: package thinlinc-tlmisc is not installed
2023-12-05 20:30:24,820: Failed to get information about package 'thinlinc-tladm':
2023-12-05 20:30:24,820: package thinlinc-tladm is not installed
2023-12-05 20:30:24,825: Failed to get information about package 'thinlinc-tlprinter':
2023-12-05 20:30:24,825: package thinlinc-tlprinter is not installed
2023-12-05 20:30:24,831: Failed to get information about package 'thinlinc-tlmisc-libs':
2023-12-05 20:30:24,831: package thinlinc-tlmisc-libs is not installed
2023-12-05 20:30:24,837: Failed to get information about package 'thinlinc-webaccess':
2023-12-05 20:30:24,837: package thinlinc-webaccess is not installed
2023-12-05 20:30:24,842: Failed to get information about package 'thinlinc-vsm':
2023-12-05 20:30:24,843: package thinlinc-vsm is not installed
2023-12-05 20:30:24,848: Failed to get information about package 'thinlinc-rdesktop':
2023-12-05 20:30:24,848: package thinlinc-rdesktop is not installed
2023-12-05 20:30:24,854: Failed to get information about package 'thinlinc-vnc-server':
2023-12-05 20:30:24,854: package thinlinc-vnc-server is not installed
2023-12-05 20:30:24,854: Version to install: 4.15.0-3358.x86_64
2023-12-05 20:30:24,854: Current version(s):
2023-12-05 20:30:24,854: Packages to install: thinlinc-server-4.15.0-3358.x86_64.rpm
2023-12-05 20:30:31,752: Installing package(s): thinlinc-server-4.15.0-3358.x86_64.rpm
2023-12-05 20:30:44,623: Installation complete.
2023-12-05 20:30:44,623: Starting tl-setup...
tlsetup.log:
2023-12-05 21:24:24,909: *** tl-setup started ***
2023-12-05 21:24:24,909: Architecture: x86_64
2023-12-05 21:24:24,909: Distribution: None
2023-12-05 21:24:24,909: Distribution version: 15.5
2023-12-05 21:24:24,909: Distribution family: None
2023-12-05 21:24:24,909: Package format: rpm
2023-12-05 21:24:24,909: Creating /usr/bin/thinlinc-login
2023-12-05 21:25:02,413: Server type: Master
2023-12-05 21:25:02,426: Running system checks...
2023-12-05 21:25:02,426: Checking for required libraries...
2023-12-05 21:25:02,427: 'libX11.so.6' found
2023-12-05 21:25:02,428: 'libc.so.6' found
2023-12-05 21:25:02,429: 'libcrypt.so.1' found
2023-12-05 21:25:02,430: 'libdl.so.2' found
2023-12-05 21:25:02,432: 'libgcc_s.so.1' found
2023-12-05 21:25:02,433: 'libm.so.6' found
2023-12-05 21:25:02,434: 'libnspr4.so' found
2023-12-05 21:25:02,436: 'libnss3.so' found
2023-12-05 21:25:02,437: 'libpam.so.0' found
2023-12-05 21:25:02,438: 'libpthread.so.0' found
2023-12-05 21:25:02,440: 'librt.so.1' found
2023-12-05 21:25:02,441: 'libssl3.so' found
2023-12-05 21:25:02,443: 'libutil.so.1' found
2023-12-05 21:25:02,444: 'libz.so.1' found
2023-12-05 21:25:02,447: 'libgssapi_krb5.so.2' found
2023-12-05 21:25:02,447: Checking for required binaries...
2023-12-05 21:25:02,448: 'gs' found
2023-12-05 21:25:02,448: 'ss' found
2023-12-05 21:25:02,448: 'pgrep' found
2023-12-05 21:25:02,448: '/usr/sbin/sendmail' found
2023-12-05 21:25:02,448: 'xauth' found
2023-12-05 21:25:02,448: 'xhost' found
2023-12-05 21:25:02,448: NFS support found
2023-12-05 21:25:02,448: sshd running
2023-12-05 21:25:02,503: PyGObject, GTK+ and Cairo integration found
2023-12-05 21:25:02,558: Python module ldap found
2023-12-05 21:25:02,558: Testing ps2pdf...
2023-12-05 21:25:02,675: ps2pdf seems to work
2023-12-05 21:25:02,675: Checking if CUPS is running...
2023-12-05 21:25:02,676: Something is responding on port 631. Assuming it is CUPS
2023-12-05 21:25:02,676: CUPS is responding on /var/run/cups/cups.sock
2023-12-05 21:25:02,676: Looking for CUPS directories...
2023-12-05 21:25:02,676: Found CUPS prefix: /usr
2023-12-05 21:25:02,679: Found CUPS server directory: /usr/lib/cups
2023-12-05 21:25:02,906: Detected firewall backend FirewallBackendFirewalld
2023-12-05 21:25:02,906: Supported Firewall found
2023-12-05 21:25:02,908: SELinux disabled or not present
2023-12-05 21:25:02,910: AppArmor enabled
2023-12-05 21:25:02,910: Checking if ThinLinc commands are allowed with sudo...
2023-12-05 21:25:02,917: System checks done.
2023-12-05 21:25:10,371: Setting /vsmserver/admin_email to 'alexandr.malusek@liu.se'
2023-12-05 21:25:34,108: Creating firewall service 'tlwebaccess' using ports 300:TCP
2023-12-05 21:25:34,430: Enable firewall service 'tlwebaccess'
2023-12-05 21:25:34,890: Creating firewall service 'tlwebadm' using ports 1010:TCP
2023-12-05 21:25:35,222: Enable firewall service 'tlwebadm'
2023-12-05 21:25:35,679: Creating firewall service 'tlmaster' using ports 9000:TCP
2023-12-05 21:25:36,002: Enable firewall service 'tlmaster'
2023-12-05 21:25:36,467: Creating firewall service 'tlagent' using ports 904:TCP
2023-12-05 21:25:36,790: Enable firewall service 'tlagent'
2023-12-05 21:25:37,249: Enable system firewall service 'ssh'
2023-12-05 21:25:45,959: Configuring AppArmor...
2023-12-05 21:25:46,771: AppArmor configuration completed successfully
2023-12-05 21:25:50,326: Configuring PAM...
2023-12-05 21:25:50,327: PAM is already configured for ThinLinc
2023-12-05 21:25:50,327: Setting /vsm/setup_completed...
2023-12-05 21:25:50,340: Installing services...
2023-12-05 21:25:50,340: Installing service 'vsmserver'...
2023-12-05 21:25:50,708: Installing service 'vsmagent'...
2023-12-05 21:25:51,153: Installing service 'tlwebadm'...
2023-12-05 21:25:51,579: Installing service 'tlwebaccess'...
2023-12-05 21:25:51,998: Starting services...
2023-12-05 21:25:51,998: Starting service 'vsmagent'...
2023-12-05 21:25:52,128: Starting service 'tlwebadm'...
2023-12-05 21:25:52,304: Starting service 'vsmserver'...
2023-12-05 21:25:52,443: Starting service 'tlwebaccess'...
2023-12-05 21:25:52,604: Services done.
2023-12-05 21:26:15,022: tl-setup is finished
Thank you!
Those looks fine. So let’s move on to check what’s reported in /var/log/vsmserver.log and /var/log/vsmagent.log when you try to logon with ThinLinc client.
Regards,
Martin
Hello,
The logs are below.
Regards,
Alexandr
vsmserver.log:
2023-12-05 21:25:52 INFO vsmserver: VSM Server version 4.15.0 build 3358 started
2023-12-05 21:25:52 INFO vsmserver.license: Updating license data from disk to memory
2023-12-05 21:25:52 INFO vsmserver.license: License summary: 10 concurrent users. Hard limit of 10 concurrent users.
2023-12-05 21:25:52 INFO vsmserver.session: Loaded 0 sessions for 0 users from file
2023-12-05 21:26:27 INFO vsmserver.session: User with uid 1000 (alema80) requested a new session
2023-12-05 21:26:32 WARNING vsmserver: VSM Agent 127.0.0.1 reported failure creating session for alema80
2023-12-05 21:26:32 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-12-05 21:26:32 WARNING vsmserver: No working agents found trying to start new session for alema80
2023-12-05 21:27:07 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 5 penalty points, decreasing to 4 after successful periodic load update
2023-12-05 21:27:47 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 4 penalty points, decreasing to 3 after successful periodic load update
2023-12-05 21:28:27 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 3 penalty points, decreasing to 2 after successful periodic load update
2023-12-05 21:29:07 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 2 penalty points, decreasing to 1 after successful periodic load update
2023-12-05 21:29:47 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 1 penalty points, decreasing to 0 after successful periodic load update
2023-12-05 21:37:03 INFO vsmserver.session: User with uid 1000 (alema80) requested a new session
2023-12-05 21:37:10 WARNING vsmserver: VSM Agent 127.0.0.1 reported failure creating session for alema80
2023-12-05 21:37:10 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-12-05 21:37:10 WARNING vsmserver: No working agents found trying to start new session for alema80
2023-12-05 21:37:43 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 5 penalty points, decreasing to 4 after successful periodic load update
2023-12-05 21:37:58 INFO vsmserver: Got SIGTERM, signaling process to quit
2023-12-05 21:37:58 INFO vsmserver: Terminating. Have a nice day!
vsmagent.log:
2023-12-05 21:25:52 INFO vsmagent: VSM Agent version 4.15.0 build 3358 started
2023-12-05 21:25:52 INFO vsmagent: My public hostname is 130.236.239.198
2023-12-05 21:26:27 WARNING tl-session: tl-xinit exited with status=1
2023-12-05 21:36:50 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-12-05 21:36:50 INFO vsmagent: Terminating. Have a nice day!
2023-12-05 21:36:50 INFO vsmagent: VSM Agent version 4.15.0 build 3358 started
2023-12-05 21:36:50 INFO vsmagent: My public hostname is 130.236.239.198
2023-12-05 21:37:03 WARNING tl-session: tl-xinit exited with status=1
2023-12-05 21:38:06 WARNING tl-session: tl-xinit exited with status=1
2023-12-05 21:39:50 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-12-05 21:39:50 INFO vsmagent: Terminating. Have a nice day!
Great, we can see from vsmagent.log that tl-xinit failed to create the session, for some reason. This failure made vsmserver to give the agent penalty points, which resulted in it not being eligble to create sessions for a short while, hence the error that the ThinLinc client reported, “No agent server was available”
So let’s dig a bit deeper and take a look at /var/opt/thinlinc/sessions/alema80/last/xinit.log to see what clues it provides.
Regards,
Martin
There are several directories in /var/opt/thinlinc/sessions/alema80/ like “10.1701807332.ended”. The xinit.log in those directories contains:
# cat 10.1701807503.ended/xinit.log
xauth: file /var/opt/thinlinc/sessions/alema80/10/Xauthority does not exist
xauth: (argv):1: bad display name "alpha:10" in "add" command
tl-xinit: xauth exited with failure code 1
The “last” directory contains the log for the currently running 4.14.0 version, which works OK. I attach it for completeness.
# cat last/xinit.log
xauth: file /var/opt/thinlinc/sessions/alema80/10/Xauthority does not exist
xauth: (argv):1: bad display name "alpha:10" in "add" command
xauth: file /var/opt/thinlinc/sessions/alema80/10/Xauthority does not exist
tl-xinit: Waiting for Xserver to accept connections...
Xvnc ThinLinc release 4.14.0 build 2408 - built Jan 26 2022 10:15:02
Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12013000
(II) Initializing extension VNC-EXTENSION
Wed Dec 6 13:39:21 2023
vncext: VNC extension running!
vncext: Listening for VNC connections on local interface(s), port 5910
vncext: created VNC server for screen 0
(II) Initializing extension Generic Event Extension
(II) Initializing extension SHAPE
(II) Initializing extension MIT-SHM
(II) Initializing extension XInputExtension
(II) Initializing extension XTEST
(II) Initializing extension BIG-REQUESTS
(II) Initializing extension SYNC
(II) Initializing extension XKEYBOARD
(II) Initializing extension XC-MISC
(II) Initializing extension XFIXES
(II) Initializing extension RENDER
(II) Initializing extension RANDR
(II) Initializing extension COMPOSITE
(II) Initializing extension DAMAGE
(II) Initializing extension MIT-SCREEN-SAVER
(II) Initializing extension DOUBLE-BUFFER
(II) Initializing extension RECORD
(II) Initializing extension DPMS
(II) Initializing extension Present
(II) Initializing extension DRI3
(II) Initializing extension X-Resource
(II) Initializing extension XVideo
(II) Initializing extension XVideo-MotionCompensation
(II) Initializing extension GLX
(II) IGLX: Loaded and initialized swrast
(II) GLX: Initialized DRISWRAST GL provider for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
> Internal error: Could not resolve keysym XF86Keyboard
Errors from xkbcomp are not fatal to the X server
Connections: accepted: 127.0.0.1::50914
VNCSConnST: closing 127.0.0.1::50914: Clean disconnection
EncodeManager: Framebuffer updates: 0
EncodeManager: Total: 0 rects, 0 pixels
EncodeManager: 0 B (1:-nan ratio)
Connections: closed: 127.0.0.1::50914
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
tl-xinit: Xserver ready for clients.
Wed Dec 6 13:39:22 2023
Connections: accepted: 127.0.0.1::50918
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
VNCSConnST: Replacing existing connection
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
--- System information ---
ThinLinc 4.14.0
Linux alpha 5.14.21-150500.55.36-default #1 SMP PREEMPT_DYNAMIC Tue Oct 31 08:37:43 UTC 2023 (e7a2e23) x86_64 x86_64 x86_64 GNU/Linux
Welcome to \S - Kernel \r (\l).
eth0: \4{eth0} \6{eth0}
LSB Version: n/a
--- End system information ---
Cannot find xsri. Background image support not available.
Running /opt/thinlinc/etc/xstartup.d/01-tl-kinit.sh (Obtaining Kerberos ticket)
kinit: Configuration file does not specify default realm when parsing name alema80
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe
Running /opt/thinlinc/etc/xstartup.d/02-tl-dbus-launch.sh (Starting session D-Bus server)
Existing session D-Bus server found.
Setting initial D-Bus and systemd environment...
Running /opt/thinlinc/etc/xstartup.d/11-tl-set-title (Setting client window title)
Running /opt/thinlinc/etc/xstartup.d/12-tl-default-keyboard (Configuring default keyboard layout)
Setting default keyboard layout to "us"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
> Internal error: Could not resolve keysym XF86Keyboard
Errors from xkbcomp are not fatal to the X server
Running /opt/thinlinc/etc/xstartup.d/15-tl-shadow-notify (Enabling notifications when the session is shadowed)
Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)
Running /opt/thinlinc/etc/xstartup.d/30-tl-xdg-user-dirs (Translating standard folders)
Running /opt/thinlinc/etc/xstartup.d/40-tl-mount-localdrives (Mounting local drives)
Running /opt/thinlinc/etc/xstartup.d/41-tl-lp-redir-launch (Setting up printer port redirection)
Running /opt/thinlinc/etc/xstartup.d/43-tl-pulseaudio-launch.sh (Starting session PulseAudio server)
W: [pulseaudio] main.c: Couldn't canonicalize binary path, cannot self execute.
Session PulseAudio server started. Redirecting applications...
Running /opt/thinlinc/etc/xstartup.d/50-tl-wait-smartcard (Waiting for smart card connection)
Stopping initial window manager...
Done.
Executing profile: mate
Using XDG session: mate
Updating D-Bus and systemd environment...
Executing XDG session command: mate-session
mate-session-check-accelerated: GL Helper exited with code 512
mate-session-check-accelerated: GLES Helper exited with code 512
gnome-keyring-daemon: no process capabilities, insecure memory might get used
mate-session[15367]: EggSMClient-WARNING: Invalid Version string '2.20210607.0' in /home/alema80/.config/autostart/kite-autostart.desktop
** Message: 13:39:35.339: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
mate-session[15367]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1'
mate-session[15367]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x55e8110e36d0 finalized while still in-construction
mate-session[15367]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
mate-session[15367]: WARNING: could not read /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
mate-session[15367]: WARNING: Unable to find provider '' of required component 'dock'
Window manager warning: Log level 128: unsetenv() is not thread-safe and should not be used after threads are created
(mate-session:15367): Gtk-WARNING **: 13:39:35.393: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
** (mate-settings-daemon:15406): WARNING **: 13:39:35.411: Could not open RFKILL control device, please verify your installation
(mate-session:15367): Gtk-WARNING **: 13:39:35.425: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(marco:15410): Gtk-WARNING **: 13:39:35.429: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(mate-panel:15418): Gtk-WARNING **: 13:39:35.439: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(marco:15410): Gtk-WARNING **: 13:39:35.455: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(mate-panel:15418): Gtk-WARNING **: 13:39:35.467: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(mate-settings-daemon:15406): Gtk-WARNING **: 13:39:35.527: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
Unable to open desktop file /usr/share/applications/google-chrome.desktop for panel launcher: No such file or directory
gnome-keyring-daemon: no process capabilities, insecure memory might get used
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
gnome-keyring-daemon: no process capabilities, insecure memory might get used
starting kited 2.20210607.0 --system-boot
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
gnome-keyring-daemon: no process capabilities, insecure memory might get used
(nm-applet:15479): Gtk-WARNING **: 13:39:35.686: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
[region= release=] 2023/12/06 13:39:35.720693 lib.go:21: loading tensorflow dynamically...
[region= release=] 2023/12/06 13:39:35.720735 loader_linux.go:17: Loading tensorflow libary libtensorflow.so.1.15.0
E: [pulseaudio] module.c: Failed to open module "module-x11-publish".
Failure: Module initialization failed
[region= release=] 2023/12/06 13:39:35.817757 lib.go:18: loading tensorflow took 97.047681ms
(mate-screensaver:15528): Gtk-WARNING **: 13:39:35.869: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(caja:15428): Gtk-WARNING **: 13:39:35.908: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
(mate-power-manager:15569): Gtk-WARNING **: 13:39:35.932: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
[region= release=] 2023/12/06 13:39:35.998123 rollbar.go:188: ROLLBAR critical http port already in use []
[region= release=] 2023/12/06 13:39:35.998143 rollbar.go:182: rollbar [critical]: http port already in use []
[region= release=] 2023/12/06 13:39:35.998149 main.go:56: http port already in use
[region= release=] 2023/12/06 13:39:35.998154 rollbar.go:188: ROLLBAR critical http port already in use []
[region= release=] 2023/12/06 13:39:35.998159 rollbar.go:182: rollbar [critical]: http port already in use []
[region= release=] 2023/12/06 13:39:35.998164 alert.go:16: alert: http port already in use
[region= release=] 2023/12/06 13:39:35.998167 main.go:33: http port already in use
kited terminated with exit code 1. terminating.
(mate-power-manager:15569): PowerManager-ERROR **: 13:39:36.029: Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied
(blueman-applet:15579): Gtk-WARNING **: 13:39:36.111: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
(evolution-alarm-notify:15489): Gtk-WARNING **: 13:39:36.245: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
blueman-applet 13.39.36 WARNING PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 13.39.36 WARNING PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher priority
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.relationtable OK
akonadi.relationtypetable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
akonadi.tagtypetable OK
[15798:7:1206/133936.884202:ERROR:command_buffer_proxy_impl.cc(141)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
Wed Dec 6 13:39:36 2023
ComparingUpdateTracker: 40.115 Mpixels in / 3.49334 Mpixels out
ComparingUpdateTracker: (1:11.4833 ratio)
(caja:15428): Gtk-WARNING **: 13:40:00.937: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
Initializing caja-sendto extension
blueman-applet 13.40.01 WARNING DiscvManager:119 update_menuitems: warning: Adapter is None
Wed Dec 6 13:42:09 2023
ComparingUpdateTracker: 981.378 Mpixels in / 75.4528 Mpixels out
ComparingUpdateTracker: (1:13.0065 ratio)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000c (Advanced M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(marco:15410): Gtk-WARNING **: 13:42:20.161: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000c (Advanced M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(mate-screensaver:15528): GLib-CRITICAL **: 14:01:18.301: Source ID 47 was not found when attempting to remove it
(polkit-mate-authentication-agent-1:15452): Gtk-WARNING **: 14:02:56.899: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000c (Advanced M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(mate-terminal:4186): dbind-WARNING **: 16:51:26.026: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000c (Advanced M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x9200007 specified for 0x9200005 (Anaconda-N).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x940000b specified for 0x9400009 (Spyder).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x940000b specified for 0x9400009 (Spyder).
Wed Dec 6 18:05:06 2023
ComparingUpdateTracker: 120.16 Gpixels in / 233.648 Mpixels out
ComparingUpdateTracker: (1:514.277 ratio)
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e00004 specified for 0x2e00002 (Slicer).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x920000c specified for 0x920000a (Slicer).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x9200064 specified for 0x9200071 ( ).
Wed Dec 6 18:12:27 2023
VNCSConnST: closing 127.0.0.1::50918: Clean disconnection
EncodeManager: Framebuffer updates: 42757
EncodeManager: Tight:
EncodeManager: Solid: 32.92 krects, 141.139 Mpixels
EncodeManager: 514.375 KiB (1:1072.58 ratio)
EncodeManager: Bitmap RLE: 4.744 krects, 1.62434 Mpixels
EncodeManager: 137.417 KiB (1:46.5785 ratio)
EncodeManager: Indexed RLE: 96.728 krects, 52.6802 Mpixels
EncodeManager: 12.9743 MiB (1:15.5743 ratio)
EncodeManager: Tight (JPEG):
EncodeManager: Full Colour: 80.314 krects, 219.561 Mpixels
EncodeManager: 303.574 MiB (1:2.76203 ratio)
EncodeManager: Total: 214.706 krects, 415.005 Mpixels
EncodeManager: 317.185 MiB (1:4.9989 ratio)
Connections: closed: 127.0.0.1::50918
ComparingUpdateTracker: 16.225 Gpixels in / 124.377 Mpixels out
ComparingUpdateTracker: (1:130.45 ratio)
E: [tunnel-source] module-tunnel-source-new.c: Stream failed: Connection terminated
E: [tunnel-sink] module-tunnel-sink-new.c: Stream failed.
Thu Dec 7 13:33:14 2023
Connections: accepted: 127.0.0.1::59344
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
VNCSConnST: Replacing existing connection
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
(mate-terminal:32101): dbind-WARNING **: 13:39:15.146: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(mate-terminal:32156): dbind-WARNING **: 13:39:47.235: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000c (Advanced M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(mate-terminal:32295): dbind-WARNING **: 13:41:58.580: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000c (Advanced M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Hey, sorry for taking so long to respond.
Thank you for providing the session log. From that we can see on the second line bad display name "alpha:10 in "add" command.
This could be because the local hostname, alpha is not resolvable in DNS.
Regards,
Martin
Hello. The hostname is set via LiU’s DHCP, and the FQDN (alpha.imv.liu.se) is in DNS. It seems that DHCP does not set the FQDN. I will try to add the FQDN to /etc/hosts. I can also ask LiU’s IT about possibly providing FQDN via DHCP. Anyway, the machine works with ThinLinc 4.14.0. Has the hostname handling changed between 4.14.0 and 4.15.0?
Regards,
Alexandr
Hello again @alema,
A workaround that you could implement yourself is to set a domain search list to /etc/resolv.conf.
Since this file gets updated automatically by netconfig, it’s not recommended to edit it by hand.
Instead, fire up your editor of choice and open /etc/sysconfig/network/config and change
NETCONFIG_DNS_STATIC_SEARCHLIST=""
to
NETCONFIG_DNS_STATIC_SEARCHLIST="imv.liu.se"
Also, according to this article,, one has to change:
NETCONFIG_DNS_POLICY="auto"
to
NETCONFIG_DNS_POLICY="STATIC NetworkManager"
After those changes has been made, executel netconfig update -f to force adjusting of
/etc/resolv.conf
(This should also survive a reboot of the server)
This will append .imv.liu.se to short hostnames and try to resolve those, if possible.
We made some adjustments to how we invoke xauth between 4.14.0 and 4.15.0, so this is a probable cause. I don’t have the details on this yet.
Please try this out and see if it makes 4.15.0 happier 
Regards,
Martin
Hello Martin. Setting NETCONFIG_DNS_STATIC_SEARCHLIST and running “netconfig update -f” solved the problem. I use Wicked, not NetworkManager, so I keep the default NETCONFIG_DNS_POLICY=“auto”. I appreciate your help.
1 Like
Hi Martin
Just a little bump here because I think that it may help others or at least remind myself from my mistakes, if you can add this to a FAQ, it may help a lot
I’m using openSUSE Tumbleweed (which is rolling release) and I’m using ThinLinc since 2020. I was running 4.14.0 lately because it was working fine for me and the tlserver does not remind us to upgrade like the tlclient does.
Today I had to use ThinLinc more intensively and decided to upgrade my tlserver also (from 4.14 to 4.17). And after the upgrade it was fine until I had to reboot. I’ve been hitting my head until now that I found this topic with the right solution, BUT something was still missing for me… I feel a little dumb to admit it, but on top of everything that you pointed out, my agent was still not connecting… turns out that my /etc/hosts was
127.0.0.1 localhost localhost.localdomain
My system was not getting its hostname from DHCP like alema’s, so, if someone has problems like this and after setting network config as suggested the system still has the same problem on /var/opt/thinlinc/sessions/USER/last/xinit.log, check /etc/hosts
I thought about creating a new topic, but this one already had the complete solution, I just had to also fix my /etc/hosts.
just one more thing, I’m also using HOST_ALIASES and using my system’s LAN IP address, not the hostname… So, even if one is using an IP address, the agent needs the hostname and hosts file to be set correctly to be able to run tl-xinit.