ThinLinc login failed. (No agent server was available)

Hi

I use ThinLinc from year or two :slight_smile: and till now I don’t have any issue. But from today when I try to connect by web or app I get error: ThinLinc login failed. (No agent server was available)

My environment:
Fedora 37 on Intel NUC (physical system)
thinlinc 4.14


[root@serwerek log] # systemctl status vsmagent
● vsmagent.service - ThinLinc VSM agent
     Loaded: loaded (/usr/lib/systemd/system/vsmagent.service; enabled; preset: disabled)
     Active: active (running) since Mon 2023-01-09 13:08:55 CET; 12min ago
    Process: 1224 ExecStart=/bin/bash --login -c /opt/thinlinc/sbin/vsmagent (code=exited, status=0/SUCCESS)
   Main PID: 1380 (python3)
      Tasks: 1 (limit: 9315)
     Memory: 18.3M
     CGroup: /system.slice/vsmagent.service
             └─1380 /opt/thinlinc/libexec/python3 /opt/thinlinc/sbin/vsmagent

sty 09 13:08:55 serwerek systemd[1]: Starting vsmagent.service - ThinLinc VSM agent...
sty 09 13:08:55 serwerek systemd[1]: Started vsmagent.service - ThinLinc VSM agent.

[root@serwerek log] # tail -20 vsmagent.log
2023-01-09 11:47:04 WARNING vsmagent: Always use fully qualified hostnames for agent_hostname.
2023-01-09 11:47:04 INFO vsmagent: My public hostname is serwerek
2023-01-09 12:05:44 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 12:05:44 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 12:06:18 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 12:06:18 INFO vsmagent: My public hostname is 172.16.0.135
2023-01-09 12:12:58 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 12:12:58 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 12:13:04 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 12:13:04 INFO vsmagent: My public hostname is 172.16.0.135
2023-01-09 12:14:13 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 12:14:13 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 13:05:21 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 13:05:21 INFO vsmagent: My public hostname is 172.16.0.135
2023-01-09 13:08:19 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 13:08:19 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 13:08:55 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 13:08:55 WARNING vsmagent: agent_hostname serwerek does not contain a dot!
2023-01-09 13:08:55 WARNING vsmagent: Always use fully qualified hostnames for agent_hostname.
2023-01-09 13:08:55 INFO vsmagent: My public hostname is serwerek

[root@serwerek log] # tail -20 vsmserver.log
2023-01-09 13:20:46 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 7 penalty points, decreasing to 6 after successful periodic load update
2023-01-09 13:21:26 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 6 penalty points, decreasing to 5 after successful periodic load update
2023-01-09 13:22:06 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 5 penalty points, decreasing to 4 after successful periodic load update
2023-01-09 13:22:46 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 4 penalty points, decreasing to 3 after successful periodic load update
2023-01-09 13:23:18 INFO vsmserver.session: User with uid 1000 (mipo) requested a new session
2023-01-09 13:23:18 WARNING vsmserver.session: VSM Agent 127.0.0.1:904 responded with permission denied in request for new session. 
2023-01-09 13:23:18 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 8
2023-01-09 13:23:18 WARNING vsmserver: No working agents found trying to start new session for mipo
2023-01-09 13:23:58 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 8 penalty points, decreasing to 7 after successful periodic load update
2023-01-09 13:24:38 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 7 penalty points, decreasing to 6 after successful periodic load update
2023-01-09 13:25:18 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 6 penalty points, decreasing to 5 after successful periodic load update
2023-01-09 13:25:58 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 5 penalty points, decreasing to 4 after successful periodic load update
2023-01-09 13:26:38 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 4 penalty points, decreasing to 3 after successful periodic load update
2023-01-09 13:27:18 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 3 penalty points, decreasing to 2 after successful periodic load update
2023-01-09 13:27:58 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 2 penalty points, decreasing to 1 after successful periodic load update
2023-01-09 13:28:38 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 1 penalty points, decreasing to 0 after successful periodic load update
2023-01-09 13:29:50 INFO vsmserver.session: User with uid 1000 (mipo) requested a new session
2023-01-09 13:29:50 WARNING vsmserver.session: VSM Agent 127.0.0.1:904 responded with permission denied in request for new session. 
2023-01-09 13:29:50 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-01-09 13:29:50 WARNING vsmserver: No working agents found trying to start new session for mipo

I even try to fully remove thinlinc (dnf remove thinlinc*; rm -fr /opt/thinlinc ) and install it again but same issue appear. Can someone help me ?:smiley:

Best regards
Michal

1 Like

Hello @mipo and welcome to the community!

The vsmserver detects that the vsmagent is unable to create sessions, and increasing its penalty points for not being able to do so, which will lead to the error your client displays: “No agent server was available”.

According to your vsmagent log, there seems to be permissions problems when trying to create a session:

2023-01-09 13:29:50 WARNING vsmserver.session: VSM Agent 127.0.0.1:904 responded with permission denied in request for new session.

You need to verify correct permission for mipo homedir. Are you able to execute this from a remote machine

To verify that the home directory works, the following command can be used:
$ ssh <username>@<agenthost> touch .

If the home directory is correctly mounted and writable by the user, the above command will not produce any output except the password question.

Hi

Yes I see that warning with permission but have no idea what permission need to be checked…

when I try to execute your command nothing happen (as expected) first as a mipo user on other system with key authentication and second as a root with assword

-> ssh mipo @ 172.16.0.135 touch .
-> sudo su -
root @ DESKTOP-GCA6N5F:~# ssh mipo @ 172.16.0.135 touch .
mipo @ 172.16.0.135's password: 
root @ DESKTOP-GCA6N5F:~#
[root@serwerek mipo] # ls -la /home | grep mipo
drwx--x---+ 53 mipo      mipo       4096 01-09 14:10 mipo
[root@serwerek mipo] # df -h | grep home
/dev/mapper/fedora_vg-home       158G  135G   17G  90% /home

And for all files and folder user mipo are owned.

Same issue for other user:

[root@serwerek log] # tail -20 vsmserver.log
2023-01-09 13:29:50 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-01-09 13:29:50 WARNING vsmserver: No working agents found trying to start new session for mipo
2023-01-09 13:30:30 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 5 penalty points, decreasing to 4 after successful periodic load update
2023-01-09 13:31:10 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 4 penalty points, decreasing to 3 after successful periodic load update
2023-01-09 13:31:50 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 3 penalty points, decreasing to 2 after successful periodic load update
2023-01-09 13:32:30 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 2 penalty points, decreasing to 1 after successful periodic load update
2023-01-09 13:33:10 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 1 penalty points, decreasing to 0 after successful periodic load update
2023-01-09 13:44:38 INFO vsmserver.session: User with uid 1000 (mipo) requested a new session
2023-01-09 13:44:38 WARNING vsmserver.session: VSM Agent 127.0.0.1:904 responded with permission denied in request for new session. 
2023-01-09 13:44:38 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-01-09 13:44:38 WARNING vsmserver: No working agents found trying to start new session for mipo
2023-01-09 13:45:18 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 5 penalty points, decreasing to 4 after successful periodic load update
2023-01-09 13:45:58 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 4 penalty points, decreasing to 3 after successful periodic load update
2023-01-09 13:46:38 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 3 penalty points, decreasing to 2 after successful periodic load update
2023-01-09 13:47:18 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 2 penalty points, decreasing to 1 after successful periodic load update
2023-01-09 13:47:58 INFO vsmserver.loadinfo: VSM Agent 127.0.0.1 had 1 penalty points, decreasing to 0 after successful periodic load update
2023-01-09 14:14:20 INFO vsmserver.session: User with uid 1004 (test) requested a new session
2023-01-09 14:14:20 WARNING vsmserver.session: VSM Agent 127.0.0.1:904 responded with permission denied in request for new session. 
2023-01-09 14:14:20 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-01-09 14:14:20 WARNING vsmserver: No working agents found trying to start new session for test

PS. sorry I need put space between user and ip as this forum has limitation for number of link …

Best Regards
Michal

Just a quick follow-up question. Are the user home directories over autofs/nfs or local to your server?

Local disk (LVM)

[root@serwerek ~] # mount | grep home
/dev/mapper/fedora_vg-home on /home type ext4 (rw,relatime,seclabel)
[root@serwerek ~] # pvs
  PV             VG        Fmt  Attr PSize    PFree   
  /dev/nvme0n1p3 fedora_vg lvm2 a--  <952,37g <158,37g

Let’s increase the logging to see if it yields any more clues to what’s going on here.

Modifiy the following section in /opt/thinlinc/etc/conf.d/vsmagent.hconf

[/vsmagent/logging/levels]
# Execution of external commands
vsmagent.extcmd=INFO
# Info about sessions
vsmagent.session=INFO
# XMLRPC debugging.
vsmagent.xmlrpc=INFO

Replace INFO with either DEBUG or DEBUG2 (DEBUG2 is more verbose) and restart vsmagent.service after modifying the configuration
$ sudo systemctl restart vsmagent

Regards,
Martin

Hi

I rise logs to agent and server all to DEBUG2 and restart both services:


[root@serwerek log] # tail -60 vsmserver.log
2023-01-09 17:51:31 INFO vsmserver: VSM Server version 4.14.0 build 2408 started
2023-01-09 17:51:31 INFO vsmserver.license: Updating license data from disk to memory
2023-01-09 17:51:31 INFO vsmserver.license: License summary: 10 concurrent users. Hard limit of 10 concurrent users. 
2023-01-09 17:51:31 DEBUG vsmserver: Hosts allowed to do restricted operations: ['127.0.0.1', 'serwerek']
2023-01-09 17:51:31 DEBUG vsmserver.HA: Allowed HA update hosts: []
2023-01-09 17:51:31 INFO vsmserver.session: Loaded 0 sessions for 0 users from file
2023-01-09 17:51:31 DEBUG vsmserver.session: Loaded sessions: []
2023-01-09 17:51:31 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Mon Jan  9 17:52:11 2023
2023-01-09 17:51:47 DEBUG vsmserver: Handling connection from ('127.0.0.1', 60958)
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-09 17:51:47 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-09 17:51:47 DEBUG2 vsmserver: Setting up removal of /var/run/thinlinc/master/1000 at Mon Jan  9 17:53:47 2023
2023-01-09 17:51:47 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-09 17:51:47 DEBUG vsmserver: Handling connection from ('127.0.0.1', 60970)
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-09 17:51:47 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-09 17:51:47 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method get_capabilities on socket owned by uid 1000
2023-01-09 17:51:47 DEBUG vsmserver: Handling connection from ('127.0.0.1', 60976)
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-09 17:51:47 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-09 17:51:47 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method get_user_sessions on socket owned by uid 1000
2023-01-09 17:51:47 DEBUG vsmserver.session: User with uid 1000 requested a list of his/her sessions
2023-01-09 17:51:47 DEBUG vsmserver.extproc: Starting process ['/opt/thinlinc/libexec/tl-session', '--initgroups']
2023-01-09 17:51:47 DEBUG vsmserver: GetUserSessionHandler: List of groups: [1000, 10, 11, 970, 972, 1004, 1006, 65534]
2023-01-09 17:51:47 DEBUG vsmserver: Handling connection from ('127.0.0.1', 60988)
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-09 17:51:47 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-09 17:51:47 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-09 17:51:47 DEBUG2 vsmserver: Handling method new_session on socket owned by uid 1000
2023-01-09 17:51:47 INFO vsmserver.session: User with uid 1000 (mipo) requested a new session
2023-01-09 17:51:47 DEBUG vsmserver.session: client_params: {'capabilities': {'client_build': '2324', 'client_lang': 'C.UTF-8', 'client_platform': 'Linux', 'client_version': '4.14.0', 'sound': {}}, 'hwaddr': '00155D292A1F'}
2023-01-09 17:51:47 DEBUG vsmserver.extproc: Starting process ['/opt/thinlinc/libexec/tl-session', '--initgroups']
2023-01-09 17:51:47 DEBUG vsmserver: List of groups: [1000, 10, 11, 970, 972, 1004, 1006, 65534]
2023-01-09 17:51:47 DEBUG vsmserver: User mipo requesting session on cluster 'Default'
2023-01-09 17:51:47 DEBUG vsmserver: Contacting VSM Agent 127.0.0.1 to request a new session for mipo
2023-01-09 17:51:47 WARNING vsmserver.session: VSM Agent 127.0.0.1:904 responded with permission denied in request for new session. 
2023-01-09 17:51:47 WARNING vsmserver.loadinfo: Agent 127.0.0.1 failed to start session, Increasing penalty points by 5 to 5
2023-01-09 17:51:47 WARNING vsmserver: No working agents found trying to start new session for mipo

[root@serwerek log] # tail -20 vsmagent.log
2023-01-09 12:06:18 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 12:06:18 INFO vsmagent: My public hostname is 172.16.0.135
2023-01-09 12:12:58 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 12:12:58 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 12:13:04 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 12:13:04 INFO vsmagent: My public hostname is 172.16.0.135
2023-01-09 12:14:13 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 12:14:13 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 13:05:21 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 13:05:21 INFO vsmagent: My public hostname is 172.16.0.135
2023-01-09 13:08:19 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 13:08:19 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 13:08:55 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 13:08:55 WARNING vsmagent: agent_hostname serwerek does not contain a dot!
2023-01-09 13:08:55 WARNING vsmagent: Always use fully qualified hostnames for agent_hostname.
2023-01-09 13:08:55 INFO vsmagent: My public hostname is serwerek
2023-01-09 17:48:32 INFO vsmagent: Got SIGTERM, signaling process to quit
2023-01-09 17:48:32 INFO vsmagent: Terminating. Have a nice day!
2023-01-09 17:48:32 INFO vsmagent: VSM Agent version 4.14.0 build 2408 started
2023-01-09 17:48:32 INFO vsmagent: My public hostname is 172.16.0.135

I have the exact same issue, running fedora 37, and intel NUC, started yesterday after a system-update and reboot for me, been working fine for a couple of weeks before that. (I have my $HOME on an nfs mount).
My logs is almost identical to mipo:s. and I have no problems running ssh to the server.


2023-01-09 18:21:33 INFO vsmserver.session: User with uid 1000 (mickevi) requested a new session
2023-01-09 18:21:33 WARNING vsmserver.session: VSM Agent 192.168.0.110:904 responded with permission denied in request for new session.


2023-01-09 18:21:24 DEBUG2 vsmagent: Scheduling next housekeeping at Mon Jan  9 18:21:34 2023


2023-01-09 18:21:33 DEBUG vsmagent: Handling connection from ('192.168.0.110', 1023)
2023-01-09 18:21:33 DEBUG2 vsmagent: Handling method get_load
2023-01-09 18:21:33 DEBUG vsmagent: Handling connection from ('192.168.0.110', 57636)
2023-01-09 18:21:33 DEBUG2 vsmagent: Handling method req_session
2023-01-09 18:21:34 DEBUG2 vsmagent: Waiting for children
2023-01-09 18:21:34 DEBUG2 vsmagent: Updating dynamic load information


Hi

Yes my issue start after update i forgot to mention that … and now when i check what was updated I only find that maybe python brake ThinLinc:

    Upgrade       python2.7-2.7.18-26.fc37.x86_64                    @updates
    Upgraded      python2.7-2.7.18-25.fc37.x86_64                    @@System
    Upgrade       python3-firewall-1.2.3-1.fc37.noarch               @updates
    Upgraded      python3-firewall-1.2.2-1.fc37.noarch               @@System
    Upgrade       python3-pwquality-1.4.5-1.fc37.x86_64              @updates
    Upgraded      python3-pwquality-1.4.4-11.fc37.x86_64             @@System
    Upgrade       python3-unbound-1.17.0-1.fc37.x86_64               @updates
    Upgraded      python3-unbound-1.16.3-3.fc37.x86_64               @@System

Will try to reverse those change and update later

We’ve been able to reproduce this issue internally. For what it looks like right now it could have have something todo with the 6.0.18 kernel in Fedora.

@mipo Was your kernel not updated? Which one are you running?

Hi

yes kernel was update as well now I’m on:

[root@serwerek ~] # uname -a
Linux serwerek 6.0.17-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jan 4 15:58:35 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Having the same issue, narrowed down the issue to the 6.0.15 → 6.0.16 kernel update. If you want ThinLinc to work currently, roll back to 6.0.15. As anything higher than 6.0.15 breaks it.

2 Likes

Hi

Yes I boot with old kernel and all back to normal I’m able to start ThinLinc session :smiley:

[root@serwerek ~] # uname -a
Linux serwerek 6.0.15-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Dec 21 18:33:23 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[root@serwerek log] # tail -70 vsmserver.log
2023-01-10 12:29:35 DEBUG vsmserver.session: Loaded sessions: []
2023-01-10 12:29:35 WARNING vsmserver.loadinfo: [Errno 111] Połączenie odrzucone talking to VSM Agent 127.0.0.1:904 in request for loadinfo. Marking as down.
2023-01-10 12:29:35 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:30:15 2023
2023-01-10 12:30:15 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:30:55 2023
2023-01-10 12:30:55 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:31:35 2023
2023-01-10 12:31:35 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:32:15 2023
2023-01-10 12:32:15 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:32:55 2023
2023-01-10 12:32:55 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:33:35 2023
2023-01-10 12:33:35 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:34:15 2023
2023-01-10 12:34:15 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:34:55 2023
2023-01-10 12:34:55 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:35:35 2023
2023-01-10 12:35:35 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:36:15 2023
2023-01-10 12:36:15 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:36:55 2023
2023-01-10 12:36:55 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:37:35 2023
2023-01-10 12:37:17 INFO vsmserver: Got SIGTERM, signaling process to quit
2023-01-10 12:37:17 DEBUG vsmserver.session: Writing active sessions to disk
2023-01-10 12:37:17 DEBUG vsmserver.session: Done writing sessions
2023-01-10 12:37:17 INFO vsmserver: Terminating. Have a nice day!
2023-01-10 12:38:08 INFO vsmserver: VSM Server version 4.14.0 build 2408 started
2023-01-10 12:38:08 INFO vsmserver.license: Updating license data from disk to memory
2023-01-10 12:38:08 INFO vsmserver.license: License summary: 10 concurrent users. Hard limit of 10 concurrent users. 
2023-01-10 12:38:08 DEBUG vsmserver: Hosts allowed to do restricted operations: ['127.0.0.1', 'serwerek']
2023-01-10 12:38:08 DEBUG vsmserver.HA: Allowed HA update hosts: []
2023-01-10 12:38:08 INFO vsmserver.session: Loaded 0 sessions for 0 users from file
2023-01-10 12:38:08 DEBUG vsmserver.session: Loaded sessions: []
2023-01-10 12:38:08 WARNING vsmserver.loadinfo: [Errno 111] Połączenie odrzucone talking to VSM Agent 127.0.0.1:904 in request for loadinfo. Marking as down.
2023-01-10 12:38:08 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:38:48 2023
2023-01-10 12:38:40 DEBUG vsmserver: Handling connection from ('127.0.0.1', 54660)
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-10 12:38:40 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-10 12:38:40 DEBUG2 vsmserver: Setting up removal of /var/run/thinlinc/master/1000 at Tue Jan 10 12:40:40 2023
2023-01-10 12:38:40 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-10 12:38:40 DEBUG vsmserver: Handling connection from ('127.0.0.1', 54662)
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-10 12:38:40 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-10 12:38:40 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method get_capabilities on socket owned by uid 1000
2023-01-10 12:38:40 DEBUG vsmserver: Handling connection from ('127.0.0.1', 54678)
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-10 12:38:40 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-10 12:38:40 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method get_user_sessions on socket owned by uid 1000
2023-01-10 12:38:40 DEBUG vsmserver.session: User with uid 1000 requested a list of his/her sessions
2023-01-10 12:38:40 DEBUG vsmserver.extproc: Starting process ['/opt/thinlinc/libexec/tl-session', '--initgroups']
2023-01-10 12:38:40 DEBUG vsmserver: GetUserSessionHandler: List of groups: [1000, 10, 11, 970, 972, 1004, 1006, 65534]
2023-01-10 12:38:40 DEBUG vsmserver: Handling connection from ('127.0.0.1', 54690)
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method create_user_socket
2023-01-10 12:38:40 DEBUG vsmserver.session: User with uid 1000 requested a socket
2023-01-10 12:38:40 DEBUG2 vsmserver: Accept on user socket with uid 1000
2023-01-10 12:38:40 DEBUG2 vsmserver: Handling method new_session on socket owned by uid 1000
2023-01-10 12:38:40 INFO vsmserver.session: User with uid 1000 (mipo) requested a new session
2023-01-10 12:38:40 DEBUG vsmserver.session: client_params: {'capabilities': {'client_build': '2324', 'client_lang': 'C.UTF-8', 'client_platform': 'Linux', 'client_version': '4.14.0', 'sound': {}}, 'hwaddr': '00155D292A1F'}
2023-01-10 12:38:40 DEBUG vsmserver.extproc: Starting process ['/opt/thinlinc/libexec/tl-session', '--initgroups']
2023-01-10 12:38:40 DEBUG vsmserver: List of groups: [1000, 10, 11, 970, 972, 1004, 1006, 65534]
2023-01-10 12:38:40 DEBUG vsmserver: User mipo requesting session on cluster 'Default'
2023-01-10 12:38:40 DEBUG vsmserver: Contacting VSM Agent 127.0.0.1 to request a new session for mipo
2023-01-10 12:38:42 INFO vsmserver.session: Session 127.0.0.1:10 created for user mipo
2023-01-10 12:38:42 DEBUG vsmserver.session: Writing active sessions to disk
2023-01-10 12:38:42 DEBUG vsmserver.session: Done writing sessions
2023-01-10 12:38:42 DEBUG vsmserver: Requesting VSM Agent 127.0.0.1 to unbind ports for mipo's display 10
2023-01-10 12:38:48 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:39:20 2023
2023-01-10 12:38:50 DEBUG vsmserver: Handling connection from ('127.0.0.1', 54706)
2023-01-10 12:38:50 DEBUG2 vsmserver: Handling method get_public_sessioninfo
2023-01-10 12:38:51 DEBUG vsmserver: Handling connection from ('127.0.0.1', 53050)
2023-01-10 12:38:51 DEBUG2 vsmserver: Handling method get_public_sessioninfo
2023-01-10 12:39:20 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:40:00 2023
2023-01-10 12:40:00 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:40:40 2023
2023-01-10 12:40:40 DEBUG2 vsmserver: Setting up removal of /var/run/thinlinc/master/1000 at Tue Jan 10 12:40:40 2023
2023-01-10 12:40:40 DEBUG2 vsmserver: Removing /var/run/thinlinc/master/1000 due to timeout
2023-01-10 12:40:40 DEBUG vsmserver: Scheduled load update of 127.0.0.1 at Tue Jan 10 12:41:20 2023

@blacksnow Thanks it was on my check list to do but …

@martin Do you plan create any patch for ThinLinc ?

@mipo No, there is nothing wrong in ThinLinc. There is some bug in either the Fedora version of the kernel or upstream. Working on a bug report now.

1 Like

Workaround for the moment is to downgrade your kernel to 6.0.15

If possible can you post a link to the bug report you file to redhat or fedora. Just want to be able to track it so I know when I can resume my normal updates on some systems.

Hey @blacksnow
Sorry for the late reply, here it is
https://bugzilla.redhat.com/show_bug.cgi?id=2159711&

1 Like

Just an update on this, I see some movement on the bug report although no confirmed fix. However, if you upgrade your kernel to the latest 6.1.5.200.fc37 then the issue is no longer there.

2 Likes

Can confirm it now works for me too – kernel 6.1.6-200.fc37.x86_64