Hi all,
I use transmission-remote on cygwin frequently to control my transmission-deamon running on headless linux server. I downloaded nightly sources from transmissionbt.com and compile it on cygwin. With last a few releases after 2.33, I've noticed some wrong status info and garbage like ...
Search found 8 matches
- Sat Aug 06, 2011 2:31 am
- Forum: General
- Topic: Garbase in transmission-remote screen
- Replies: 1
- Views: 1721
- Tue Aug 02, 2011 10:57 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
Re: RPC can't bind
I am recompiling all depends again to see what happens. I installed Development Tools from http://homepage.ntlworld.com/itimpi/opentera.htm some tools are quite old.
Before recompiling dependable libraries, I used to get pre-compiled optware via ipkg tool. Some packages caused incompatibilities ...
Before recompiling dependable libraries, I used to get pre-compiled optware via ipkg tool. Some packages caused incompatibilities ...
- Mon Aug 01, 2011 4:27 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
Re: RPC can't bind
Hello,
I was aware of epoll problem and set env EVENT_NOEPOLL=1 when calling transmission-daemon.
When I started I transmission-daemon in the foreground I got the following messages
root@NAS:~# EVENT_NOEPOLL=1 TR_DEBUG=1 transmission-daemon -f -t -g /mnt/array1/share/.config/transmission-daemon ...
I was aware of epoll problem and set env EVENT_NOEPOLL=1 when calling transmission-daemon.
When I started I transmission-daemon in the foreground I got the following messages
root@NAS:~# EVENT_NOEPOLL=1 TR_DEBUG=1 transmission-daemon -f -t -g /mnt/array1/share/.config/transmission-daemon ...
- Wed Jul 13, 2011 9:06 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
Re: RPC can't bind
Hello,
Just a short update on transmission on my PPC NAS Box.
I've re-flashed fresh firmware, installed development tools and recompile transmission-daemon of previous releases. The last release worked successfully was 1.93. Anything above 1.93 causes 'cannot bind' symptom as above mentioned. All ...
Just a short update on transmission on my PPC NAS Box.
I've re-flashed fresh firmware, installed development tools and recompile transmission-daemon of previous releases. The last release worked successfully was 1.93. Anything above 1.93 causes 'cannot bind' symptom as above mentioned. All ...
- Tue Jun 28, 2011 2:08 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
Re: RPC can't bind
Thanks rb07 for your advises.
Sorry for keeping silent as I was busy with some other NAS of newer generation to playwith. I did check all the settings config and know how to enable disable certain ports or allow/deny list. No luck. I just dont have enough debug tool to see where exactly ...
Sorry for keeping silent as I was busy with some other NAS of newer generation to playwith. I did check all the settings config and know how to enable disable certain ports or allow/deny list. No luck. I just dont have enough debug tool to see where exactly ...
- Fri Jun 17, 2011 5:13 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
Re: RPC can't bind
Thanks rb07
I did the test with many ports as
transmission-remote 9093 -b -si
and checked LISTENING ports with command netstat -ltpn, you can notice that port 53413 is open, but no 9093
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID ...
I did the test with many ports as
transmission-remote 9093 -b -si
and checked LISTENING ports with command netstat -ltpn, you can notice that port 53413 is open, but no 9093
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID ...
- Fri Jun 17, 2011 2:47 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
Re: RPC can't bind
Thank you all for looking at this thread.
transmission-deamon successfully binds to it's ports 51413 or whatever I put in the command line parameter -P.
Torrent seeding/leeching still works as I put needed torrents into watch folder.
Yes, I did all the things I know to examine the problems ...
transmission-deamon successfully binds to it's ports 51413 or whatever I put in the command line parameter -P.
Torrent seeding/leeching still works as I put needed torrents into watch folder.
Yes, I did all the things I know to examine the problems ...
- Thu Jun 16, 2011 11:33 am
- Forum: Support
- Topic: RPC can't bind
- Replies: 14
- Views: 15704
RPC can't bind
Hello,
I am trying to build from source tarball transmission 2.31+ (12501) on TeraStation Pro I Linux 2.4.20_mvl31-ppc_terastation #36 Fri Aug 24 18:20:13 JST 2007 ppc GNU/Linux with all dependencies of latest releases: libevent-2.0.12-stable curl-7.21.6 gettext etc.... Everything ran smoothly ...
I am trying to build from source tarball transmission 2.31+ (12501) on TeraStation Pro I Linux 2.4.20_mvl31-ppc_terastation #36 Fri Aug 24 18:20:13 JST 2007 ppc GNU/Linux with all dependencies of latest releases: libevent-2.0.12-stable curl-7.21.6 gettext etc.... Everything ran smoothly ...