qBittorrent icon indicating copy to clipboard operation
qBittorrent copied to clipboard

Published 20 hours ago • verified publisher icon qbittorrent

Docker: container restarting due to `Catching signal: SIGTERM`

Open RNGIllSkillz opened this issue 1 year ago • 9 comments

qBittorrent & operating system versions

4.6.0_1.1.1 TrueNas scale

What is the problem?

Constantelly see "Catching signal: SIGTERM" in my logs and container restarting by its own

Steps to reproduce

idk if its relevent but i have around 350k of torrents problem usually happent when I access qbittorrent via api, stopping torrents that cant recieve metadata

Additional context

No response

Log(s) & preferences file(s)

023-10-30 01:10:52.236631+00:00(N) 2023-10-30T01:10:52 - Restored torrent. Torrent: "80351ceb31b817d67f736cac96e9483f814789eb" 2023-10-30 01:10:52.243223+00:00(N) 2023-10-30T01:10:52 - Restored torrent. Torrent: "320eb319de9952ab9584e690683ac80f6a565be7" 2023-10-30 01:10:52.256415+00:00(N) 2023-10-30T01:10:52 - Restored torrent. Torrent: "6c63f3cb273514d3680495d795d0f18292b32c5c" 2023-10-30 01:10:52.257600+00:00Catching signal: SIGTERM 2023-10-30 01:10:52.257621+00:00Exiting cleanly 2023-10-30 01:10:52.257609+00:00(N) 2023-10-30T01:10:52 - qBittorrent termination initiated

2023-10-31 1:43:14 Startup probe failed: Get "http://172.16.0.92:30000/": dial tcp 172.16.0.92:30000: connect: connection refused 2023-10-30 20:44:09 Readiness probe failed: Get "http://172.16.0.92:30000/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 2023-10-30 20:44:09 Liveness probe failed: Get "http://172.16.0.92:30000/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

RNGIllSkillz avatar Oct 29 '23 02:10 RNGIllSkillz

Were you ever able to fix it? I am currently having similar problems.

arthurmelton avatar May 04 '24 11:05 arthurmelton

nope. end up using multiple containers

RNGIllSkillz avatar May 04 '24 14:05 RNGIllSkillz

Problem still persists, maybe a mod is the issue?

Numbernaut avatar May 27 '24 22:05 Numbernaut

Same thing here, it's driving me absolutely crazy...

huntyh avatar Jun 17 '24 19:06 huntyh

I fixed the problem for me, I was getting OOM errors. If you are using something that is limiting the ram that the docker container is able to consume, try increasing that number.

arthurmelton avatar Jun 19 '24 21:06 arthurmelton

Same problem here, adding a "restart: unless-stopped" for now.

dreamfalcon avatar Jun 24 '24 08:06 dreamfalcon

Same problem here, adding a "restart: unless-stopped" for now.

Complete n00b here, but I am having the same problem. Where do you put the "restart: unless-stopped"?

traiannicolau avatar Aug 11 '24 13:08 traiannicolau

Same problem here, adding a "restart: unless-stopped" for now.

Complete n00b here, but I am having the same problem. Where do you put the "restart: unless-stopped"?

In the composer file or using portainer.

dreamfalcon avatar Aug 12 '24 08:08 dreamfalcon