to have the ch3snas working fine with nzbget you need the nzget.conf file
I have adjusted the nzbget.conf delivered with latest beta release nzbget-0.6.0-testing-r269 to have it working with the CH3SNAS and my previous installation instruction. download the new file here you can rename the nzbget.conf.new to nzbget.conf

I’m now checking if there is an updated unpak script yes/no ;-)

Posted in Generic, Life 2 Comments »

As some users are still having issues with nzbget and the installation on a CH3SNAS I made a new installation instruction.

This Instruction only tells you how to install NZBGET. The instruction does not tell you the use of the postprocess configuration file (par and unpack the downloaded files) and the installation of nzbgetweb.

I used a totally empty CH3SNAS with 2 fresh formatted HDD’s ..

Follow the instructions and nzbget is installed and started. Please note that this is a quick and dirty installation from scratch and you need to do a lot of other fine-tuning but this shows the simplest way how it should be installed. I expect you have a little Linux knowledge and you know what telnet is.

You can copy the files in \Volume_1

Volume_1 should be equal to /mnt/HD_a2 later used in telnet.

copy fun_plug
copy fun_plug.tgz
# download these 2 files from:
http://www.inreto.de/dns323/fun-plug/0.5/
—
copy nzbget-0.6.0-testing-r269-bin-dns323-arm.tar.tar
or nzbget-0.6.0-testing-r269-bin-dns323-arm.tar.gz (depends on how you downloaded the file).
# download from http://sourceforge.net/project/showfiles.php?group_id=102632&package_id=264752

Note: depending on how you downloaded the file, it can also have extension *.tar.gz than the commandline will be:
—
copy nzbget.conf.example
# download from http://www.aroundmyroom.com/ch3snas-funplug/nzbget.conf.example

# above files you have to put in /mnt/HD_a2
reboot the CH3SNAS
—
open telnet session  with for example `Putty`
you will see: #

cd /mnt/HD_a2
# make some folders. They are used in the nzbget.conf file
mkdir unpack
mkdir usenet
mkdir usenet/download
mkdir usenet/queue
mkdir usenet/tmp
mkdir usenet/nzb
# all folders are made, if you want to have other names, or locations you have to adjust them in the nzbget.conf file as well.

# if you want to have all folders writable for everyone than you can do this:
Option:
chmod 777 usenet -R
But I do not believe that this is necessary
—

mv nzbget-0.6.0-testing-r269-bin-dns323-arm.tar.tar /mnt/HD_a2/unpack
# move the nzbget file to the unpack folder
tar -xvzf nzbget-0.6.0-testing-r269-bin-dns323-arm.tar.tar
# note: the file can have a different extension (depends on how you downoaded it, than the commandline will be:

mv nzbget-0.6.0-testing-r269-bin-dns323-arm.tar.gz /mnt/HD_a2/unpack
# move the nzbget file to the unpack folder
tar -xvzf nzbget-0.6.0-testing-r269-bin-dns323-arm.tar.gz
# unpack the file

cp nzbget /ffp/bin
cp /mnt/HD_a2/nzbget.conf.example /ffp/etc/nzbget.conf
# copy the nzbget file to the binary location
# copy the example configuration file to the correct location,
# the used configuration file is modified to work with the
# Ch3SNAS and the created folders. DO NOT USE the delivered nzbget.conf file as it’s not modified to work with CH3SNAS
—
cd /ffp/bin
chmod 755 nzbget
./nzbget -D -c /ffp/etc/nzbget.conf
—
# change folder to /ffp/bin
# make the nzbget file executable
# start it as deamon (background) with correct configuration file

with above command the nzbget is started without any error messages in the background

the command ‘ps’ shows it running
12864 root     ./nzbget -D -c /ffp/etc/nzbget.conf
12869 root     ./nzbget -D -c /ffp/etc/nzbget.conf
12872 root     ./nzbget -D -c /ffp/etc/nzbget.conf
12873 root     ./nzbget -D -c /ffp/etc/nzbget.conf
12874 root     ./nzbget -D -c /ffp/etc/nzbget.conf

The rest is already described on this weblog.

The postprocess / unpak script I use can be found downloaded here: http://www.aroundmyroom.com/ch3snas-funplug/
updated: 28/12/08
updated: 29/12/08 ; made the location for nzbget.conf.nexample more clear

Posted in Work 18 Comments »

Today was testing day with Andrei (developer of nzbget) and Fonz (developer of FFP).  Cause nzbget crashed during repair of RAR files after checking the validation of the RAR files.

Finally it resulted in a new binary created by Andrei. (no fix from Fonz yet cause it’s still unclear what is the real issue or if it has to do with statically and dynamically linking of libraries).

So for all users of the Conceptronic CH3SNAS or DNS-323 who do not want to use optware (ipkg) (like me) but want to use NZBGET with FFP 0.5

Here are the guidelines:

First make sure you are using the correct extra libraries libpar2 (libpar2-0.2-2.tgz) (install with funpkg -i after download) and libsigc libsigc++-2.0.18-1.tgz (install with funpkg -i after download)

(according to Andrei it might even not be necessary to need these seperate tools when using the special compiled version for CH3SNAS/DNS-323).

You can find the source & scripts here

Make sure you download and install the correct unrar version. I have just upgraded my version to 3.7.8-1 from ULI the older version 3.4 caused strange crash during a long unrar session.

Download the nzbget-static-all-release.zip file, and if you have troubles you could use the debug version. Also available for download from the same webpage. This is the modified binary.

Put this file on your CH3SNAS. unzip this file and make sure it will be in /ffp/bin
You can use my nzbget.conf script, modify the usenet server details!

the nzbget.conf file must be put in /ffp/etc  folder
All my files are in /mnt/HD_a2/usenet
and under this folder there are 4 other folders needed: nzb, download, queue and tmp

If you want to process the RAR files after download you need a postprocess.sh file, you can grab your copy from my page and make sure it is called postproces.sh and put in /ffp/etc as well. Modify pathnames if necessary.

The last thing you need to do is grab the nzbget.sh file and put it in /ffp/start and make sure you make it executable with: chmod a+x nzbget.sh

You can check the working witht the command: sh nzbget.sh start - check it with sh nzbget.sh status - and stop it with sh nzbget.sh stop

Reboot your CH3SNAS or DNS-323 and after a few minutes you should be able to enter telnet again and see that nzbget is running (use ps as command to see the processes).

Smart people also make lighttpd working in combination with nzbgetweb .. to get a webfrontend for nzbget. the only thing you have to do is copy a nzb file into the /mnt/HD_a2/usenet/nzb folder

update 13-10:

changed links to folder content so that updates can be found rather than missing.

update 16-10:

Oeps.. some links to the files were gone .. Note: I am busy to get a more advanced postprocess script working ok.

When using NZBGETWEB

Addon: uploading large NZB > 8MB through the webinterface of NZBGETWEB is not possible if you do not use a separate PHP.INI. So please copy from /ffp/etc/examples the php.ini-recommended to /ffp/etc/php.ini, change the max upload file size. Although lighttpd has PHP support it does not use PHP.INI so you have to add this. open /ffp/etc/lighttpd.conf and edit : “bin-path” => “/ffp/bin/php-cgi“, to  /ffp/bin/php-cgi -c /ffp/etc/php.ini“; restart lighttpd and also large NZB files can be uploaded with NZBGET if you use this webfrontend.

enjoy!

Posted in Life, Weblog related 58 Comments »

It took me some effort to get the fun_plug part working on the Conceptronic CH3WNAS, but after hours of testing I was able to create the correct files.

download the telnet package for the CH3WNAS

Copy the RAR file to the root of the harddisk and unpack the rar file also into the ‘root’ (ch3wnas\hdd_a [share]) of the device.

The files: fun_plug, sed and the busyboxy file will be available now. Reboot the device and telnet should be available.

You have to login with the username: root with the password of the admin. If seeing the black screen as shown here: it’s working ..

Have fun ..

Why using telnet? For some: hacking is a way of life, but for me: if there are files you cannot modify / delete for what kind of reason: with the telnet session you can: rm [filename] -rf and ALL is removed (use it with caution, I do not guarantee the safety of your data, cause I do not own your backup) ;-)

b.t.w. no idea how stable it is .. I lost 2 times a connection with the device already .. a hard reboot was the only thing to get it alive again.

Posted in Work 14 Comments »