Log in

Bekijk de volledige versie : Transmission - segmentation fault



marco82
14-11-2007, 18:20
Evey time I wanna see info for some torrent I get the segmentation fault.
The core file is (from /opt/torrent/.transmission folder): http://rapidshare.com/files/69705744/core.6989.html

oleo
15-11-2007, 15:13
Evey time I wanna see info for some torrent I get the segmentation fault.
The core file is (from /opt/torrent/.transmission folder): http://rapidshare.com/files/69705744/core.6989.html

This is probably bug in transmission lib not providing nonblocking scrape info any more.

oleo
15-11-2007, 15:14
Evey time I wanna see info for some torrent I get the segmentation fault.
The core file is (from /opt/torrent/.transmission folder): http://rapidshare.com/files/69705744/core.6989.html


I will change this back to libbt.

marco82
15-11-2007, 18:10
OK, let us know when u do that, and also how to fix it.

TNX!

avberk
10-04-2008, 22:31
When i run transmission-daemon like this:
cd /tmp/harddisk/torrent && transmission-daemon -f -p /opt/var/run/transmission.pid -s /etc/transmission.socket

i get a segmentation fault: (was stable with 1.06)

[warn] epoll_create: Function not implemented
[warn] epoll_create: Function not implemented
Transmission 1.11+ (5576) started
Queued for verification
Verifying torrent
Queued for verification
Bound socket 14 to port 51413
Opened port 51413 to listen for incoming peer connections
Verifying torrent
Segmentation fault


I would like to go back to version 1.06.
Can someone please attach this for me?

oleo
11-04-2008, 21:15
solved with http://trac.transmissionbt.com/changeset/5579

avberk
12-04-2008, 11:20
Thanks Oleo,

The 'segment fault' has been resolved!

:)

lale
01-05-2008, 02:43
I`ve just did ipkg update& ipkg upgrade and when I want to start transmission I get this message
"transmissiond: can't load library 'libcurl.so.4'"??

Is there a solution?

al37919
01-05-2008, 06:02
ipkg install -force-reinstall curl

andersos
03-10-2008, 18:13
The last couple of days I get a compile error when trying to cross-compile Transmission trunk. It builds with no problem natively in Debian. Please help!!



natpmp.c:84: warning: no previous prototype for 'sendpendingrequest'
natpmp.c:100: warning: no previous prototype for 'sendnatpmprequest'
natpmp.c:165: warning: no previous prototype for 'readnatpmpresponse'
natpmp.c: In function `sendnewportmappingrequest':
natpmp.c:162: internal compiler error: in arm_print_operand, at config/arm/arm.c:11866
Please submit a full bug report,
with preprocessed source if appropriate.
Send email to arm-gnu@codesourcery.com for instructions.
{standard input}: Assembler messages:
{standard input}:302: Warning: partial line at end of file ignored
make[3]: *** [natpmp.o] Error 1
make[3]: Leaving directory `/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission/third-party/libnatpmp'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission/third-party'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission'
make: *** [/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission/.built] Error 2

Freelancer
04-10-2008, 09:12
Hi, there

I just need to write down my frustrations so I can get over them.
First of all I would like to shout Transmission 1.34 IS A PIECE OF SHIT!
Now after this is over I would like to write down my problems.
First of I was very happy with Transmission 1.22.
But one day my torrents were downloading really slow. I thought maybe my Internet provider is lowering the priority of my torrents or some other people are sabotaging the torrent uploading by uploading bad chunks.
So I figured out that maybe I should upgrade because the new version will have encryption and better security and so on.
I upgraded and remained with my mouth open not from amazement but from being puzzled.
So I started to try around and play and experiment.
Thanks to this thread:
http://wl500g.info/showthread.php?t=15562&highlight=transmission.cgi
I was able to figure out how it works.
I'll continue with the negatives on the next post.

Freelancer
04-10-2008, 09:27
1.
First fucking big problem is that I can not add comment to the torrent. Oh this is real fucking big problem because I am a member of many closed torrent portals and by adding comment to the torrents I was able to see who belongs to who and I was able to keep manageable my stuff.
2.
Second big fucking problem is that transmission 1.22 put the torrents in separate directory's.
For example it put them in a directory of the name of the torrent file.
Now this shit puts them in a directory unleashed mode.
This is bad because the old way I was able to manage the files much better.
3.
Third fucking big problem is that of putting the files into one directory the files will be open to abuse.
I do not know what would happen if you have two torrents with one readme.txt in the root.
Please somebody explain this to me.
4.
It takes to me quite long time to upgrade because of the directory problems.
5.
I can not see the syslog, log. (Log button missing)
6.
I can not get info about the torrent regarding what type
of files contains. (Info button missing)
7.
About button also missing.
8.
There is no fucking Fetch option.
9.
During download does not shows to how many pears I am uploading.
Does not show the ratio in this stage.

In the next post I will write down some tips on how to make a smother upgrade.

Freelancer
04-10-2008, 10:12
This is a quite helpful post regarding how to configure and start the new transmission.
http://wl500g.info/showpost.php?p=108659&postcount=39
this post is good on how to write the rc.unslung correctly:
http://wl500g.info/showpost.php?p=60931&postcount=2

Now here are some other tips.
Watch out for the download and the configuration directory's.
If you decide to start with a new config than do not have this layout:
"/tmp/hardisk/torrent" -here are going the torrents this is download directory.
"/tmp/hardisk/torrent/.config" this is the config dir.
This is bad and pay attention. :-)
Somebody can create a torrent like this:
".config/torrents/infinitecycle.torrent"

The old 1.22 Transmission had the following default configuration.
Well he went for the:
"/tmp/harddisk/torrent" directory as a default.
From here he had the following standard layout:
/.config - for the config.
/source - here you putted your torrents for upload, this was a legacy of the old transmission.
/target - here were the fully downloaded torrents. This was the seeding place. :-)
/work - here were the currently active torrents.
The /.config had the following layout:
/blocklist
/resume
/torrents
Here were the torrent files that he worked.
There was no separation between downloaded or working. only working and resume.
The torrent files were also present in the /target and /work directory's. here was the structure of let's say /target (/work was the same.)
/Name of the torrent file directory/
/Name of the torrent file directory/.info
/Name of the torrent file directory/.status
/Name of the torrent file directory/Name of the torrent file.torrent.seeding
/Name of the torrent file directory/* The torrent data *

This type of directory was more of legacy from the prehistoryk transmission.
The torrent files were present in many places.
First:
.config/resume
.config/torrents
target/Name of the torrent file directory/
work/Name of the torrent file directory/
and they all had different endings.
.resume
.suspended
.seeding
or simply torrent.

Next post the new directory structure of new transmission.

Freelancer
04-10-2008, 10:23
Well the new transmission has two main directory's:
configuration and download.
configuration by default is around:
/tmp/local/root/ ...
This is on the flash so leave it alone and start it as Shouriken said it.
In the configuration directory you will have the same structure as at Transmission 1.22
But in the download directory you will have the torrents unleasd so no special directory's for them or info files or whatever.
This is I think is bad, and what pisses me on that if they correct this in the future I will have to do a lot of work to upgrade and transfer my seeds.

Now I have a lot of upgrading to do so I'll stop.

Freelancer
04-10-2008, 12:41
I just realized why the fuck I was not able to reinstall transmission 1.22.
It is because I installed bash and that fucked the ipkg.
Now I did all the conversions to my config files. I have the old ones backuped, but I am not going to revert. So I'll stay with this shit. Man I am pissed!

Freelancer
08-10-2008, 18:15
Hi, there

Here I am a couple of days later to continue the monologue.
But hey maybe it will help somebody. :-)


1.
First fucking big problem is that I can not add comment to the torrent. Oh this is real fucking big problem because I am a member of many closed torrent portals and by adding comment to the torrents I was able to see who belongs to who and I was able to keep manageable my stuff.

Well I installed on my PC the Windows Remote UI.
From here:
http://users.aber.ac.uk/anf6/projects/transmission/
And that UI shows the trackers and I can sort them there.
Visually I can keep track of them by the tracker.
How ever there is no possibility of the comment which is still bad.
An other thing, for me the Windows Remote UI did not worked and for this I needed to download the source and to correct it and recompile it.
I rewrote the following function:


private void Form1_Resize(object sender, EventArgs e)
{
if (Program.form != null)
{
if (Program.form.NotifyIcon.Visible && FormWindowState.Minimized == this.WindowState)
{
this.Hide();
}
}
}




2.
Second big fucking problem is that transmission 1.22 put the torrents in separate directory's.
For example it put them in a directory of the name of the torrent file.
Now this shit puts them in a directory unleashed mode.
This is bad because the old way I was able to manage the files much better.
3.
Third fucking big problem is that of putting the files into one directory the files will be open to abuse.
I do not know what would happen if you have two torrents with one readme.txt in the root.
Please somebody explain this to me.

Still a problem.



4.
It takes to me quite long time to upgrade because of the directory problems.

Well yeah this was a pain + the recheck.



5.
I can not see the syslog, log. (Log button missing)

Still looking for a solution.



6.
I can not get info about the torrent regarding what type
of files contains. (Info button missing)

This was solved by the Windows Remote UI.
You can see the details here.



7.
About button also missing.
8.
There is no fucking Fetch option.

Still a problem.




9.
During download does not shows to how many pears I am uploading.
Does not show the ratio in this stage.

Well on the Clutch you can see it in the Info panel.
Windows Remote UI also shows it.

And there is a 10 problem:
I can not limit the number of torrents only the upload/download speed.

oleo
09-10-2008, 19:03
If u are dissapointed wint new interface, please open a ticket describing each trouble at http://trac.transmissionbt.com/report

Meanwhile you can use old transmission now called transmissiond as separate package, that can work along new interface.

calebz
17-10-2008, 21:31
Hello

I use Openwrt with transmission. Im so lazy I didnt even make a startup script because it works stable for me.

I didnt even read what you wrote right after the part where you say its a piece of shit and multiple F words.

Really man go f yourself. Its a free peace of software and yes its not perfect but remember some ppl waste time making/trying it work and get your whining as credit.

If you dont like it flash it back to ASUS firmware and kiss Download Master for me.

andersos
27-10-2008, 19:50
I still can't build Transmission :( The natpmp was updated today so I thought I'd give it a try. It still builds ok natively on Debian. Could it be that a newer version of the toolchain is needed?

Now I get this error :



natpmp.c:83: warning: no previous prototype for 'sendpendingrequest'
natpmp.c:99: warning: no previous prototype for 'sendnatpmprequest'
natpmp.c:164: warning: no previous prototype for 'readnatpmpresponse'
natpmp.c: In function `sendnewportmappingrequest':
natpmp.c:161: internal compiler error: in arm_print_operand, at config/arm/arm.c:11866
Please submit a full bug report,
with preprocessed source if appropriate.
Send email to arm-gnu@codesourcery.com for instructions.
{standard input}: Assembler messages:
{standard input}:302: Warning: partial line at end of file ignored
make[3]: *** [natpmp.o] Error 1
make[3]: Leaving directory `/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission/third-party/libnatpmp'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission/third-party'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission'
make: *** [/home/andersos/projects/optware/trunk/cs05q3armel/builds/transmission/.built] Error 2

Kenny
01-11-2008, 00:03
Hi, there

Here I am a couple of days later to continue the monologue.
But hey maybe it will help somebody. :-)


Well I installed on my PC the Windows Remote UI.
From here:
http://users.aber.ac.uk/anf6/projects/transmission/
And that UI shows the trackers and I can sort them there.
Visually I can keep track of them by the tracker.
How ever there is no possibility of the comment which is still bad.
An other thing, for me the Windows Remote UI did not worked and for this I needed to download the source and to correct it and recompile it.
I rewrote the following function:


private void Form1_Resize(object sender, EventArgs e)
{
if (Program.form != null)
{
if (Program.form.NotifyIcon.Visible && FormWindowState.Minimized == this.WindowState)
{
this.Hide();
}
}
}




Could you post your recompiled version of the program?

beatmag
06-11-2008, 09:44
does someone have the transmission 1.22 ipkg files?

i have been unable to find them on the internet =(

beatmag
06-11-2008, 10:02
im trying to build 6228. its not happy about ....


checking pkg-config is at least version 0.9.0... yes
checking for OPENSSL... yes
checking for LIBCURL... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking how to copy va_list... va_copy
configure: invoking libevent's configure script
checking for GTK... no
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for intltool >= 0.23... awk: cannot open ./intltool-update.in (No such file or directory)
awk: cannot open ./intltool-update.in (No such file or directory)
found
./configure: line 24150: test: : integer expression expected
configure: error: Your intltool is too old. You need intltool 0.23 or later.
make: *** [/opt/optware/oleg/builds/transmissiond/.configured] Error 1


also the latest couldn't build either

beatmag
08-11-2008, 07:15
Tranmission 1.22 Built by checking out a older version of unslung, using the latest toolchain but old unslung scripts to build.

Currently not tested yet. I am about to test it soon.

andersos
10-11-2008, 20:59
1.34+ finally built ok for me yesterday after weeks of breaking. But today 1.40 was released - waiting for official optware package :D

gstadler
29-11-2008, 20:20
Hi,

I have tried to compile the newest transmission client (1.40) from source. The 'configure' command wants to find the file 'openssl.pc' which does not exists in the firmware. I thought that this was fixed in transmission 1.40 because I saw the closed tickets for this. I have both the openssl and openssl-dev packages installed.

If anyone has an idea what am i missing, please let me know.

[admin@wlgp transmission-1.40]$ ./configure -q && make -s
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
No package 'openssl' found
configure: error: Cannot locate ssl

Lesiuk
29-11-2008, 21:40
Hi,

I have tried to compile the newest transmission client (1.40) from source. The 'configure' command wants to find the file 'openssl.pc' which does not exists in the firmware. I thought that this was fixed in transmission 1.40 because I saw the closed tickets for this. I have both the openssl and openssl-dev packages installed.

If anyone has an idea what am i missing, please let me know.

[admin@wlgp transmission-1.40]$ ./configure -q && make -s
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
No package 'openssl' found
configure: error: Cannot locate ssl
For me openssl-devel package not works too.
I compiled it from sources and now it works.

gstadler
30-11-2008, 12:20
Did you mean the openssl-dev package works or compiling transmission 1.40 works as well for you?

Lesiuk
30-11-2008, 12:49
Did you mean the openssl-dev package works or compiling transmission 1.40 works as well for you?

Compile it: http://www.openssl.org/source/openssl-0.9.8i.tar.gz
After that compile transmission.

Lesiuk
15-12-2008, 16:21
hi,

newest transmission from repository is not working for me.


[admin@LesiukNET root]$ transmission-daemon
transmission-daemon: can't resolve symbol '__libc_pthread_init'

Somebody know how to fix it?
Transmission 1.40 works OK.

edit: also __libc_* refers to a fullblown libc, not uClibc (afaik)
is that package wrong compiled?

best regards
Damian Lesiuk

wpte
16-12-2008, 09:12
you probably need to do:

ipkg install libpthread

at least... that's what it's asking for I believe

iGz
17-12-2008, 14:55
Hi folks,

After I`ve upgraded from 1.34 and pointed browser to my router with transimission installed, I get only "401: Unauthorized - Unauthorized IP Address" .

I changed nothing in configuration, and only thing that I found about this, is some problem with "auth.backend.htdigest.userfile" file instead "auth.backend.plain.userfile" . I did not find these files on my hdd :(

I`m newbie in linux world, so if you have any hint how to resolve this, or is there somebody who has same problem... :)

BTW : Have somebody older version of transmission (1.3x) ? Because this one worked, and after update I cannot find old version.

Thank you...

Wxm
17-12-2008, 18:48
Hi folks,

After I`ve upgraded from 1.34 and pointed browser to my router with transimission installed, I get only "401: Unauthorized - Unauthorized IP Address" .

I changed nothing in configuration, and only thing that I found about this, is some problem with "auth.backend.htdigest.userfile" file instead "auth.backend.plain.userfile" . I did not find these files on my hdd :(

I`m newbie in linux world, so if you have any hint how to resolve this, or is there somebody who has same problem... :)

BTW : Have somebody older version of transmission (1.3x) ? Because this one worked, and after update I cannot find old version.

Thank you...

Try this (Maybe) In my asus works:D
http://forum.transmissionbt.com/view...php?f=1&t=6659

iGz
17-12-2008, 20:16
Try this (Maybe) In my asus works:D
http://forum.transmissionbt.com/view...php?f=1&t=6659

Thanks, but your url is malformed, so i used search engine on that forum, but nothing there worked and found some others people that have same problem :(

Have anyone older Transmission release than 1.4x ?

Wxm
17-12-2008, 20:37
Thanks, but your url is malformed, so i used search engine on that forum, but nothing there worked and found some others people that have same problem :(

Have anyone older Transmission release than 1.4x ?

This solve your problem
http://www.wl500g.info/showthread.php?t=10307:D

iGz
18-12-2008, 00:02
Funny :p

Total reinstall is to much time consuming for me, so i`m trying to avoid it :D

vleutmans
18-12-2008, 07:33
Hi all,

after upgrading transmission to 1.41b4-1 I had to change the URL to be able to access the GUI again.
I remotely connect to router via SSH.

Before I connected to GUI by http://192.168.1.1:9091
(192.168.1.1 is the local IP of the router itself)

now I connect to http://localhost:9091 and the GUI is there.

As you see I'm not a guru, but it's easy to just try it :-)

Maybe it helps for you.

Regards

Michel

iGz
18-12-2008, 09:36
Thank you, this works with default configuration, but still doesn`t work with additional settings like customed port, user authentication, ip restrictions....

But thanks for hint :)
Seem to new Transmission doesn`t recognise older configuration. :confused:

kaizen
18-12-2008, 10:59
Seem to new Transmission doesn`t recognise older configuration. :confused:

Looks like it creates new config folder in /opt/torrent/.config
How to move it back to harddisk?

It looks likne -g switch stopped working this is not working anymore (http://wl500g.info/showpost.php?p=108370&postcount=30) with new version :(

BalMagnuM
19-12-2008, 23:03
Hi Everyone,

first of all, thanks to oleg, wengi and oleo for the great job!

I just wanted to share, how I got rid of the issue - still partially.
I tryed to follow through wengi's instructions, part 10. transmission, but still got the error, until I figured, you need to explicitly enable the client's IP address from which you want to connect to your box.

From settings.json:
"rpc-whitelist": "your.clients.IP.address",

I've tried to add in a new line, other IP's or hostnames, but the result was the same 401 error message.

Now, this is wonderful, if you only connect to your box from 1 client, but presume some of us would like to see the box from ANYWHERE...

What makes me :confused: is why's there no info on how to put together a config file?

Cheers,
B

BalMagnuM
20-12-2008, 00:11
Hi,

finally back to normal after upgrading to 1.41b4-1 from 1.41b3-something.

Error:
- 401 error message in browser when connecting to the server

Root cause:
- config file may have been ignored or insufficient data in the config file. client's IP address is not added in the rpc-whitelist tag

Solution:
As a basis, I'm using wengi's well written instructions (http://www.wl500g.info/showthread.php?t=10307) with minor changes to personalise settings of transmission (http://www.wl500g.info/showpost.php?p=60933&postcount=4).
Follow the post on transmission through, as we are just going to alter it to use the config file.
You need to set up server starting to take into account only the config file.

vi /opt/etc/init.d/S90transmission-daemon
Change the following line from

/opt/bin/transmission-daemon -g /tmp/harddisk/transmission/config -b -w /tmp/harddisk/transmission/download
to

/opt/bin/transmission-daemon -g /tmp/harddisk/transmission/config
Once that is done, you need only to alter the settings file. If you need to test your settings, you can use the server start|stop options or preferably the command line start and the server stop.

/opt/etc/init.d/S90transmission-daemon start
/opt/etc/init.d/S90transmission-daemon stop

or

/opt/bin/transmission-daemon -g /tmp/harddisk/transmission/config
/opt/etc/init.d/S90transmission-daemon stop

To create your settings file, please read the official site about editing the config file (http://trac.transmissionbt.com/wiki/EditConfigFiles).

Editing the options file, do

vi /tmp/harddisk/transmission/config/settings.json

Example:
don't use a blocklist, setup upload and download limiters, protect the transmission site with a us3r : pazWd5 access, where the server can be accessed from anywhere ("rpc-whitelist": "*.*.*.*")

{
"blocklist-enabled": 0,
"download-dir": "\/tmp\/harddisk\/transmission\/download\/",
"download-limit": 200,
"download-limit-enabled": 1,
"encryption": 1,
"max-peers-global": 200,
"peer-port": 51413,
"pex-enabled": 1,
"port-forwarding-enabled": 0,
"rpc-access-control-list": "+127.0.0.1",
"rpc-authentication-required": 1,
"rpc-password": "us3r",
"rpc-port": 9091,
"rpc-username": "pazWd5",
"rpc-whitelist": "*.*.*.*",
"upload-limit": 50,
"upload-limit-enabled": 1
}


Cheers,
B

wengi
20-12-2008, 13:31
Hi BalMagnuM,

i wondered why my transmission does not accept my settings.json.
Maybe this is because of the other startup options.

Let me test your solution and update the HowTo.

Thank you
wengi

Kenny
22-12-2008, 17:05
"rpc-whitelist": "*.*.*.*",




That did the trick for me, thanks

Wxm
22-12-2008, 17:54
Hi
I`need help.:eek:
I have a problem with transmission.:)
My deamon work good but only about 1h. and crash.
I can`t use putty and log to my asus.:p
Please help me.:eek:

Kenny
27-12-2008, 13:01
Hi, i've this script in /opt/etc/init.d/S57trans
#!/bin/sh


case $1 in
start)
/opt/bin/nice transmission-daemon -g /tmp/mnt/disc0_5/torrent/.config/transmission-daemon
;;
stop)
if [ -n "`pidof transmission-daemon`" ] ; then
echo "stopping transmission-daemon"
killall transmission-daemon
fi
;;
restart)
$0 stop
sleep 5
$0 start
;;
*)
echo "usage: $0 (start|stop)"
exit 1
esac

It does work if i start it manually, but it does not start automatically at boot. Permissions are set correctly (r,w,x). Any suggestions?

alxndrv
27-12-2008, 14:51
Hi! Reinstalled all my software from scratch after formatting hdd. Problems with trasmission: it doesn't create the file "settings.json" and thus doesn't save any settings via web-interface. It only creates 4 dirs: config dir with empty dirs blocklits, resume, torrents. Also it doesn't accept hand-made settings.json. Transmission v 1.42-1

avberk
29-12-2008, 07:40
put this after the first line:

export PATH=/opt/bin:/opt/sbin:$(PATH)

Kenny
29-12-2008, 18:35
working! Thank you very much

lyka
14-01-2009, 23:45
i just added -a *.*.*.* (this means allow all ip)

here:

nano /opt/etc/init.d/S90transmission-daemon (you can use vi instead)
like this:

/opt/bin/transmission-daemon -a *.*.*.* -g /tmp/harddisk/[yourtorrentfolder]

then

/opt/etc/init.d/S90transmission-daemon stop
/opt/etc/init.d/S90transmission-daemon start

gravisrs
18-07-2011, 23:18
without any reason transmission 2.32-1 after my last update just segfaults..

Is it only me or it's common problem ? How to make transmission talks to me (debug mode)?

[ed]
opted 1.9.2.7-d-r2624 fully updated

ok --debug gives nothing, segfaults also without message.