Transmission

install Transmission 2.22 in Linkstaion Pro. (Optware)
Setting.json is as below: Starting transmission-daemon -f in telnet. transmission load in, and UPnP opened. port forwarding ok.
Why cannot open the Web GUI? Using Transmission Remote.
Error with request aborted: requst is cancelled

anyone can give your hand? give me some advice?

i used transmission to solove this problem.
Transmission 2.22 seems not compacitable for LS-Pro

Looks to me like the css files aren't loading.

You might want to open the transmission web client up in a browser debugger to see if there are any js/css/jpg/etc files that are failing to load?

I reinstall the eldder edition transmission 1.76, it works well. and very stable. but 1.76 is lack of some useful function.

I'm having the same problem. The jpg/css/javascript are not working. Anyone have any ideas on how to fix this?

I've installed this on a NAS.

I get this message aborted message when i run the webpage gui

# ./transmission-daemon -f
[19:12:23.405] Transmission 2.22 (12099) started (session.c:708)
[19:12:23.406] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:807)
[19:12:23.406] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:807)
[19:12:23.406] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:985)
[19:12:23.407] RPC Server Whitelist enabled (rpc-server.c:989)
[19:12:23.407] Using settings from "//.config/transmission-daemon" (daemon.c:498)
[19:12:23.407] Saved "/.config/transmission-daemon/settings.json" (bencode.c:1716)
[19:12:23.407] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
[19:12:23.407] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
[19:12:25.425] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.1.101:5555/ctl/IPConn" (upnp.c:113)
[19:12:25.425] Port Forwarding (UPnP) Local Address is "192.168.1.6" (upnp.c:115)
[19:12:25.425] Port Forwarding (UPnP) Port forwarding through "http://192.168.1.101:5555/ctl/IPConn", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.1.6:51413) (upnp.c:221)
[19:12:25.426] Port Forwarding (UPnP) Port forwarding successful! (upnp.c:224)
[19:12:25.426] Port Forwarding State changed from "Not forwarded" to "Forwarded" (port-forwarding.c:95)
Aborted (core dumped)
#

chuckyplay wrote:when i run the webpage gui

Do you mean "when you open the Web client"? In other words, when you open the Web client the daemon crashes?

If that is the case, that's odd, sounds like a very old problem where libevent 1.4.x didn't work right when trying to use epoll (which was the default and only known to affect NASes)... but Transmission 2.22 uses libevent 2.x which doesn't even have the option to disable epoll.

rb07 wrote:

chuckyplay wrote:when i run the webpage gui

Do you mean "when you open the Web client"? In other words, when you open the Web client the daemon crashes?

yes that's correct.

chuckyplay
And you also install Transmission using Optware?

It looks like a library or build problem... almost impossible to diagnose since we don't know what changes (patches or whatever) is Optware using, but any or all of those changes are probably the cause of the problem.

Can you check the version of libevent used?

A test, which shouldn't change anything, but... stop the daemon, then do the same test you showed above, now with an extra environment string:

rb07 wrote:And you also install Transmission using Optware?

yep

chuckyplay wrote:Can you check the version of libevent used?

it was 2.2

chuckyplay wrote:EVENT_NOEPOLL=1 ./transmission-daemon -f

this works! gui loads - settings are abit flaky. when the daemon crashes the settings reset.

There is no libevent 2.2, the latest is 2.0.11. Is Optware using a different libevent?

When the daemon crashes it doesn't save the settings.

The WebClient working with EVENT_NOEPOLL is strange, I searched the source code of libevent to see if they where still using it, and no, they don't use it. So, I don't really know what is going on.

Thanks for testing and writing about the results.

Confirmed by libevent's author: EVENT_NOEPOLL still works to disable using epoll.

That means all NAS users need to keep disabling it with the latest versions of Transmission.

x190 wrote:

rb07 wrote:Confirmed by libevent's author: EVENT_NOEPOLL still works to disable using epoll.

That means all NAS users need to keep disabling it with the latest versions of Transmission.

This seems to bite a lot of users. Can something be done on Transmission's side?

I just added some info to the FAQ, in the section "Distribution Specific Questions".

I'm also in communication with Nick Mathewson, one of the main developers of libevent. He wants to see if the problem can be detected and corrected, or at least detected and disable epoll on these devices.