Problem with 1.60 WebUI on headless NAS

[cico]

I'm running transmission-daemon with the web interface on a Synology CS407 NAS. I've been still using 1.34 because of a unicode bug in 1.4x/1.5x reported here and here. But even though the bug is still there in 1.60 I'd like to upgrade now because I don't want to miss the new enhancements to the web interface, thank you for that!


But after upgrading and restarting the daemon I got this...

Code: Select all

syno> transmission-daemon -f
[20:05:30.427] Couldn't create socket: Address family not supported by protocol
[20:05:30.445] System does not seem to support IPv6. Not listening onan IPv6 address
[20:05:30.447] RPC Server: Adding address to whitelist: 127.0.0.1
[20:05:30.447] RPC Server: Adding address to whitelist: 192.168.*.*
[20:05:30.448] RPC Server: Serving RPC and Web requests on port 9091
[20:05:30.449] RPC Server: Whitelist enabled
[20:05:30.449] Transmission 1.60 (8339) started
[20:05:31.431] %s succeeded (%d): initnatpmp succeeded (0)
[20:05:31.431] %s succeeded (%d): sendpublicaddressrequest succeeded (2)
[20:05:39.470] Starting: Starting
[20:05:39.470] Opened port %d on %s to listen for incoming peer connections: Opened port 51413 on 0.0.0.0 to listen for incoming peer connections
[20:05:39.530] Starting: Starting

...and then, but first AFTER calling the webinterface

Code: Select all

[20:36:13.948] Searching for web interface file "/root/.local/share/transmission/web/javascript/transmission.js"
[20:36:13.974] Searching for web interface file "/opt/share/transmission/web/javascript/transmission.js"

That's all, the crucial line
"Serving the web interface files from "/opt/share/transmission/web"
isn't shown and my browser gives me a "404"

(of course all files are where they should be)


The daemon itself is running fine, all my active torrents from 1.34 started again instantly after upgrading, so in my understanding it seems to be an issue with Transmission's webserver. I'm also wondering what the first two lines after starting the daemon concerning IPv6 mean, could that be the reason why Transmission isn't serving the WebUI? And if so, can the IPv6 support be disabled to make Transmission run on my Syno again?

Just my humble thoughts, sorry if that is nonsense...

Any help would be much appreciated!

[rb07]

I think you are seeing this problem: http://trac.transmissionbt.com/ticket/2030; there is a patch near the end.

I'm also using a NAS and didn't see the problem, it seems that only new installations run into it.

About the other messages... they are normal, the ones about IPv6 just mean that transmission first tries to attach itself to the port using IPv6 (which the NAS doesn't have) then it tries IPv4 which succeeds. The weird looking messages (with format specs instead of real data is just the garbage transmission spills, its been like that for a long time (at least on the NASes, I haven't looked elsewhere).

One question: in my NAS (an HP MediaVault) I have to patch daemon/remote.c so that "transmission-remote -l" does show the list, not just one "success" line, is it the same on yours? The current patch (trivial really) is:

Code: Select all

--- daemon/remote.c.orig        2009-05-05 18:04:38.000000000 -0500
+++ daemon/remote.c     2009-05-05 18:05:24.000000000 -0500
@@ -724,7 +724,7 @@
     {
         *buf = '\0';
     }
-    else switch( status )
+    else switch( (int)status )
     {
         case TR_STATUS_STOPPED:
             tr_strlcpy( buf, "Stopped", buflen );
@@ -1247,7 +1247,7 @@
         const char * str;
         tr_bencDictFindInt( &top, "tag", &tag );
 
-        switch( tag )
+        switch( (int)tag )
         {
             case TAG_SESSION:
                 printSession( &top ); break;

[cico]

rb07,

thanks for your detailed answer! Yes, it seems I have the same problem as described by many others in ticket #2030, sorry for not searching the forum close enough before opening a new topic.

I'm a macuser with very little linux experience and I'm not able to build transmission from source by myself and therefore depend on the optware feed on nslu2-linux.org where only the official release candidates appear. So I'm afraid I have to wait for 1.61.

For me the problem occurs after updating as well as after a new installation. First I updated from my existing 1.34, then a day later I did a complete clean install of my NAS (for some other reason), removed all optware stuff, upgraded firmware, newly bootstraped and finaly installed transmission again.

I never used transmission-remote before and currently I haven't any active torrents. It gives me this (unpatched)

Code: Select all

syno> transmission-remote -l
ID     Done       Have  ETA           Up    Down  Ratio  Status       Name
Sum:              None               0.0     0.0
syno> 

Maybe this can answer your question, even without any torrent running.

Thanks again for your help!

[cico]

fantastic, optware transmission has already been upgraded to 1.60+r8349 !!

[rb07]

Maybe this can answer your question, even without any torrent running.

Yes, thank you.

[cico]

unfortunately for me on my synology nas the problem is still there respectively I must report a new one...

the "404 bug" was solved with r8349 for me. but when upgrading to r8368 (which should be the "final" version regarding ticket #2030 yesterday I saw a new issue: the webinterface loads, showing all active torrents, I can pause, resume, delete torrents, BUT I cannot open/add a new torrent! after selecting the .torrent in the open dialog and clicking "upload" simply nothing happens.

this seems to be a general problem, another user reports the same thing appearing on his mac. I checked on my mac as well (normally I'm only using my nas for my torrent activities) and I can confirm, with 1.60 everything is ok, with 1.61 I cannot open/add torrents via clutch...

[rb07]

I haven't used 1.61 but I'm curious, is not the torrent paused mis-feature? (i.e. the torrent is added, but as paused)

If is not that you should report the problem to the release thread or, better yet, to the trac bug reports.

[cico]

no, regardless of trying to open a torrent via 1.61 clutch with "start transfers when added" checked or not, on my syno nas as well as on my mac, nothing is ever shown up...

[rb07]

OK, thanks for the info.

If it "moves like a bug, quacks like a bug, stinks ..." then its a bug. You're not the only one reporting this problem.

[super-poussin]

try the last nightly