I use ThinLinc from year or two 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] # 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 ?
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.
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
[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 …
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
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
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?
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.
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.
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.
This thread is helpful. Thank you. Interesting in that we have the same error, but are running RHEL8.8 with kernel 4.18.0-477.13.1.el8_8.x86_64. We opened a support ticket with Cendio. Oddly, this started an hour into our day after everyone logged on and zero problems for a few months. What changed? Nothing that we can see as we only do updates quarterly during a well planned and approved maintenance window. Will start a new thread as this has an official solution. Offering here to be complete.
Full uname output:
4.18.0-477.13.1.el8_8.x86_64 #1 SMP Thu May 18 10:27:05 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
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)