DSM-G600, DNS-3xx and NSA-220 Hack Forum

Transmission v1.83 is up, containing just bugfixes for the 1.80 release.

Enjoy!

I tried funpkg -u Transmission-1.83-1.tgz then rebooted the NAS but still no luck

after the reboot I did a 'ps' from the command line but it doesn't look like Transmission is running

/mnt/HD_a2 # ps
PID   USER     COMMAND
    1 root     init
    2 root     [ksoftirqd/0]
    3 root     [events/0]
    4 root     [khelper]
    5 root     [kthread]
   11 root     [kblockd/0]
   14 root     [khubd]
   49 root     [pdflush]
   50 root     [pdflush]
   52 root     [aio/0]
   51 root     [kswapd0]
  190 root     [scsi_eh_0]
  191 root     [scsi_eh_1]
  192 root     [scsi_eh_2]
  193 root     [scsi_eh_3]
  204 root     [mtdblockd]
  218 root     [kcryptd/0]
  219 root     [kmirrord/0]
  230 root     [loop0]
1202 root     atd
1473 root     chkbutton
1498 root     /web/webs
1501 root     fancontrol
1538 root     /usr/sbin/samba/smbd -D
1542 root     /usr/sbin/samba/nmbd -D
1546 root     /usr/sbin/samba/smbd -D
1548 root     op_server 3 3 3
1555 root     -sh
1582 root     pure-ftpd (SERVER)
1617 root     lpd Waiting
1648 root     crond
1721 root     /ffp/sbin/rpc.portmap
1731 root     /ffp/sbin/unfsd -e /ffp/etc/exports
1745 root     /ffp/sbin/telnetd -l /ffp/bin/sh
1803 root     /ffp/bin/sh
1908 root     ps
/mnt/HD_a2 #

The log gets created but nothing is logged..

The command line shows "Bus Error"

I attached a screenshot of the error and the command line you asked me to execute

Last edited by ithrowpicks (2010-01-29 20:19:25)

---

Attachments:
BusError.jpg, Size: 17,021 bytes, Downloads: 215

OK I uninstalled everything Transmission, curl, and uclibc in the order below and reinstalled in the same order and it appears to be working properly now.  After reinstalling the settings.json file was intact so I didn't have to edit that as well.

Uninstall with these commands
# funpkg -r curl-7.18.1.tgz
# funpkg -r Transmission-1.83-1.tgz
# funpkg -r uclibc-0.9.29-7.tgz

Reboot the NAS

Reinstall with these
# funpkg -i curl-7.18.1.tgz
# funpkg -i Transmission-1.83-1.tgz
# funpkg -i uclibc-0.9.29-7.tgz

Did I do something wrong by executing the following?  Should I have done something else as well?
# funpkg -u Transmission-1.83-1.tgz

Last edited by ithrowpicks (2010-01-29 23:48:00)

1.83 crashes for me whenever I open the web page.  I get the following when I run Transmission in the foreground

[17:39:12.087] Blocklist "level1.bin" updated with 224277 entries (blocklist.c:304)
[17:39:12.088] Blocklist "level1.bin" contains 224277 entries (blocklist.c:110)
[17:39:12.088] Transmission 1.83 (10040) started (session.c:647)
[17:39:12.088] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:772)
[17:39:12.089] RPC Server Adding address to whitelist: 192.168.0.100 (rpc-server.c:772)
[17:39:12.089] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:945)
[17:39:12.089] RPC Server Whitelist enabled (rpc-server.c:949)
[17:39:12.089] DHT Reusing old id (tr-dht.c:365)
[17:39:12.090] DHT Bootstrapping from 52 nodes (tr-dht.c:146)
[17:39:12.090] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
[17:39:12.090] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
[17:39:12.091] Using settings from "/mnt/usb/transmission" (daemon.c:385)
[17:39:12.091] Saved "/mnt/usb/transmission/settings.json" (session.c:467)
[17:39:14.101] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.0.1:4444/wipconn" (upnp.c:105)
[17:39:14.101] Port Forwarding (UPnP) Local Address is "192.168.0.110" (upnp.c:107)
[17:39:14.102] Port Forwarding (UPnP) Port forwarding through "http://192.168.0.1:4444/wipconn", service "urn:schemas-upnp-org:service:WANIPConnection:1".  (local address: 192.168.0.110:12345) (upnp.c:194)
[17:39:14.102] Port Forwarding (UPnP) Port forwarding successful! (upnp.c:197)
[17:39:14.102] Port Forwarding State changed from "Not forwarded" to "Forwarded" (port-forwarding.c:87)
[17:39:15.108] SO_SNDBUF size is 16384 (fdlimit.c:659)
[17:39:15.108] SO_RCVBUF size is 43689 (fdlimit.c:661)
[17:39:23.213] Searching for web interface file "/home/root/.local/share/transmission/web/javascript/transmission.js" (platform.c:526)
[17:39:23.213] Searching for web interface file "/ffp/share/transmission/web/javascript/transmission.js" (platform.c:526)
[17:39:23.213] Blocklist "level1.bin" contains 224277 entries (blocklist.c:110)
Killed

1.83 Runs fast and bugfree.

finally! magnet links are supported from the web ui! the only thing missing is a web based interface for RSS download support.

romanl wrote:

I am getting lots of "tracker did not respond" errors after running transmission 1.83 for some time. Looks like connection resources are leaking or whatever.

i noticed the same

Transmission 1.83 seems to be working ok for me.

Watch directory is fine and have seen no issues but have not been monitoring closely.

Thanks as always Kyle.

Oh, just one suggestion.  How about putting a note about the umask setting in the settings.json file with the installation instructions as this seems to trip a number of people up with access problems after a download has finished.

Kylek, can you make a build from nightly snapshot, to confirm if this bug persists?

It seams that the download links are not working can someone please repair or give new links to 1.83 thanks people.

Hi KyleK, can you apply this patch to your next release?

--- transmission.sh.bak 2010-02-08 12:42:32.000000000 +0200
+++ transmission.sh     2010-02-08 12:43:33.000000000 +0200
@@ -8,6 +8,7 @@

 name="transmission-daemon"
 command="/ffp/bin/$name"
+su_cmd="/ffp/bin/su"
 start_cmd="transmission_start"
 stop_cmd="transmission_stop"
 status_cmd="transmission_status"
@@ -15,12 +16,11 @@

 transmission_start()
 {
-
        if [ ! -d ${TRANSMISSION_HOME} ]; then
-               su $user -c "mkdir ${TRANSMISSION_HOME}"
+               $su_cmd $user -c "mkdir ${TRANSMISSION_HOME}"
        fi
        echo "Starting $name"
-       su $user -c "$command -f -g ${TRANSMISSION_HOME} 1>${TRANSMISSION_HOME}/$name.log 2>&1 &"
+       $su_cmd $user -c "$command -f -g ${TRANSMISSION_HOME} 1>${TRANSMISSION_HOME}/$name.log 2>&1 &"
 }

 transmission_stop()

Without this, transmission won't start from cron, because /ffp/bin is not in the PATH.

Sorry for the files being down over the weekend, I upgraded the storage in my server, which took a while
@angdraug: Thanks for the info, the next version will include your changes.
zuluwalker: The issue has been fixed as far as I know, I'll post a nightly build later tonight so you guys can check.
I expect 1.90 for next week.