Bekijk de volledige versie : Questions on the use of Transmission
Recently I had a couple of torrents running in Transmission which were stuck at 95-98%. Turned out that it kept redownloading pieces from users, with an error "piece of hash failed". Is there any way to (auto)ban these users? I didn't find any option in the config.
As a result, I tried to suspend/restart the torrents, but they would not restart. I figured that, since I my torrents were suspended anyways, I'd try and update my transmission to version 0.81 (had 0.74 i think). That was a mistake probably, since my active-torrents.txt got deleted. As a result, it won't recognize my working torrents -- it sees the progress at 0.00%, when it was at 95-98%! Is there any way I can salvage my downloads, or do i have to restart from scratch?
What contents does "active-torrents.txt" exactly have?
edit:ugh, getting generic i/o errors with transmission now
The contents is simply list of all active torrents. Each one in its own line.
Upgrade to 0.8x requires freshly start of torrents. There is nothing much to do when you receive failed hash. Sometimes failed hash occurs on many peers. It help if you invite someone with complete torrent to join seeding.
There is .transmission/cache directory where you could erase cache file(s).
Hi!
I got Generic I/O error as soon as one of downloaded files reaches 2GB. My transmission version is 0.82. This is the message from log file:
Sep 12 20:20:37 transmissiond[863]: Fatal error, stopping download (-2147483584)
The file system is:
/dev/discs/disc0/part2 on /opt type ext3 (rw)
Where can be the problem? :confused:
Patrik
You shoud fsck your disk. This can even be done on router with unmounted partition:
killall stupid-ftpd
killall smbd
killall nmbd
umount /dev/disk/...
e2fsck -f -y /dev/disk/...
You shoud fsck your disk. This can even be done on router with unmounted partition:
killall stupid-ftpd
killall smbd
killall nmbd
umount /dev/disk/...
e2fsck -f -y /dev/disk/...
The same error :confused:
[admin@myasus /]$ e2fsck -f -y /dev/discs/disc0/part2
e2fsck 1.38 (30-Jun-2005)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/discs/disc0/part2: 9620/6111232 files (8.5% non-contiguous), 3889836/12209400 blocks
Sep 13 17:45:38 transmissiond[988]: Transmission daemon 0.82 (r) started - http://transmission.m0k.org/
Sep 13 17:45:51 transmissiond[988]: Starting torrent /opt/torrent/work/[BHD]...torrent
Sep 13 20:49:35 transmissiond[988]: Fatal error, stopping download (-2147483584)
Here is the code of your problem. You should check torrent. It is possible that the problem is only with this torrent. Otherwise file a ticket at http://transmission.m0k.org/trac/ explaining the problem.
/* receive/send messages */
tr_torrentWriterLock( tor );
for( i=0; i<tor->peerCount; ) {
tr_peer_t * peer = tor->peers[i];
int ret = tr_peerPulse( peer );
if( ret & TR_ERROR_IO_MASK ) {
tr_err( "Fatal error, stopping download (%d)", ret );
tor->runStatus = TR_RUN_STOPPING;
tor->error = ret;
strlcpy( tor->errorString,
tr_errorString(ret),
sizeof(tor->errorString) );
break;
}
if( ret ) {
tr_peerDestroy( peer );
tor->peerCount--;
memmove( &tor->peers[i], &tor->peers[i+1],
(tor->peerCount-i)*sizeof(void*) );
continue;
}
i++;
}
tr_torrentWriterUnlock( tor );
i seem to be getting the same error when a torrent bigger than 2 gb reaches to 2 gb
Error: Generic I/O error Start: 02 Oct 19:20 uploaded: 2.8 MB
Oct 3 13:20:21 transmissiond[240]: Fatal error, stopping download (-2147483584)
i also use ext3
[admin@(none) etc]$ mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
proc on /proc type proc (rw)
ramfs on /tmp type ramfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/discs/disc0/part2 on /opt type ext3 (rw)
/dev/discs/disc0/part3 on /tmp/harddisk type ext3 (rw,noatime)
and this is the partition where i download the file
/dev/discs/disc0/part3
228G 3.3G 214G 2% /tmp/harddisk
I suggest that you post me torrent file in question to verify for myself the issue.
it gives this error with any torrent that contains a file bigger than 2 gb.
downloading big torrents that contain smaller files is working normally.
i attached a torrent that gives this error...
i installed everything again and it seems that it gives the same error :(:(:(
I've also reproduced your error. Now I am testing past version 0.80-svn (1981) on FreeBSD and that it seems to work. Then I will repeat the same test with 0.82 to see if this is mipsel problem or not.
Ok. Let`s hope that this problem can be fixed easily.
I am joining the topic.. I have the same errors.
Oleo I hope you can help us out! :)
I am planning to do this over weekend. Right now I see that on FreeBSD works. There is a little confusion with latest release not to have transmission-cli but transmisssioncli ? Probably I will go to head and start debugging there.
Any update on the problem?
I have upgraded to latest Transmission daemon 0.82+ (r3376) and it looks like the 2GB problem is solved. There are also other substantial changes like libevent that replaced threading model, encryption, peer banning, ...
But after two days of r3376 testing I am a little suspicious that this libevent is not very effective. On one tracker I am getting Tracker: Error - No response from tracker -- will keep trying. that stops download after while. So if someone is willing to test this and report his finding here I've prepared Oleg ipkg at http://oleo.ath.cx/tmp
I will upgrade optware feeds if positive results will be reported.
Installed this new version. slow file growth stuck at 2139226112 bytes (1.99 Gb)
and then T started download nevertheless.
[admin@router mandriva-linux-2008.0-free-rc2.i586]$ cat /opt/var/log/messages | grep transmissiond
Oct 15 22:03:57 transmissiond[5640]: Transmission daemon 0.82+ (r3376) started - http://transmission.m0k.org/
Oct 15 22:03:59 transmissiond[5640]: Starting torrent /tmp/harddisk/torrent/work/mandriva-linux-2008.0-free-rc2.i586 -'mininova.org'-/mandriva-linux-2008.0-free-rc2.i586 -'mininova.org'-.torrent
Oct 15 22:08:59 transmissiond[5640]: 1192471739 1 dl 70.40 ul 0.00 ld 0.32
Oct 15 22:10:29 transmissiond[5640]: 1192471829 1 dl 54.40 ul 0.00 ld 0.51
Oct 15 22:11:17 transmissiond[5640]: 1192471877 1 dl 50.40 ul 0.00 ld 0.60
Oct 15 22:16:17 transmissiond[5640]: 1192472177 1 dl 48.00 ul 0.00 ld 0.64
Oct 15 22:21:17 transmissiond[5640]: 1192472477 1 dl 52.00 ul 0.00 ld 0.58
Oct 15 22:22:56 transmissiond[5640]: 1192472576 1 dl 32.80 ul 0.00 ld 0.50
Oct 15 22:27:56 transmissiond[5640]: Tracker: Error - Tracker error 3
Oct 15 22:27:56 transmissiond[5640]: 1192472876 1 dl 49.60 ul 0.00 ld 0.59
Oct 15 22:28:17 transmissiond[5640]: 1192472897 1 dl 43.20 ul 0.00 ld 0.68
Oct 15 22:33:17 transmissiond[5640]: 1192473197 1 dl 49.60 ul 0.00 ld 0.69
It seems that Transmission 0.90 has been released. Can you update the optware feeds with this new version ?
Can't remove active torrent. Says
Can only remove suspended torrents! Edit transmission.conf to FORCE_REMOVE.
I uncommented this value in transmission.conf and restarted router, but it still doesn't work and keeps saying the same.
Why's that?
Can't remove active torrent. Says
I uncommented this value in transmission.conf and restarted router, but it still doesn't work and keeps saying the same.
Why's that?
Please read back, it is a documented feature. You can remove only suspended torrents.
Please read back, it is a documented feature. You can remove only suspended torrents.
I've read docs. I thought that it normaly can remove only suspended and with option on it can do it even without it. My bad ^_^
Can't remove active torrent. Says
I uncommented this value in transmission.conf and restarted router, but it still doesn't work and keeps saying the same.
Why's that?
Due to some mistakes this FORCE remove should be "YES" and not "yes" to work. So If you have troubles with that, just change the case.
I have upgraded to latest Transmission daemon 0.82+ (r3376) and it looks like the 2GB problem is solved. There are also other substantial changes like libevent that replaced threading model, encryption, peer banning, ...
But after two days of r3376 testing I am a little suspicious that this libevent is not very effective. On one tracker I am getting Tracker: Error - No response from tracker -- will keep trying. that stops download after while. So if someone is willing to test this and report his finding here I've prepared Oleg ipkg at http://oleo.ath.cx/tmp
I will upgrade optware feeds if positive results will be reported.
this work with OpenWrt and X-wrt?
I use latest Transmission 0.82-3 package from /optware/ddwrt/cross/stable and the same problem files above 2GB (generic I/O error). My safe try it?
Transmission 0.9 does not solve 2GB limit. But it works after two days of testing. I will commit this version in a day or two and then seek for the 2GB bug.
This bug may be uclibc related and all firmwares (X-wrt, OpenWrt, dd-wrt, Oleg, ... ) are affected!
I've just setup my wl500gp according to wengis tutorial. Everything seems to work smoothly except that:
Using transmission daemon-
torrents freeze (dl only) after some time (can be after 10mins or 2hours). Everything else is still functional. Except, in a few instances, I could no longer access the web interface.
The folder .../torrents/work becomes inaccessible, i.e. can't do ls or touch
I throttled the upload since otherwise I can't access my network folders using samba2.
tj_spark
31-10-2007, 09:36
The folder .../torrents/work becomes inaccessible, i.e. can't do ls or touch
I had the same problem.
It was triggered because the 3rd partition (which is an ext3 type and mounted to /tmp/harddisk like the tut says) was eventually automounted by the router as a vfat type partition to /tmp/harddisk.
At first I thought I had fixed the problem by doing an "umount /tmp/harddisk" before the actual "mount /tmp/harddisk" in my post-mount script.
But after some time the router does the above mentioned automount as vfat again :-(
The problem vanished after I removed a specific nvram setting by unset'ing it.
Try the following on a console as one command:
nvram show | grep -i usb | grep "/tmp/harddisk"
There should be an entry like:
usb_disc0_...=/tmp/harddrive
Then unset this entry:
nvram unset usb_disc0_...
(the points are not part of the name you must write down everything before the "=" sign from the "nvram show" output)
Then you have to save the settings before rebooting:
nvram save
I hope this helps you fix the problem.
TJ
thanks for the prompt reply, however, unfortunately this doesn't seem to be the problem.
>> nvram show | grep -i usb | grep "/tmp/harddisk"
size: 13585 bytes (19183 left)
i.e., there is no entry "/tmp/harddisk", further
>> nvram show | grep -i usb | grep "usb_disc0"
size: 13585 bytes (19183 left)
usb_disc0_port=0
usb_disc0_index=0
usb_disc0_fs_path0=
usb_disc0_fs_path1=
usb_disc0_fs_path2=
usb_disc0_fs_path3=
usb_disc0_fs_path4=
usb_disc0_fs_path5=
usb_disc0_fs_path6=
usb_disc0_dev=
usb_disc0_path0=
usb_disc0_path1=
usb_disc0_path2=
usb_disc0_path3=
usb_disc0_path4=
usb_disc0_path5=
usb_disc0_path6=
Looking at the log, one becomes very suspicious of:
GET unknown message '20'
What exactly is this and how do I prevent it from freezing up my torrents as well as not being able to access .../torrent/work?
This problem occurs only when downloading, not when seeding.
see attached: problem_log.png
I suspect problem with disk with such report. Please umount your disk and do
e2fsck -f -y /dev/disk/... on your partitions. If this does not help and you see
SCSI errors when you type /bin/dmesg when system freezes than connect USB disk to the PC with linux and do w2fsck there.
YES!
e2fsck -f -y /dev/discs/disc0/...
did the trick.
It's been working very nicely so far, nice!
And thanks for the help :D
It seems that Transmission 0.91 has also been released. Can you please update the optware feeds with this version ?
Hi all,
I was wondering whether it is possible to set dl/up limit not only globally but also for each torrent. Does anybody know?
I guess transmission just lost it's last advantage against rtorrent: web interface
http://libtorrent.rakshasa.no/wiki/RTorrentXMLRPCGuide
http://canbruixa.homelinux.net/wt/
I guess transmission just lost it's last advantage against rtorrent: web interface
http://libtorrent.rakshasa.no/wiki/RTorrentXMLRPCGuide
http://canbruixa.homelinux.net/wt/
This is just specification. There is no real web interface as I see. And nobody really want to run PHP for web interface on routers.
Besides transmissiond there is also transmission-daemon and transmission-client that uses RPC, but nobody really wrote WWW interface for them.
Hi all,
I have some problems with transmision:
1. transmision don't places the torrent file automatically from queue to active files.
2. It cannot be more than 1 active file, though in config Max_active files=5.
Great thanks for help...looking forward for any reply.
1. you need to call /opt/sbin/transmission_watchdog from cron every hour or so
2. you can always use push to add more torrents
Bobanovicz
07-12-2007, 19:51
Any news about 2GB bug?
it seems that it had been solved with the newer versions of transmission
I just did ipkg upgrade.
After watchdog button it says:
/opt/sbin/transmission_watchdog: /opt/sbin/transmission_watchdog: 304: transmissiond: not found
Am I making mistake or...?
Regards.
Its no mistake. Seems that bzhou missed my daemon code when upgraded with http://trac.nslu2-linux.org/optware/changeset/7468
I hope that I will correct this ASAP.
Regards!
Chgset #7470 (http://trac.nslu2-linux.org/optware/changeset/7470) corrected transmissiond inclusion and upgraded to latest SVN.
Please report any problems here.
Hi Oleg,
Removed the package
Ipkg remove transmission
Than installed again
Ipkg install transmission
Still have the same error message :(
PLZ HEEEELP!
don't forget before install transmission:
ipkg update
It is working indeed!;)
THX catmat!
I like transmission 0.96. Many bugs have been solved out
Due to late transmission bugs I started to look for an alternative torrent client for my router. As I’m Linux dumbass who learned basics this year (embarrassed to confess that it took me three months to figure out complete Optware, Samba and transmission successful install, albeit on the dd-wrt firmware with not so great tutorials as found here) I rely on experienced guys knowledge.
So I tried this great mancub’s tutorial. But for the dd-wrt firmware, there are some syntax differences I don’t know how to solve.
If you don’t have success with new love what to do? Return to the first one of course.
As our guru oleo mentioned, there is full feature transmission deamon but with no RPC interface. For some time I’m eyeing The Clutch project. Looks to me as fine web UI to fully featured transmission (or maybe I’m wrong). So I decided to fire up and try. Installed lighttpd, downloaded and unpacked clutch to the lighttpd directory and tried http:// routerip:8081. I got UI interface:
http://img227.imageshack.us/img227/1246/screen1ya1.jpg
Of course, with no deamon to connect to. But with access to configuration (and nice looking too):
http://img172.imageshack.us/img172/7088/screen2cu2.jpg
I wonder are we only one step away from better transmission interface? What we need is proper transmission deamon and therefore I ask you experienced users to give a try and compile or find proper one to connect to.
Oh, and happy new year to everyone.
Ups,
Didn't properly insert some links:
http://trac.recurser.com/transmission/wiki/About
All I could tell from quick look at Clutch is that using such www client uses many resources on router were you must balance mem/cpu/disk usage. And even using PHP from my point of view is too much. It would be better to have desktop client (GTK+) and just daemon on router for those that can't resist to pretty icons. Lacking any batch processing?
Trailblazer
29-12-2007, 06:13
I finally got the linux cobwebs to clear enough and I got a working Oleg/Transmission install going on my Premium. I really like Transmission. Easy and quick and low mem. Thanks Oleo!!! This is exactly what I bought this router for! :D
I have one annoying error, but can live with it if not easy to fix. I'm wondering if it is a permissions problem in the www area that it's trying to create the .png file in. Anyway, here it is:
Creating graph...
/opt/bin/gnuplot: can't load library 'libiconv.so.2'
I've searched all over and not found anything about this. Everything works fine, I just don't get a graph on the Log page. Anyone got ideas?
Once DD-WRT 24 final comes out, I would really like to get this working on that firmware. Is there a way to image everything on the router? (my working Oleg) if I fail with DD-WRT?
oleo,
I'm aware that controlling transmission through cgi script is the most efficient and rational way. Thank you for making this possible. I'm not attracted to the Clutch by fancy appearance (though it looks nice) but by expectation to get full access to the transmission configuration and controll. Whether the resources penalty for the router will be too big I can't tell. For sure you can better estimate that than me.
Anyway, looking to the Clutch files reveals several JavaScript files with transmission.js being only 46 KB. Seems that this concept is similar to the rtorrent/Ntorrent solution with difference that Ntorrent java client is on the desktop and doesn't consume router resources.
I think that this solution deserves to be taken into the consideration and tested. Only then will we know for sure.
Hi! Is it possible to select files from the torrent to download (not to download them all) thru the transmission.cgi script? Transmission later than 0.80 is supposed to support this feature.
Transmission library provides such feature, but my daemon does not!
Creating graph...
/opt/bin/gnuplot: can't load library 'libiconv.so.2'
Try to install iconv. DD-WRT should work fine with Transmission :)
Trailblazer
03-01-2008, 00:05
Try to install iconv. DD-WRT should work fine with Transmission :)
Thanks for your suggestion. There is no iconv or libiconv in the ipkg respository. I looked one up on the web and found one here:
http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.11.tar.gz
That is 4+MB. Surely there is a watered down version for use with Transmission.
Anyway, I'll be trying it with dd-wrt when they come out with a final for v24.
Thanks again for a great program, oleo!