Logs

Logs shows what the server, the torrent engine and playback are doing, newest first, as it happens. Look here when something doesn't work and the panel doesn't say why.

What you'll learn

What the page shows and how to narrow it down. How to collect a log for a bug report is in Logs and diagnostics.

The list

Entries are grouped by day. A red mark is an error, a yellow one is a warning. An entry that repeats is shown once with how many times it repeated. Click an entry to see its time, source, level and details, and to copy it.

The page keeps only recent entries. Earlier ones are in the downloaded log.

Narrow it down

• Level: All, Warnings or Errors.
• Source: one part of the server, such as Engine, Playback, Sources, Network or Backups.
• Search in messages.
• Pause stops live updates while you read, Resume starts them again.

When you scroll down the list, new entries don't push it: a button at the top says how many arrived and brings them in.

A problem in Overview about engine crashes opens this page already filtered to the engine's warnings.

Download and verbose logs

• Download logs saves the whole log as a text file.
• Verbose logs, in the More menu, also records requests and internal steps. Turn it on, reproduce the problem, download the log, and turn it off again. When the LOG_LEVEL variable is set, it decides the level and the switch is unavailable.

See Logs and diagnostics for where the log is kept, the container log, and what to put in a bug report.

Next

• Settings.
• Troubleshooting.