Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker image fails to start, endlessly restarts #101

Open
LazerDickMcCheese opened this issue Aug 12, 2024 · 26 comments
Open

Docker image fails to start, endlessly restarts #101

LazerDickMcCheese opened this issue Aug 12, 2024 · 26 comments
Assignees

Comments

@LazerDickMcCheese
Copy link

LazerDickMcCheese commented Aug 12, 2024

What's wrong with the following docker compose? I'm pretty new to docker, but I thought this was going to be a simple set up.

version: "3"
services:
qbitrr:
image: feramance/qbitrr:latest
user: 1000:1000 # Required to ensure the container is run as the user who has perms to see the 2 mount points and the ability to write to the CompletedDownloadFolder mount
tty: true # Ensure the output of docker-compose logs qBitrr are properly colored.
restart: unless-stopped
environment:
- TZ=America/New_York
volumes:
- /etc/localtime:/etc/localtime:ro
- /volume1/docker/qbitrr/config:/config # Config folder for qBitrr
- /volume1/docker/qbittorrent/torrents/completed:/completed_downloads:rw

logging:
driver: "json-file"
options:
max-size: "50m"
max-file: 3

@Feramance
Copy link
Owner

Can you please attach looks? Or is nothing at all working? Any error messages?

Thanks

@LazerDickMcCheese
Copy link
Author

Sorry, but this is all of the info I have to give. The container doesn't stay active enough to generate a log at all

@Feramance
Copy link
Owner

Feramance commented Aug 14, 2024

For the sake of testing, please try the following:

services:
  qbitrr:
    image: feramance/qbitrr:latest

@LazerDickMcCheese
Copy link
Author

It start/stopped, then pumped this out:

14/08/2024 09:51 pm | NameError: name 'CONFIG' is not defined | stderr
14/08/2024 09:51 pm | CONFIG.get("Settings.FFprobeAutoUpdate", fallback=True) | stderr
14/08/2024 09:51 pm | File "/usr/local/lib/python3.10/site-packages/qBitrr/config.py", line 109, in | stderr
14/08/2024 09:51 pm | from qBitrr.config import ( | stderr
14/08/2024 09:51 pm | File "/usr/local/lib/python3.10/site-packages/qBitrr/logger.py", line 9, in | stderr
14/08/2024 09:51 pm | import qBitrr.logger # noqa | stderr
14/08/2024 09:51 pm | File "/usr/local/lib/python3.10/site-packages/qBitrr/init.py", line 4, in | stderr
14/08/2024 09:51 pm | import(pkg_name) | stderr
14/08/2024 09:51 pm | File "/usr/local/lib/python3.10/runpy.py", line 110, in _get_module_details | stderr
14/08/2024 09:51 pm | mod_name, mod_spec, code = _get_module_details(mod_name, _Error) | stderr
14/08/2024 09:51 pm | File "/usr/local/lib/python3.10/runpy.py", line 187, in _run_module_as_main | stderr
14/08/2024 09:51 pm | Traceback (most recent call last): | stderr
14/08/2024 09:51 pm | STARTING QBITRR | stdout
14/08/2024 09:51 pm | Rename it to "config.toml" then edit it and restart the container | stdout
14/08/2024 09:51 pm | 'config.rename_me.toml' has been generated | stdout
14/08/2024 09:51 pm | New config file has been saved to "/config/config.rename_me.toml" | stdout
14/08/2024 09:51 pm | config.toml has not been found

@Feramance
Copy link
Owner

Ok, so now add:

volumes:
  - /path/to/appdata/qbitrr:/config

Run it again, then rename the config file generated and change any values required within it

@Feramance Feramance self-assigned this Aug 16, 2024
@Feramance
Copy link
Owner

Have you managed to get anywhere? @LazerDickMcCheese

@LazerDickMcCheese
Copy link
Author

Long story short, changed hardware and had to do a full setup again so I was out of commission for a few days. I just set this up again, I'm getting many errors about "parser.py" Do you want the logs?

@Feramance
Copy link
Owner

Feramance commented Aug 22, 2024

Hi, yes. Send trace logs (adjust log level in configs) and config please, ideally in a zip

@Feramance
Copy link
Owner

Feramance commented Sep 9, 2024

[config.zip]
Try this config as you didn't pass the correct value types. To make sure the TOML is valid I suggest using VSCode with the following extension installed:

Even Better TOML - https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml

@LazerDickMcCheese
Copy link
Author

LazerDickMcCheese commented Sep 9, 2024

It's been a while since I looked at those files, I just realized they have my APIs and passwords in them. Would you mind deleting the ones you uploaded as well? So we have progress, qBitrr isn't stuck restarting. It's currently failing to connect to my Radarr and Sonarr instances, but those are the only errors.

The trace logs show some form of this:
Failed to get version
...
Starting xxxx monitor
Starting torrent monitoring for xxxx
Could not connect to 192.168.x.x:xxxx
Could not connect to 192.168.x.x:xxxx
Failed to connected to the Arr instance, sleeping for 0:05:00

The instances are up and available however, the IPs listed are correct.

@Feramance
Copy link
Owner

Kindly send new logs so I can take a look please

@LazerDickMcCheese
Copy link
Author

logs.zip

Thank you for your help

@Feramance
Copy link
Owner

I'll update the description but, add http:// in front of all your Arr urls and let me know how it goes. Also ensure that any numeric values are not surrounded by ", same with all boolean values, and make sure any other value (text/alphanumeric) is surrounded by "

@LazerDickMcCheese
Copy link
Author

I believe that fixed it! Strange, qbit works without http:// in front of the address so I would've never thought to try that. Thank you again for your help.

@LazerDickMcCheese
Copy link
Author

qbitrr added tags to my qbit, so I assumed it was working. Fast forward a few days and nothing has been tagged (some of them should have been due to the config settings). So I stopped the container, checked the config.toml, and restarted the container. It's back to restarting continuously.

As a side note, qbitrr says it doesn't have permissions to its config folder if I set the YAML to the UID I usually use for docker containers despite having read/write permissions.

qbitrr.zip

@Feramance
Copy link
Owner

If you're on a linux system, I suggest first trying to run chmod -R 777 /path/to/qbitrr/data, and see how that goes

@LazerDickMcCheese
Copy link
Author

I entered the command, rebuilt the container, and it's still giving the "AttributeError: 'String' object has no attribute 'get'" error in the log and restart-looping

@Feramance
Copy link
Owner

I'll need logs again please

@LazerDickMcCheese
Copy link
Author

When I start the container, only 2 of the logs write. "Category exists without save path" The arrs have been working just fine, so I don't know which path it's talking about.

"qbitrr.zip

@Feramance
Copy link
Owner

Can you run chmod -R 777 /path/to/qBitrr/config and try running it again? It should produce a few more logs than just that.

Also check docker logs by running docker logs qBitrr in a terminal to check what else is being outputted, sometimes some things aren't captured with the file logs.

@LazerDickMcCheese
Copy link
Author

qbitrr.txt

@Feramance
Copy link
Owner

Ok, I'll work on fixing this, I see the problem now. In the meantime send over your config, I'll edit it slightly and send it back so you can have a working config

@LazerDickMcCheese
Copy link
Author

Thank you for your help, you've been very kind. Did I break something? I'm lost here

config.zip

@Feramance
Copy link
Owner

config.zip
Use this config, the issue is the trackers, I'll look into it but you can use qBitrr in the meantime

@LazerDickMcCheese
Copy link
Author

It's definitely working now! About 600 stalled downloads corrected themselves, and my NAS has been purring ever since. On behalf of everyone using my server, thank you for your help

@Feramance
Copy link
Owner

Very happy to hear, though I'm leaving this open to remind myself to check the trackers issue you had

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants