Hi,
i am testing this software and i am not able to connect the client to the server.
my setup is:
os - oracle linux 9.u4
machines are virtualized in virtualbox and network is briged.
installed the latest thinlinc software.
no dns but i have configured hosts file.
configured vsmagent.hconf and pointed out to the 1st vm as the master.
no clues in the log.
what is the correct steps for setting up 1 vsm server (no ha) and multiple agents ?
do i need to configure same users and passwords on all the machines ?
do i need to do something with ssh ?
Have you set agent_hostname correctly in vsmagent.hconf? This parameter should be set to an IP address or hostname of the agent, which is directly accessible by the client. It should be different for each agent in the cluster.
You can find the documentation on how to do this here:
hi @aaron ,
things are not working. i have configured vsmagent and read the documentation and there is still 111 error.
i do not use central auth. for me it is every linux to itself. does that matter ? do i have to have central auth to solve 111 ?
maybe i am missing something here with the cluster purpose, the cluster is for load balancing to exact linux boxs ? i was under the impression that the master will have all it agents under a list and when i connect to the master i am presented with all the available linux boxs to choose from.
i do not see any informative logs to help me understand this 111.
do i have to configure certificates to solve 111 problem ? i have done regular install on both linux machine and haven’t changed the certificates what so ever.
10x
Could you please clarify the “111 error”, since it is nothing I recognise or familiar with. Where is this error originating from, and are you able to provide the log file or error messages associated with it (or at the very least, a screenshot)?
You don’t have to use a central authentication mechanism, no. You can configure the accounts on each agent server individually. This can be inefficient for larger systems, though.
Normally, the master will choose which agent to start the session on, based on load. So a user logging in may end up on any one of the agents.
As above, I’m not familiar with the 111 error, so will need more info. But valid TLS certificates are not a requirement. ThinLinc ships with self-signed certificates which will work, although most browsers will raise a warning.
There are parts of the ThinLinc Web Administration that are only meant to be used on the Master server. I understand that the interface is confusing, and showing the ”Cannot connect to master: 111”-error doesn’t help. Hopefully, we can improve this in the future. I added a bug in our systems for this.
When using Web Administration on a ThinLinc Agent, the following menus are not relevant:
Status → Licenses
Status → Load
Status → Sessions
VSM → Subclusters
VSM → Master
The above menus are only relevant for the ThinLinc Master. I hope that clarifies the error.
Are you also having problems connecting using a ThinLinc client?
thank you very much for the clarification.
i didn’t had problems with connecting to both servers using both web and thin. the only problem i had was due to decentralized user management. i saw the thinlinc client trying to connect to the agent server and the server so load balancing seemed to work.
