Hi everyone!
Ever since I updated to version 188, Transmission has been crashing. When I start it, it varies after how long it crashes.
This is what is in the log file when I start the transmission:
[root@wrouter ~]# grep transmission /var/log/messages
Sep 19 20:43:54 wrouter sudo: root : TTY=pts/0 ; PWD=/root ; USER=whaskes ; COMMAND=/usr/bin/transmission-daemon -g /etc/transmission
I don’t run it as root, so far there were no problems with it, everything worked until the update.
The Transmission log shows:
[root@wrouter ~]# cat /var/ADAT/transmission2/transmission.log
[2024-09-20 10:11:08.174] inf session.cc:646 Transmission version 4.0.5 (a6fe2a64aa) starting (session.cc:646)
[2024-09-20 10:11:08.174] inf session.cc:404 Listening to incoming peer connections on [0.0.0.0]:6969 (session.cc:404)
[2024-09-20 10:11:08.174] inf session.cc:404 Listening to incoming peer connections on [::]:6969 (session.cc:404)
[2024-09-20 10:11:08.174] inf port-forwarding.cc:215 State changed from 'Not forwarded' to 'Starting' (port-forwarding.cc:215)
[2024-09-20 10:11:08.174] inf tr-udp.cc:168 Bound UDP IPv4 address [0.0.0.0]:6969 (tr-udp.cc:168)
[2024-09-20 10:11:08.174] inf tr-udp.cc:202 Bound UDP IPv6 address [::]:6969 (tr-udp.cc:202)
[2024-09-20 10:11:08.174] inf session-alt-speeds.cc:91 Time to turn on turtle mode (session-alt-speeds.cc:91)
[2024-09-20 10:11:08.174] inf rpc-server.cc:763 Added '127.0.0.1' to host whitelist (rpc-server.cc:763)
[2024-09-20 10:11:08.174] inf rpc-server.cc:907 Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (rpc-server.cc:907)
[2024-09-20 10:11:08.174] inf rpc-server.cc:713 Listening for RPC and Web requests on '0.0.0.0:9091' (rpc-server.cc:713)
[2024-09-20 10:11:08.174] inf rpc-server.cc:917 Password required (rpc-server.cc:917)
[2024-09-20 10:11:08.174] inf rpc-server.cc:923 Serving RPC and Web requests from '/usr/share/transmission/public_html' (rpc-server.cc:923)
[2024-09-20 10:11:08.174] inf daemon.cc:715 Loading settings from '/etc/transmission' (daemon.cc:715)
[2024-09-20 10:11:08.174] inf daemon.cc:751 Requiring authentication (daemon.cc:751)
[2024-09-20 10:11:08.174] WRN torrent-metainfo.cc:271 unexpected: path '[][creation files]', int '1872281' (torrent-metainfo.cc:271)
[2024-09-20 10:11:08.174] WRN torrent-metainfo.cc:271 unexpected: path '[][creation files]', int '137805' (torrent-metainfo.cc:271)
[2024-09-20 10:11:08.174] inf session.cc:1406 Loaded 105 torrents (session.cc:1406)
[2024-09-20 10:11:11.174] WRN Cserkészkézikönyv zombiapokalipszis esetére 2160p at t.ncore.sh:2710 Couldn't parse scrape response: Malformed benc? Unable to parse string (84) (announcer-http.cc:657)
[2024-09-20 10:11:11.174] WRN Hansel.and.Gretel.Witch.Hunters.2013.1080p.UNRATED.READ.NFO.BluRay.ENGx264.HuN-TRiNiTY at t.ncore.sh:2710 Couldn't parse scrape response: Malformed benc? Unable to parse string (84) (announcer-http.cc:657)
[2024-09-20 10:13:15.175] inf port-forwarding.cc:215 State changed from 'Starting' to '???' (port-forwarding.cc:215)
[2024-09-20 10:15:03.175] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1345:d300:6846:ff10:8b28:3e5]:44622: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:03.175] WRN tr-udp.cc:261 Couldn't send to [2a01:36d:116:823:4a65:6a50:d9ec:c2e]:59389: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:03.175] WRN tr-udp.cc:261 Couldn't send to [2a01:5d0:8572:3f00::2f6d]:38382: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:03.175] WRN tr-udp.cc:261 Couldn't send to [2001:4c4d:10e0:2300:e3a1:e641:fe9e:e17b]:30500: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4d:1010:c900:d64f:75d9:7945:24ae]:34529: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1337:1c00:2864:b09d:da07:2]:32064: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4c:1adf:7300::1004]:12556: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2a02:ab88:6c01:9c00::e0ad]:20178: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2001:0:284a:364:38ff:3409:3e1d:1c9e]:44327: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2a01:36d:3500:205e:f9e5:f85a:6f33:6ea4]:51994: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:04.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:2bc1:bb00:79d5:b627:8dbf:d35a]:33184: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2a01:36d:2700:26b7:de68:6ee1:4c79:1867]:42099: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:2c0a:5a00:d661:ca48:8e81:6ec7]:17635: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2a01:36d:2700:2742:47cd:f739:44e2:d173]:42099: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1349:ba00:83c8:1005:2ccf:13bd]:44622: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1549:5300:c8b5:4a5b:1b8b:b36]:64819: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1324:f200:572:84d9:1b08:55b1]:42235: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1334:300:aacf:f2af:5727:8573]:32064: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:05.185] WRN tr-udp.cc:261 Couldn't send to [2a01:5d0:8567:e500::e5b4]:38382: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:06.177] WRN tr-udp.cc:261 Couldn't send to [2a02:ab88:2a00:e280::9836]:50878: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:06.177] WRN tr-udp.cc:261 Couldn't send to [2a02:ab88:150c:2a80::5ec8]:58611: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:06.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1481:f800:463e:a0fb:1cb6:d513]:37254: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:06.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:2386:ce00:1f2a:5c10:2efd:fd48]:52645: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:06.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1ace:d600:d7c4:cc4:fb05:8e78]:59195: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:2105:6c00:2c28:888b:dd9d:b1e0]:37982: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1345:d300:6846:ff10:8b28:3e5]:44622: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4d:1010:c900:d64f:75d9:7945:24ae]:34529: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Couldn't send to [2a01:5d0:8572:3f00::2f6d]:38382: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Couldn't send to [2a01:36d:116:823:4a65:6a50:d9ec:c2e]:59389: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Couldn't send to [2001:4c4e:1337:1c00:2864:b09d:da07:2]:32064: 99 (Cannot assign requested address) (tr-udp.cc:261)
[2024-09-20 10:15:07.177] WRN tr-udp.cc:261 Too many messages like this! I won't log this message anymore this session. (tr-udp.cc:261)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 67 to 2001:4c4e:1345:d300:6846:ff10:8b28:3e5:44622: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 67 to 2001:4c4d:1010:c900:d64f:75d9:7945:24ae:34529: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 67 to 2a01:5d0:8572:3f00::2f6d:38382: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 67 to 2a01:36d:116:823:4a65:6a50:d9ec:c2e:59389: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 69 to 2001:4c4e:1337:1c00:2864:b09d:da07:2:32064: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 69 to 2001:4c4d:10e0:2300:e3a1:e641:fe9e:e17b:30500: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 70 to 2a02:ab88:6c01:9c00::e0ad:20178: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:25.176] WRN net.cc:245 Couldn't connect socket 70 to 2001:4c4c:1adf:7300::1004:12556: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:26.179] WRN net.cc:245 Couldn't connect socket 69 to 2a01:36d:3500:205e:f9e5:f85a:6f33:6ea4:51994: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:26.179] WRN net.cc:245 Couldn't connect socket 69 to 2001:0:284a:364:38ff:3409:3e1d:1c9e:44327: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:26.179] WRN net.cc:245 Couldn't connect socket 70 to 2001:4c4e:2bc1:bb00:79d5:b627:8dbf:d35a:33184: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:26.179] WRN net.cc:245 Couldn't connect socket 70 to 2a01:36d:2700:26b7:de68:6ee1:4c79:1867:42099: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:26.179] WRN net.cc:245 Couldn't connect socket 73 to 2a01:36d:2700:2742:47cd:f739:44e2:d173:42099: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:26.179] WRN net.cc:245 Couldn't connect socket 73 to 2001:4c4e:2c0a:5a00:d661:ca48:8e81:6ec7:17635: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:27.186] WRN net.cc:245 Couldn't connect socket 55 to 2001:4c4e:1324:f200:572:84d9:1b08:55b1:42235: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:27.186] WRN net.cc:245 Couldn't connect socket 55 to 2a01:5d0:8567:e500::e5b4:38382: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:27.186] WRN net.cc:245 Couldn't connect socket 55 to 2001:4c4e:1349:ba00:83c8:1005:2ccf:13bd:44622: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:27.186] WRN net.cc:245 Couldn't connect socket 55 to 2001:4c4e:1334:300:aacf:f2af:5727:8573:32064: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:27.186] WRN net.cc:245 Couldn't connect socket 55 to 2001:4c4e:1549:5300:c8b5:4a5b:1b8b:b36:64819: Cannot assign requested address (99) (net.cc:245)
[2024-09-20 10:15:27.186] WRN net.cc:245 Couldn't connect socket 25 to 2a02:ab88:2a00:e280::9836:50878: Cannot assign requested address (99) (net.cc:245)
That’s all he writes, from startup to crash. I can’t find any posts related to this anywhere else…
How long typically is it after starting, that transmission stops for you. A transmission user from the developers has not seen any problem with transmission after it has run for three days on CU188.
Does it crash when you do a specific torrent download or when doing nothing with it.
The shortest time was about 1 minute, the longest was less than 10 minutes until the crash.
Even if I just start it, it crashes. I can do anything without problems as long as it goes, add, delete, etc.
Previously, I ran more than 200 torrents, and it handled that without any problems. I have the problem now since the update.
I just tried it and it appeared that even if I add a torrent, it doesn’t start downloading, it just appears in the list and waits. With the other torrents, the uploading starts almost as soon as I start the transmission
These two lines indicate that two torrents are not able to parse correctly, due to a malformation in part of the torrent, and are probably causing transmission to crash.
Maybe try to disable those two torrents or remove them from the list temporarily and then see if transmission runs without crashing.
I’m over it. I already took these out. However, these two have been on the list for weeks or months. I’m about to try removing all the torrents and leaving only the one I want to download now.
It’s not working…
Transmission has not changed in IPFire. It is still version 4.0.5, so the only thing That I can think of regarding the failure with the torrent is that they have changed something that no longer works with that version of transmission.
Unfortunately we cannot update to the latest version, 4.0.6, as it fails to build due to a bug, for which they plan to implement a bug fix in version 4.0.7 but that is not yet available.
It looks like I should be able to do an update to version 4.0.6 using a patch from the Arch Linux transmission build.
So that is with one torrent in the list. If you have no torrents does transmission still crash.
The problem is that we have not been able to reproduce that with our systems for the devs having transmission installed. So we need to understand the specific conditions that trigger your crash.
Unfortunately, I can only provide so many logs… Maybe I can install an older version manually on ipfire? If so, where can I download the older transmission version?
The current version 4.0.5 has been the current version since Core Update 184. The old versions of addon are not available to load. The addon server only has the current version available.
I also doubt that going to version 4.0.4 will fix things as nothing has changed in Transmission in IPFire since January 2024 so it must be a change in the torrent format.
You will need to use a newer version of Transmission and you could always build this yourself with the Build AddOns page in the Development section of the wiki but you would also have to overcome the bug issue using the patch from Arch Linux to make the build process for version 4.0.6 work successfully.
As I already indicated we have a dev user that has updated to CU188 with transmission running and it has been going without issues for 3 days so there has to be an additional something on your system that is causing this issue and that may also give a problem with an older or newer version.
Ok, I’ll do the latest transmission tomorrow. I’ll write if it’s good, or if not. 
Hi everyone,
I have the same problem here: After Core-Update 188 Transmission stopped working.
I can restart it (both from ipfire webinterface/status/services as well as from bash /etc/init.d/transmission start).
After I start it, it stops after some time. Shortest time was less than a minute (I’d say couple of secs but not sure), longest was several minutes (maybe 10 min?).
I Could finish a previously started torrent (although it contained errors in the end) and I could also add completely download a new torrent (some 300 MB). I do not see a pattern in the crashes.
I did not find any transmission log and I wonder how I could activate that or how I could help you guys otherwise.
Really appreciate your work, thanks a lot.
PS: previously it worked for more than 3 years withou any problems
PPS: I’m willing to help 
Hallo @raudi
Welcome to the IPFire community.
It looks like there is no entry in the System Logs that has been created for Transmission, so you need to go to the command line and run the following command after having run transmission and having it crash.
less /var/log/messages | grep transmission
and hopefully this will show some info on why it is crashing.
it won’t show anything…
If you want a log, start the transmission like this:
sudo -u whaskes transmission-daemon -g /etc/transmission -e /var/ADAT/transmission2/transmission.log -log-debug
edit /etc/init.d/transmission.
I stopped all torrents, deleted the downloads. There are 105 seed torrents in there, stopped. That’s how Transmission didn’t crash. I started them one by one, currently I am seeding 4 pcs. 5 or more will crash. I will write in the morning to see if he made it through the evening.
What may have appeared is that, as I recall, Transmission used ~1.5 GB or more of memory, which I had no problem with (the system can work with 32 GB of memory). Now it works with 30 mb of memory, not much more even if I start the 105 torrents. I can watch this until I collapse.
It still crashes when I run some torrents, but much later.
Other, non IPFire users, have reported the same crash issue into the transmission issues page on github some time back and it has been identified that version 8.9.1 of curl, which was installed into CU188, is causing a sigpipe failure, a regression from previous version of curl, and this is causing transmission to crash.
https://github.com/transmission/transmission/issues/7035
The fix has been applied by curl to version 8.10.0
I will submit a patch to update curl to the latest version and this will be merged into master to be part of CU189.
EDIT:
I have just realised that I had already submitted a patch submission for the update of curl to 8.10.0 and this had been merged into next which would have been CU190.
We have now just merged this into master so it will become part of CU189.
If I switch the Repository to Testing, then Release 188 → 189 will already appear there. Can this work or should I not experiment on a production system? When will the update come out?
I would wait a couple of days. We have just put a lot of changes into CU189.
It got released quicker than i expected. So you can now update to the CU189 Testing which has the updated curl package.
If you test with the CU189 Testing, please confirm that it solves the crash issue you were experiencing.