Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I had to add
EXPORT PATH=$PATH:$FFP_PATH/bin:$FFP_PATH/sbin
to my fun_plug file after the variable definitions as the logon script kept giving me errors about being unable to find [, ], mount, etc., etc., and I assume that it also needs the stuff in sbin.
Last edited by blarg (2008-12-28 03:07:52)
Offline
blarg wrote:
I had to add
EXPORT PATH=$PATH:$FFP_PATH/bin:$FFP_PATH/sbin
to my fun_plug file after the variable definitions as the logon script kept giving me errors about being unable to find [, ], mount, etc., etc., and I assume that it also needs the stuff in sbin.
What 'logon script'?
/ffp/etc/rc already has 'export PATH=/ffp/sbin:/ffp/bin:/usr/sbin:/sbin:/usr/bin:/bin'
Offline
fun_plug.tgz wasn't unzipping properly on boot
> **** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****
> Fri Dec 26 22:26:24 GMT 2008
> ln -snf /mnt/HD_a2/ffp /ffp
> * Installing /mnt/HD_a2/fun_plug.tgz ...
> tar: inflate error 2
> /ffp/etc/rc: Not found or not executable
so I had to unzip it manually, create the fpp directory on Volume_1 and drop everything in. On reboot fpp.log then kept giving me errors like:
> **** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****
> Fri Dec 26 22:53:22 GMT 2008
> ln -snf /mnt/HD_a2/ffp /ffp
> * Running /ffp/etc/fun_plug.init ...
> /bin/sh: Can't open [
> /bin/sh: Can't open [
> /bin/sh: Can't open [
> /bin/sh: Can't open mount
> /bin/sh: Can't open grep
> /bin/sh: Can't open mount
> /bin/sh: Can't open chmod
> /bin/sh: Can't open chmod
> /bin/sh: Can't open grep
> /ffp/etc/fun_plug.init: groupadd: error 80
> /bin/sh: Can't open mkdir
> /bin/sh: Can't open touch
> /bin/sh: Can't open chgrp
> /bin/sh: Can't open chmod
> /bin/sh: Can't open echo
> /bin/sh: Can't open echo
> * Running /ffp/etc/rc ...
> /ffp/etc/rc: rcorder: error 80
> * OK
and adding the PATH statement to "fun_plug" resolved the issue.
I know other people have had to manually drop the files into the fpp directory because of similar tar errors. Some claim the errors were due to corrupt .tgz files, but after several re-downloads and manual unpackings I know the archive isn't corrupt (using stuffit or izarc on different OS's). Simply adding the path statement after a manual unpacking fixed it.
BTW, great work on this package - everything I have tried so far works like a charm. The wiki is very useful.
Cheers.
Offline
blarg wrote:
Some claim the errors were due to corrupt .tgz files
I think there are some 'smart' browsers that unzip .tgz archives on-the-fly (resulting in this kind of error). Did you try a different browser? It's not a good idea to unzip the archive yourself over the windows network - file modes are lost that way.
Offline
I used Firefox 3.0.5 on an XPSP3 machine, saved to local drive, then copied to the NAS without touching it initially. Errors as above.
I also used Firefox 3.0.5 on a MacOS X.4 machine, seperately, and saved it to local drive before uploading it. Both cases resulted in the same errors.
The files unpacked, seperately, fine using either IZArc on the XPSP3 machine or StuffIt on the Mac.
Firefox is the only common ground there, but the fact that they unpacked seperately seems to indicate that it's not FF.
Offline
We're getting the exact same errors in ffp.log that Blarg shows above. We've added the path statement as follows:
# setup script (used for ffp on USB disk)
FFP_SETUP_SCRIPT=/mnt/HD_a2/.bootstrap/setup.sh
# rc file path
FFP_RC=/ffp/etc/rc
EXPORT PATH=$PATH:$FFP_PATH/bin:$FFP_PATH/sbin
echo "**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****"
date
# check for setup script. an example use for this is to load USB
# kernel modules and mount a USB storage device. The script is
# sourced, that means you can change variables, e.g. FFP_PATH to point
# to the USB device.
if [ -x $FFP_SETUP_SCRIPT ]; then
echo "* Running $FFP_SETUP_SCRIPT ..."
. $FFP_SETUP_SCRIPT
fi
-----------------
But still, we cannot telnet into the unit. Any ideas?
Offline
When putting the files in the root of Volume_1, nothing happens. Files are original ones (no .txt extension).
FW = 1.07
2 samsung 1.5 TB are mounted in RAID1
The device seems to ignore the two fun_plug files.
Anyone any ideas??
Offline
While I was able to get everything running on my DNS-321 with firmware 1.1, we can't get telnet to work on my father's unit.
We experienced the EXACT same issues Blarg described above. The files were download to an XPSP3 machine, then FTPd to the DNS. The permission on fun_plug was reset with 'quote site....' After restart we had an ffp directory and the tarball was gone, but the ffp dir was empty. We manually unzipped everything on the XP machine then FTPd it all back to the ffp dir on DNS. We restarted the machine and got the same log Blarg has above. We then added the path statement as shown below using Windows WordPad. No restart since has changed anything, and nothing is written to the log!!!
Anyone???
----
clickitysplit wrote:
We're getting the exact same errors in ffp.log that Blarg shows above. We've added the path statement as follows:
# setup script (used for ffp on USB disk)
FFP_SETUP_SCRIPT=/mnt/HD_a2/.bootstrap/setup.sh
# rc file path
FFP_RC=/ffp/etc/rc
EXPORT PATH=$PATH:$FFP_PATH/bin:$FFP_PATH/sbin
echo "**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****"
date
# check for setup script. an example use for this is to load USB
# kernel modules and mount a USB storage device. The script is
# sourced, that means you can change variables, e.g. FFP_PATH to point
# to the USB device.
if [ -x $FFP_SETUP_SCRIPT ]; then
echo "* Running $FFP_SETUP_SCRIPT ..."
. $FFP_SETUP_SCRIPT
fi
-----------------
But still, we cannot telnet into the unit. Any ideas?
Offline
I had to FTP the files onto the DNS using windows command line FTP and issue 'quote site chmod 777 fun_plug' before anything worked. Once done, though, it was sort of hit or miss. On my DNS-321 (with .5TB Seagates) it just eventually worked. On my Dad's DNS-321 (with 1.5TB Seagates), it has yet to work.
Also make sure your physical and logical Volume_1 are the same. If not try installing on Volume_2. The install guides at the wiki explain better...
Glasbakkie wrote:
When putting the files in the root of Volume_1, nothing happens. Files are original ones (no .txt extension).
FW = 1.07
2 samsung 1.5 TB are mounted in RAID1
The device seems to ignore the two fun_plug files.
Anyone any ideas??
Offline