Documentation

Logs

View and analyze Huntarr's operational logs for troubleshooting.

Overview

  • Huntarr maintains detailed logs of all operations
  • Logs are available in the UI and as files on disk
  • Filter by app, level, and time range

Viewing Logs

  1. Navigate to System > Logs in the sidebar (or Settings > Logs page)
  2. The log viewer shows recent entries
  3. Use filters to narrow by:
    • App type (Sonarr, Radarr, Movie Hunt, etc.)
    • Log level (DEBUG, INFO, WARNING, ERROR)
    • Time range

Log Entry Format

Each entry includes:

  • Timestamp
  • App/module that generated the log
  • Log level (color-coded)
  • Message text

Log Files

Log files are stored in /config/logs/:

  • huntarr.log — Main application log
  • huntarr.log.1, .2, etc. — Rotated log files
  • File rotation happens when a file reaches the configured max size (default 5 MB)

Common Log Messages

Info Messages

  • "Starting hunt cycle for Sonarr" — Normal cycle start
  • "Found 3 missing episodes" — Successful detection
  • "Search triggered for Movie Title" — Search sent to the app

Warning Messages

  • "No missing items found" — Nothing to search (normal if library is complete)
  • "Rate limited by indexer" — Slow down your schedule
  • "Connection timeout" — Network issue with an *arr app

Error Messages

  • "API key invalid" — Check your app's API key
  • "Connection refused" — The *arr app may be down
  • "Database locked" — Usually resolves itself; restart if persistent

Troubleshooting with Logs

Steps:

  1. Set log level to DEBUG in Settings > Log Settings
  2. Reproduce the issue
  3. Check logs for ERROR or WARNING entries
  4. Look for the sequence of events leading to the problem
  5. Set log level back to INFO when done
DEBUG Level

DEBUG level produces a lot of output. Only enable it when actively troubleshooting, then switch back to INFO.