Chapter 13Logs and diagnostics
This chapter is for the support technician. It explains where the program writes its logs, what the support screens show, how a status report is sent to Clarus support, and how a remote support session is opened.
13.1 The logs
| Log | Where | What to look for in it |
|---|---|---|
clarus.log | logs in the data folder | The program's errors and warnings. Rotated every 10 MB, with five kept before it |
postgresql.log | logs in the data folder | The database's errors while it runs |
postgresql-startup.log | logs in the data folder | Why the database did not start |
clarus-lis-updater-<date and time>.log | logs in the data folder | What happened in each update |
install-transcript.log | The program's folder | What happened at installation |
clarus-member-*.log | data\logs in the program's folder, on a member computer | The program running on the member computer |
The full paths are in B.4 The logs.
13.2 The support screens
In the Support menu:
| Screen | What it holds |
|---|---|
| Health and diagnostics | Cards: Successful backups, the Database and its integrity, Verified audit events, Registered devices, Data protection and Local server readiness. Beneath them is the database's maintenance (see 4.5 Checking its health) |
| Cases and reports | The cases sent to support, and their reports |
| Go-live | What is left before the laboratory really works on the program |
| Server and updates | The database, its address and port, and the state of updates |
13.3 The status report to support
Health and diagnostics and Cases and reports both have the Send the system's state to support button:
- Under Describe the problem (optional), write what happened, when, and on which screen.
- Press Read it before sending to see the report as it will be sent.
- Press Send now. The program then shows the report's reference at support: give it when you call.
| Sends | Never sends |
|---|---|
| The version, the licence state, the free disk, the backups, the devices, and the last errors, each line cleaned. | No patient, no order, no result, no report: no name, code or count that could identify anybody. |
From the logs, the report takes the last 400 lines of the three newest files, and cleans every line. If it cannot reach support, it is saved to a file to send by hand, and the screen says where.
13.4 A remote support session
Support enters your copy with your agreement, for a time you choose, and you stop it whenever you wish.
- From My account, press Ask for technical support.
- Describe the problem under What is wrong?. The status report that goes with it can be read first: Show what will be sent.
- Press Next: the agreement, choose the Session length, then I agree: open the session.
- The Support session code appears. Read it to the Clarus support engineer; it is good for entering for a limited time, which the screen shows. The code is shown this time only and is kept nowhere.
While the session is open, a strip shows at the top of every screen: Clarus technical support is inside your copy now. Anyone in the laboratory can stop the session at any moment from the strip at the top of every screen. The session ends by itself on time.
In the session's window:
- Conversation, including sending pictures of the analyser's or the program's screen.
- What support did: every change support made, what was there before and what is there after, and The way back.
- Patient data: support sees no patient data without a separate permission: Allow patient data to be seen. It can be withdrawn at any time: Withdraw the patient-data permission.
Support work that needs Windows administrator rights is carried out by the Support task (see C.2 Scheduled tasks). If that task is not registered, Windows asks for the administrator's consent on the computer itself.
13.5 Before calling support
Gather:
- The program's version, from Licence.
- A description of what happened, when, and on which computer and screen.
- A picture of the message as it appeared.
- The status report, sent or saved to a file.