Skip to content

Logs get bloated if sonarr or Radarr are not properly configured, and eventually fill docker host disk #21

@jamesbiederbeck

Description

@jamesbiederbeck

NOTE THAT UNCLEAR BUG REPORTS (i.e. without the information requested below like logs, settings, versions, etc) MIGHT BE CLOSED WITHOUT ANY HELP!!

Please check https://github.com/wouterdebie/putioarr/releases if any breaking changes have been made before filing a bug report.

Describe the bug
Logs get too big if Radarr and Sonarr are not configured as expected.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

** Logs **

[2025-09-11T19:09:31Z ERROR] Error retrieving history form Radarr: error decoding response body
[2025-09-11T19:09:31Z ERROR] Error retrieving history form Sonarr: error decoding response body

^Time a million or so
** Configuration **

# Required. Username and password that sonarr/radarr use to connect to the proxy
username = "arr"
password = "<snip>"

# Required. Directory where the proxy will download files to. This directory has to be readable by
# sonarr/radarr in order to import downloads
download_directory = "/downloads"

# Optional bind address, default "0.0.0.0"
bind_address = "0.0.0.0"

# Optional TCP port, default 9091
port = 9091

# Optional log level, default "info"
loglevel = "info"

# Optional UID, default 1000. Change the owner of the downloaded files to this UID. Requires root.
uid = 1003

# Optional polling interval in secs, default 10.
polling_interval = 10

# Optional skip directories when downloding, default ["sample", "extras"]
skip_directories = ["sample", "extras"]

# Optional number of orchestration workers, default 10. Unless there are many changes coming from
# put.io, you shouldn't have to touch this number. 10 is already overkill.
orchestration_workers = 10

# Optional number of download workers, default 4. This controls how many downloads we run in parallel.
download_workers = 4

[putio]
# Required. Putio API key. You can generate one using `putioarr get-token`
api_key =  "<snip>"

# Both [sonarr] and [radarr] are optional, but you'll need at least one of them
[sonarr]
url = "http://container.lan:8989/sonarr"
# Can be found in Settings -> General
api_key = "<snip>"

[radarr]
url = "http://container.lan:7878/radarr"
# Can be found in Settings -> General
api_key = "<snip>"

Environment
docker in Ubuntu lxc on proxmox

Docker
If you're using Docker and any relevant configuration/commands.
Here's the Ansible task I run to start it, basically docker compose
- name: Run putioarr
tags:
- putioarr
- compose
community.docker.docker_compose:
project_name: putioarr
restarted: true
definition:
version: "2.1"
services:
putioarr:
image: ghcr.io/wouterdebie/putioarr:main
container_name: putioarr
environment:
- PUID=1003
- PGID=100
- TZ=America/Los_Angeles
volumes:
- /mnt/media/config/putioarr:/config
- /mnt/media/downloads:/downloads
ports:
- 9091:9091
restart: unless-stopped
Screenshots
If applicable, add screenshots to help explain your problem.

** Environment**
What operating system and version you are using.
Ubuntu 24.04
Additional context
I have limited my disk to 50GB, and 23GB of it was the repeated message above. Eventually this filled up my disk over just a couple of months, before I recreated the whole stack from lxc to the docker containers on it, and after about 6 months it reached a similar volume again. I don't have indexers set up properly in sonarr or Radarr, so I think that's the problem. I suggest adding something like this to the recommended docker

compose:
    logging:
      options:
        max-size: 50m

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions