Bug 2000 - Display error when killing sessions on downed agent
Summary: Display error when killing sessions on downed agent
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: 1.5.0
Hardware: PC All
: P2 Enhancement
Target Milestone: MediumPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2006-05-16 10:37 CEST by Pierre Ossman
Modified: 2021-12-15 08:49 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2006-05-16 10:37:36 CEST
When terminating a session on a downed agent, tladm behaves as if things are
just fine. Since the agent is down, it's impossible to kill the session. This
should be indicated to the user.
Comment 1 Erik Forsberg cendio 2006-07-06 13:27:41 CEST
See also bug 1559, which seems like about the same piece of code. 
Comment 2 Pierre Ossman cendio 2011-08-25 14:08:34 CEST
New code. Check if problem remains.
Comment 3 Morgan Eklöf cendio 2011-11-14 16:30:39 CET
Problem remains, but this is due to the VSM server reporting no error. A remote kill_session call to VSM server results in server data {'errcode': 0, 'result': 0}.
Comment 4 Pierre Ossman cendio 2019-01-22 15:16:59 CET
This is a bit different these days. We now have better handling of downed agents, and the interface will change a bit if the agent is unresponsive. It now prints a warning that the session cannot be verified, and the button changes text to "Abandon".

However you still get no warning if the agent becomes unresponsive after opening the session details, and I'm not sure if other failures are handled either.

Note You need to log in before you can comment on or make changes to this bug.