qbittorrent not starting

Had qbittorrent running fine for months here using the standard yml configuration from lscr, but a recent power outage fried it and I haven't been able to get the new one going.

Having read the thread "Qbittorrent wont start aftwr update" here, I've made sure to fully remove the existing image and then prune (both cli and in the Compose > File interface). The yml checks out, the image pulls, all fine. It appears to start without issue, but immediately starts cycling through restarts. I get no logs, no docker activity in journalctl, nothing.

Docker itself is running — I have a mariadb chugging along there without incident, thankfully. But qbit resolutely refuses to start or tell me why.

Ideas?

SMART results are all good. And nothing else is failing.

I'm pretty sure I have the permissions right, but would a problem there result in this kind of problem (restart-loop with no logs)?

Interesting. No, it doesn't run for long enough to generate a log in docker, but if I watch journalctl during the attempt, I see only.

Zitat

Sep 23 09:49:46 rasmedia systemd[14594]: run-docker-netns-c5afbc95205a.mount: Succeeded.

Sep 23 09:49:46 rasmedia systemd[14594]: var-lib-docker-overlay2-79c8deb12df02e106e204fffa8694f60af2c1e0d07906a2db971300193f9e0f9-merged.mount: Succeeded.

I'm thinking it might be time to start over entirely. A weekend project.

Totally blank. Just "END OF LINE" if I look through the front end.

And 'docker logs qbittorrent' returns nothing without error.

So weird. First, I checked 'compose/qBittorrent/data/logs/qbittorrent.log' — but qBittorrent was never written into /compose. It didn't exist. When this was working last week, it was all there, of course.

As a total Docker amateur (it's amazing I ever had this working in the first place, to be honest), I didn't know a thing about not using /compose for everything.

Just now, I scrapped everything, added /data/qBittorrent (& pointed to that in the yml). Still nothing. Now the qBittorrent directory exists (because I made it), but nothing of any kind is being written into it. I'd kill for a log of any kind, anywhere. Just the tiniest of hints.

So … it feels like permissions? What should the directory permissions be? the UID/GID are for my user, the current owner of /data/qBittorrent. Just … nothing happens.

Zitat von chente

This can help you learn if you want.

omv6:docker_in_omv [omv-extras.org]

This is looking a lot better (and more comprehensible) than when I first consulted it a few months ago. Thanks.

Thanks — chente, gderf, BlueCoffee — for all the guidance thus far.

OK, having worked through the entire guide (thanks again, chente) on a parallel install (almost … I'm using an old Asus C320 as the server, so not ARM) — which works just fine — I can now see that my problem has most likely been with the filesystem:

• as BlueCoffee pointed out, I didn't have the best structure in place for config files, etc.
• my permissions were screwed up enough in the /config and /data folders that nothing could start properly or be written to logs.

Note that I haven't confirmed this, as I'll just be shifting things over to the "new" server instead of continuing to fuss with the old one; but I'm pretty certain these were the issues.

Thanks again to everyone who pitched in.