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

FunFiler wrote:

Looks like something went wrong with your FFP install.

Yeah thats what I figured, so I've formatted the drives and started again....3 times!

I know this is prob the wrong place, but since my problem only happens when I try and run the initial command-line startup:

# su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_a2/SHARE/Downloading -a 127.0.0.1,192.168.*.*" 
su: cannot run /bin/sh:/ffp/bin/bash: No such file or directory

All I've done since format is;

1) Place fun_plug and fun_plug.tgz in Volume_1
restart
2) Telnet in and activate root user:

#pwconv 
#passwd
#usermod -s /ffp/bin/sh root
#login
#store-passwd.sh

3) Activate SSH (and de-activate telnet)

#chmod a+x /ffp/start/sshd.sh
#sh /ffp/start/sshd.sh start
#chmod a-x /ffp/start/telnetd.sh

4)Copy over the packages Transmission-2.12-1.tgz, curl-7.18.1.tgz
5)Install and try and start

#funpkg -i curl-7.18.1.tgz
#funpkg -i Transmission-2.12-1.tgz
# su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_a2/SHARE/Downloading -a 127.0.0.1,192.168.*.*" 
su: cannot run /bin/sh:/ffp/bin/bash: No such file or directory

What have I forgotten to do? I know it must be something simple, but I can't for the life of me figure it out!
If anyone can see a mistake here please let me know.

Cheers,
B

track2 wrote:

How can I skip verify when want "re-seed" my files?? HELP ,verification take too much time!!!!please help me

If you want to seed files that you haven't seeded before, you can't skip the verify. Transmission has to know which parts you already have (and it cannot know beforehand that you already have all pieces).
A verification might also occur if you had a power failure or didn't shut down Transmission cleanly.

KyleK wrote:

It seems your install of funplug is missing bash. It is a separate package provided by fonz and must be installed separately.
I'd say install it and try again.

Although I honestly don't know what in the failing command is using bash.

Hi KyleK, thanks for the suggestion. I've downloaded and installed bash-3.2-3.tgz from fonz repository, restarted and tried again but still no luck, still getting the same error?

I have tried installing all fonz's packages on previous attempts, doing (as is suggested in fonz readme):

# cd /mnt/HD_a2
# rsync -av inreto.de::dns323/fun-plug/0.5/packages .
# cd packages
# funpkg -i *.tgz

But that still didn't get it going? .... hrmmmmm...

Cheers,
B

EDIT
I just re-installed all the fonz packages (code as above), rebooted, and still getting the same errors..

Last edited by breasthead (2010-11-22 15:29:47)

@breasthead: Can you start bash on the console? What does this command do:

$ which bash

If those work, you can try and change your default shell to bash:

$ usermod -s /ffp/bin/bash root

and log in again.

Please also check if user nobody exists.
And: Can you run Transmission as user root?

$ transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_a2/SHARE/Downloading -a 127.0.0.1,192.168.*.*

Since it continues even though you reloaded an old versions, I'd have to say it isn't an issue with the new release. Have you verified all the settings in your configuration file? When you rolled back, did you restore a backup configuration file? Are there errors in yout log file? Does it capture the ports and do UPNP port forwarding?

@KyleK

Hi again. First thanks again for giving me some more things to try. Last night I was again frustrated with this and formatted the HDD's again before going to sleep, so I'm starting again on a clean minimal install. I've done nothing more than fun_plug, curl, transmission and bash (in that order).

# which bash
/ffp/bin/bash
... to elaborate, I've installed bash-3.2-3.tgz ..

I tried switching to bash shell, logging out and back and still get the same error:
su: cannot run /bin/sh:/ffp/bin/bash: No such file or directory

My users are as follows:

#cat /etc/passwd
root:x:0:0:Linux User,,,:/home/root:/ffp/bin/bash
admin:x:500:500:Linux User,,,:/home/admin:/bin/sh
nobody:x:501:501:Linux User,,,:/home/nobody:/bin/sh:/ffp/bin/bash
sshd:x:33:33:sshd:/:/bin/false
avahi:x:1000:3::/home/ftp:/ffp/bin/sh
messagebus:x:1001:3::/home/ftp:/ffp/bin/sh
brent:x:1002:1002:Linux User,,,:/home/ftp:/bin/sh

It appears that the nobody user is there. Actually, looking at this, I don't understand why there is an avahi user there still? I haven't re-done all the avahi stuff yet this time?


And yes ... I forgot to mention that earlier, I can run as user root with:

# transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_a2/SHARE/Downloading -a 127.0.0.1,192.168.*.*
[15:49:47.853] Transmission 2.12 (11423) started (session.c:622)
[15:49:47.854] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:789)
[15:49:47.854] RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:789)
[15:49:47.855] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:962)
[15:49:47.855] RPC Server Whitelist enabled (rpc-server.c:966)
[15:49:47.856] DHT Generating new id (tr-dht.c:384)
[15:49:47.856] Using settings from "/mnt/HD_a2/.transmission-daemon" (daemon.c:483)
[15:49:47.856] Saved "/mnt/HD_a2/.transmission-daemon/settings.json" (bencode.c:1686)
[15:49:47.857] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
[15:49:47.857] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
[15:49:55.901] Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:95)
[15:49:55.902] Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:95)
[15:50:14.008] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:241)
...but this is the last of the output it sits here for several minutes with nothing more happening so ctrl. c to quit.

Cheers,
B

@Soprano Can you ping the tracker from the NAS? What about the Windows and/or Mac machine, do they all resolve to the same IP address?

If you can reproduce the problem then please report it to the Transmission devs. Although I really can't think of a reason why it would work on the Mac but not the NAS.

(Except: if the tracker is really overloaded, getting a response will be hit-or-miss. Your Mac/Windows clients may just have gotten lucky.)

Version 2.12 is crashing every day on my NAS. Other versions I had (eg. 2.03) worked for weeks without crashes. Maybe it depends on the torrents or the trackers'. Logs are never informative. They just stop at a certain point without a suspicious activity.

breasthead wrote:

Now to figure out why I was told to edit the nobody information ....

You just did

Actually, I posted an issue with Transmission 2.12 earlier in the thread

There is an issue with the gzip library when using the blocklist update option.

I didn't see any reference to it on the Transmission site. It looked to me more like a compile issue.

If you enable the blocklist update in settings.json and point it to the URL that is hardcoded in previous releases

    "blocklist-enabled": true, 
    "blocklist-url": "http://update.transmissionbt.com/level1.gz",

and then issue the update command (modifying for your actual port)

/ffp/bin/transmission-remote 9090 --blocklist-update

then the following error is logged and the daemon hangs

/ffp/bin/transmission-daemon: can't resolve symbol 'gzopen64'

Although I was successful in modifying and compiling Automatic, I didn't manage to get Transmission to compile yet so I couldn't investigate further myself.

Last edited by FunFiler (2010-11-24 16:07:25)

I am trying to update the blocklist from the Transmission Remote GUI web interface; unfortunately I get the following error:
gotNewBlocklist: http error 404:Not Found and then an Access Violation error.
Any ideas what could the problem be?

Also how can I connect to the transmission daemon using SSL?