Collect diagnostics

Where to look when something is wrong, and what to put in a report.

In short
  • hallvi status and hallvi logs -f show the state of Hallvi itself.
  • The conversation, History and Command output show what Hallvi's commands did.
  • Remove tokens, passwords and keys before you post a report.
hallvi status

Shows whether the service and the Pi worker are running, and the installed version.

hallvi logs -f

Follows what the service prints. On Linux, it reads the service's journal.

The conversation

Shows each command, its output and how it ended. History and Command output keep them too.

Terminal

Opens your own shell on the application server. Try sudo docker ps.

A healthy hallvi status

Hallvi <installed version> (<revision>)
  service    running; starts when you log in to this Mac
  interface  http://127.0.0.1:4747
  Pi worker  running
  state      /Users/you/.local/share/hallvi
  logs       hallvi logs

If the interface is not answering, read hallvi logs. While the Pi worker is not running, Hallvi cannot take messages. For updates, run hallvi update --status and read ~/.local/share/hallvi/logs/update.log.

Command output keeps what Hallvi's own commands printed, not your application's logs. To see those, ask in the conversation, for example Show me the last 100 lines of the application's logs.

Report a problem

Open a public issue at github.com/lustoykov/hallvi/issues with:

Remove secrets first

Take out tokens, passwords, keys, and any addresses, domains or data you do not want public.