[Thinlinc-technical] Unable to remove existing agents from cluster
kaga at dtu.dk
Thu Dec 18 13:27:01 CET 2014
Thanks for your prompt response.
On 18 Dec 2014, at 13:12, Samuel Mannehed <samuel at cendio.se> wrote:
> Hi Kareem,
>> After restarting vsmserver and vsmagent on the corresponding nodes,
>> i’m still getting new sessions created on the old thinlinc agent
>> nodes, thinlinc3 and thinlinc4. According to the documentation, these
>> are the only parameters I need to update to configure the ThinLinc
>> server and agent nodes.
>> Can you please advise how to resolve this issue?
> I see two possible reasons for this behaviour:
> 1. Your test users has one or more open sessions on the agent nodes you
You are correct, I do have open sessions on the 2 removed agent nodes. But the whole reason for this exercise is to ensure that no new sessions are created on these 2 agent nodes, while enabling existing sessions to be available to users to reconnect to if required.
Is there a better way to ensure that no new sessions are created on agent nodes, while allowing access to any existing sessions still running on them?
> 2. You have specified these agents in
> the /vsmserver/explicit_agentselection parameter.
> Samuel Mannehed ThinLinc Developer
> Cendio AB https://cendio.com
> Teknikringen 8 https://twitter.com/ThinLinc
> 583 30 Linköping https://facebook.com/ThinLinc
> Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc
> Thinlinc-technical mailing list
> Thinlinc-technical at lists.cendio.se
> Manage your subscription:
More information about the Thinlinc-technical