Bug 5693 - some session removal isn't logged
Summary: some session removal isn't logged
Status: CLOSED WORKSFORME
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.12.0
Assignee: Pierre Ossman
URL:
Keywords:
Depends on:
Blocks: 7477
  Show dependency tree / graph
 
Reported: 2015-10-30 13:39 CET by Pierre Ossman
Modified: 2020-03-10 10:02 CET (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2015-10-30 13:39:01 CET 
There are some code paths where a session might be removed without any mention of it in the log. The prominent ones are the periodic poll and get_sessions()/get_usersessions().

It would probably be useful for an admin to see when a session died (or at least when vsmserver noticed).
Comment 1 Pierre Ossman cendio 2020-03-10 09:52:40 CET 
Basically the same thing when reconnecting or shadowing. You just get the log line:

> User foo tried to reconnect to vanished session
Comment 2 Pierre Ossman cendio 2020-03-10 10:02:22 CET 
Actually this is a lie. We fixed this in r31963 for bug 5489. You get this in the log:

> 2020-03-10 10:01:05 INFO vsmserver.session: Session 127.0.0.1:11 for tltest has terminated. Removing.

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