[GH-ISSUE #3636] transmission-daemon fills log with error #2289

New issue

Closed

opened 2026-05-05 08:58:40 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 08:58:40 -06:00

Owner

Originally created by @solsticedhiver on GitHub (Sep 20, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3636

I had a perfectly fine transmission-daemon setup running on a rpi3 (using archlinux-arm)

I changed it to use firejail with transmission-daemon. Then, transmission-daemon began to fill the system log with errors like:

Sep 20 01:10:06 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 237 nodes): Success (tr-dht.c:737)
Sep 20 01:10:12 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 237 nodes): Success (tr-dht.c:737)
Sep 20 01:10:21 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Operation now in progress (tr-dht.c:737)
Sep 20 01:10:26 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Resource temporarily unavailable (tr-dht.c:737)
Sep 20 01:10:34 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Success (tr-dht.c:737)
Sep 20 01:10:40 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Operation now in progress (tr-dht.c:737)
Sep 20 01:10:48 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 240 nodes): Success (tr-dht.c:737)

transmission-daemon seems to work fine but I am not an expert. I guess the error messages are not without reason.

Nonetheless, I fixed the log filling issue by adding packet to the list of protocol in a .local override file like:

protocol unix,inet,inet6,packet

Originally created by @solsticedhiver on GitHub (Sep 20, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3636 I had a perfectly fine *transmission-daemon* setup running on a *rpi3* (using *archlinux-arm*) I changed it to use firejail with transmission-daemon. Then, transmission-daemon began to fill the system log with errors like: ``` Sep 20 01:10:06 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 237 nodes): Success (tr-dht.c:737) Sep 20 01:10:12 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 237 nodes): Success (tr-dht.c:737) Sep 20 01:10:21 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Operation now in progress (tr-dht.c:737) Sep 20 01:10:26 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Resource temporarily unavailable (tr-dht.c:737) Sep 20 01:10:34 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Success (tr-dht.c:737) Sep 20 01:10:40 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 239 nodes): Operation now in progress (tr-dht.c:737) Sep 20 01:10:48 tarvos transmission-daemon[30237]: Some torrent name here IPv4 DHT announce failed (firewalled, 240 nodes): Success (tr-dht.c:737) ``` *transmission-daemon* seems to work fine but I am not an expert. I guess the error messages are not without reason. Nonetheless, I fixed the log filling issue by adding `packet` to the list of protocol in a `.local` **override** file like: protocol unix,inet,inet6,packet

gitea-mirror closed this issue

2026-05-05 08:58:41 -06:00

gitea-mirror commented

2026-05-05 08:58:43 -06:00

Author

Owner

@rusty-snake commented on GitHub (Sep 22, 2020):

packet is a quite power full socket. As long as nothing is broken, I'm not happy adding it. My question is: Is nothing broken? DHT is one way to get other peers, are there less peers in use if started w/o packet? DHT is also used announce you as a peer.

@rusty-snake commented on GitHub (Sep 22, 2020): `packet` is a quite power full socket. As long as nothing is broken, I'm not happy adding it. My question is: **Is** nothing broken? DHT is one way to get other peers, are there less peers in use if started w/o packet? DHT is also used _announce_ you as a peer.

gitea-mirror commented

2026-05-05 08:58:44 -06:00

Author

Owner

@solsticedhiver commented on GitHub (Sep 22, 2020):

I am not an expert either with firejail. May be there is a less permissive fix to that ?

@solsticedhiver commented on GitHub (Sep 22, 2020): I am not an expert either with firejail. May be there is a less permissive fix to that ?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2289

No description provided.

Rows
Columns