High CPU usage about docker-transmission-openvpn

[SpiralBrad]

My container is once again behaving as well. Very strange.

[auanasgheps]

Glances shows that most of the activity is done by Transmission itself and not OpenVPN:

But there's nothing really being done.
Maybe this issue is unrelated to the container and I should ask to the Transmission project, but I wanted to get your feedback first.

[ilike2burnthing]

Do you have the same problem on the dev branch?

[auanasgheps]

Just tried with the dev branch, and yes:

[SpiralBrad]

Having a similar problem, also only as of the past week or so; also seeing high disk activity when this happens.

[auanasgheps]

I'm guessing this is not a problem specific to this container but to Transmission, but I'm waiting for a confirmation.

[ilike2burnthing]

Provide the response to uname -a on your host device.

Have you tried a normal Transmission container with a few Ubuntu iso torrents, see if you get the same issue?

Have you tried earlier images? https://hub.docker.com/r/haugene/transmission-openvpn/tags (as well as the earlier version number images, also try the focal and kinetic images)

[auanasgheps]

I still haven't tried a normal Transmission container, but I would like to understate that this behaviour is seen when there is NO torrent activity. I would not complain about 15% CPU load when downloading (actually is pretty good).

BTW this is the output
Linux nas 6.1.0-0.deb11.13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1~bpo11+1 (2023-10-08) x86_64 GNU/Linux
(It's OpenMediaVault 6)

[ilike2burnthing]

Oh sorry, I meant a few Ubuntu iso torrents downloaded, seeding but idle, to semi-replicate your current container.

[auanasgheps]

I haven't done anything, but CPU usage is now at about 5%. I'll keep you posted when I can do more testing

[ilike2burnthing]

It was just having a little hissy fit, it's over it now ;)

[auanasgheps]

I'll monitor the usage for a couple of days. If nothing changes, I'll close this.

[auanasgheps]

This can be closed. I've monitored resources consumption, and the issue did not show up again. I hope it's the same for you!