Bug 830 - difficult to find all session log data
Summary: difficult to find all session log data
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Administration (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Enhancement
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2004-08-17 15:01 CEST by Erik Forsberg
Modified: 2023-07-11 09:28 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Erik Forsberg cendio 2004-08-17 15:01:52 CEST
When a user can't login for some reason, the debugging procedure currently is a
bit tedious:

* Login to the vsm server machine and read vsmserver.log. Find out if a session
was created, and if so, on which vsm agent machine. If there are two vsm server
machines (in a HA configuration), you must first determine which one is running.

* Read vsmagent.log on the agent machine selected. See if it says something
about the user.

* Read xinit.log for the user, on the correct agent machine.

It would be nice if you could just enter the username in a tladm module, and
then get all the relevant information collected in one place.

A "low budget" version would be to just find out which agent machine the user
was assigned, and then fetch the xinit.log from that machine.
Comment 1 Peter Åstrand cendio 2004-10-04 10:20:42 CEST
I have another idea: Why not let vsmagent create a ~/.thinlinc/last-termserver,
which contains information about the last selected agent host? This will allow
ordinary users to debug their session startup problems. 

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