Page 1 of 5 123 ... LastLast
Results 1 to 15 of 64

Thread: [How To] Install and Configure Hellanzb

  1. #1

    [How To] Install and Configure Hellanzb

    Hellanzb is (like sabnzbd) a tool for downloading, repairing and unpacking nzb-files from usenet.

    Prerequisites:
    - You need to be using the OLEG optware repository
    - You need to have a swap-file

    The Howto:

    Install the necessary packages:

    Code:
    ipkg update
    
    ipkg install py-hellanzb
      or if you want to use python2.5
    ipkg install py25-hellanzb
    The hellanzb package uses the following defaults:

    Hellanzb.PREFIX_DIR = '/opt/tmp/'
    Hellanzb.LOG_FILE = '/opt/var/log/hellanzb.log'

    If you like it, you only need to enter your news-servers in /opt/etc/hellanz.conf
    Otherwise change those settings aswell.

    The package creates a startup-script S71hellanzb, so you can start it by /opt/etc/init.d/S71hellanzb, or a reboot.

    nzb files go in /opt/tmp/nzb/daemon.queue/, the result comes in /opt/tmp/usenet/

    Default, hellanzb has no Webinterface, so you can track progress by watching the log file, or by installing the webinterface Zussaweb using instructions below. Or you can try to install another interface listed on hellanzb.com.

    Instructions for Zussaweb:

    Code:
    ipkg update
    ipkg install lighttpd
    ipkg install fcgi-php
    Edit /opt/etc/lighttpd/lighttpd.conf and make the following changes:

    Code:
      change
    #                               "mod_fastcgi",
      into
                                    "mod_fastcgi",
    Code:
      change
    url.access-deny             = ( "~", ".inc" )
      into
    url.access-deny             = ( "~", ".inc", ".sqlite" )
    Code:
      change
    #fastcgi.server             = ( ".php" =>
    #                               ( "localhost" =>
    #                                 (
    #                                   "socket" => "/tmp/php-fastcgi.socket",
    #                                   "bin-path" => "/usr/local/bin/php"
    #                                 )
    #                               )
    #                             )
    
      into
    fastcgi.server             = ( ".php" =>
                                   ( "localhost" =>
                                     (
                                       "socket" => "/tmp/php-fastcgi.socket",
                                       "bin-path" => "/opt/bin/php-fcgi"
                                     )
                                   )
                                )
    Now you are ready to start lighttpd by /opt/etc/init.d/S80lighttpd
    Next download and unpack zussaweb:

    Code:
    cd /opt/tmp
    wget http://download.sourceforge.net/sourceforge/zussaweb/zussaweb03.tar.gz
    cd /opt/share/www
    tar -xzvf /opt/tmp/zussaweb03.tar.gz
    Next you need to change the values of $disk and $download_nzb_path in the file /opt/share/www/zussaweb/settings.php

    Finally we need to fix a bug:
    Edit /opt/share/www/zussaweb/functions.php and change:

    Code:
    function freediskspace() {
            return (round (disk_free_space(disk)/1024/1024,2));
    }
    into:
    Code:
    function freediskspace($disk) {
            return (round (disk_free_space($disk)/1024/1024,2));
    }
    Now you can use the interface at http://192.168.1.1:8081/zussaweb/

    Happy leeching
    Last edited by DrChair; 12-01-2009 at 22:42. Reason: lastest lighttpd has changed document-root

  2. #2

    Thumbs up

    Hi DrChair,

    I followed your tutorial (using ipkg install py-hellanzb), but when I tried starting it by executing /opt/etc/init.d/S71hellanzb I received an errormessage stating "nice not found" or something like that.
    I opened S71hellanzb in VI and noticed that it calls "nice -n19 hellanzb.py".
    Running the .py actually starts hellanzb.
    So it seems that "nice" is missing from my firmware. Any idea where or how I can get this (Am I correct in thninking it's not really needed for running hellanzb?)

    Thanks for the instructions anyhow!!

    Jeroen

  3. #3
    Dr Chair

    I have Hella working and Zussa only sort of. It monitors fine and I can manually copy NZB files to the monitored queue directory but the Newsbin ID won't work and the Upload NZB won't work.

    Do yours?

  4. #4

    Question Queued?

    Hi all,

    It looks like HellaNZB is stalled on QUEUED, any idea what's wrong?
    Here's the log:
    [admin@(none) root]$ tail /opt/var/log/hellanzb.log
    2007-11-24 09:32:40,368 INFO
    2007-11-24 09:32:40,644 INFO hellanzb v0.13 (config = /opt/etc/hellanzb.conf, daemonized, C yenc module)
    2007-11-24 09:32:45,321 LOGFILE (changeme) Opening 3 connections...
    2007-11-24 09:32:45,500 INFO hellanzb - Now monitoring queue...
    2007-11-24 09:32:46,103 INFO Found new nzb: jeroen
    2007-11-24 09:32:47,070 INFO Parsing: jeroen.nzb...
    2007-11-24 09:32:49,852 INFO Parsed: 16 files (381 posts), 139.0MB
    2007-11-24 09:32:50,673 INFO Queued: 139.0MB
    [admin@(none) root]$

  5. #5
    Quote Originally Posted by Jeroen van Omme View Post
    So it seems that "nice" is missing from my firmware. Any idea where or how I can get this (Am I correct in thninking it's not really needed for running hellanzb?)
    hmmm, I checked my router (oleg 1.9.2.7-8) and it has nice installed in the firmware (/bin/nice). So I presumed it to be a standard. I might need to add a check for nice in a future startup script.

    Another thing that's not 100% oke with current startup-script, is that is doesn't set PATH. (so it can't find nice even if it is present).

    The purpose of nice is, that hellanzb (and more important unrar and par2) get started with the lowest priority, so it doesn't slow down more important processes like samba. So it's not necessary but recommended.
    You should be able to install it by installing coreutils.

  6. #6
    Quote Originally Posted by methanoid View Post
    I have Hella working and Zussa only sort of. It monitors fine and I can manually copy NZB files to the monitored queue directory but the Newsbin ID won't work and the Upload NZB won't work.

    Do yours?
    Upload NZB works fine over here... Prehaps you didn't enter $download_nzb_path correctly in settings.php, or the permissions on the queue directory are wrong?

    I don't have a Newzbin account, so i can't help you on that.

  7. #7
    Quote Originally Posted by Jeroen van Omme View Post
    Hi all,

    It looks like HellaNZB is stalled on QUEUED, any idea what's wrong?
    Hellanzb doesn't log anything during downloading.
    When it's done downloading, it should log something like this:
    Code:
    Transferred 273.5MB in 10m 57s at 426.1KB/s

  8. #8
    Quote Originally Posted by DrChair View Post
    Hellanzb doesn't log anything during downloading.
    When it's done downloading, it should log something like this:
    Code:
    Transferred 273.5MB in 10m 57s at 426.1KB/s
    Dr,
    I checked my log after some 24 hours, but it still says "QUEUED"....
    I read somewhere that you can turn ons verbose debug-logging, I will try this next.....or maybe you (or anyone else) have a suggestion?

  9. #9
    Hi DrChair,

    Nice to see that you've written a how-to of this application.

    As I have running HellaNZB and Zussaweb for quite a while now I'm going to double check if I have everything configured like you stated.


    One thing though, a problem which I'm experiencing which I hope to hear from others if they're experiencing the same problem, while HellaNZB is very stable (have download more than 20 dvd's in a row, crunching for 3-4 days) it does not unrar everything it downloads. In my opnion: if the downloaded package contains 'funky' characters like hyphens, spaces, underscores etc. it does not extract the package.

    I think it has something to do with the unrar command not being called correct from within HellaNZB.. something like:

    unrar e downloaded-package.rar

    instead of:

    unrar e 'downloaded-package.rar'

    If the package name is not encapsulated within quotes unrar does not unrar, while when it is encapsulated in quotes, it does.


    Anyhow,

    thanks for the write-up !

  10. #10
    Quote Originally Posted by Jeroen van Omme View Post
    I read somewhere that you can turn on verbose debug-logging, I will try this next.....or maybe you (or anyone else) have a suggestion?
    That was gonna be my next suggestion, remove the hash (#) in front of
    #Hellanzb.DEBUG_MODE = '/opt/var/log/hellanzb-debug.log' and change the path to a directory that exists.
    Now, if you start hellanzb, it starts logging debug info to the file specified.

  11. #11

    Cool Weird...

    DrChair,

    Well, sometimes a mistake will teach you something....
    I tried starting Hellanzb.py with the paramters -d (debug).
    Seems this doesn't really start debug-mode (I'll try your suggestion of editing the conf-file later), but it also runs hellanzb un-deamonized. And now the screens shows it's actually downloading. So, it all seems to work except when running it daemonized, as it wil stay on QUEUED.

    Will try the debug-mode tonigt.

  12. #12
    I makes kind of sense...

    the option -d (debug) should be followed by the path to the logfile, so it's ignored in your case. And because you didn't specify -D (Daemonize), it uses the console as a gui, so you see it downloading.

    to start debugging the daemonized mode, you could also do:
    hellanzb.py -D -d /opt/var/log/hellanzb-debug.log

  13. #13
    Quote Originally Posted by raas View Post
    if the downloaded package contains 'funky' characters like hyphens, spaces, underscores etc. it does not extract the package.

    I think it has something to do with the unrar command not being called correct from within HellaNZB.. something like:

    unrar e downloaded-package.rar

    instead of:

    unrar e 'downloaded-package.rar'
    That's not the case. I have downloaded lots of packages with 'funky' characters, and they all unpack just fine.
    A quote from the debug-log also proves this:
    Code:
    2007-11-27 13:22:46,241 spawnProcess THREAD ID: 2051  (/opt/bin/unrar l -y -p- -- "/tmp/harddisk/hellanzb/nzb/daemon.processing/Bla.Bla- Bla.Bla.Bla.u4e/Bla.Bla- Bla.Bla.Bla.u4e.part01.rar")
    The only time a package I downloaded didn't unpack, was when the first.par2 file was damaged, so it couldn't verify. Perhaps hellanzb should also download the first non-empty par2 file, to prevent this behavior.

  14. #14

    Thumbs up Got it going!

    Quote Originally Posted by DrChair View Post
    I makes kind of sense...

    the option -d (debug) should be followed by the path to the logfile, so it's ignored in your case. And because you didn't specify -D (Daemonize), it uses the console as a gui, so you see it downloading.

    to start debugging the daemonized mode, you could also do:
    hellanzb.py -D -d /opt/var/log/hellanzb-debug.log
    DrChair,
    Thanks for the tips, I now have it running exactly like wanted to.
    My WL-HDD is happily downloading files from usenet while my noisy, energy-sucking PC can be turned of at night.

    Thanks again!

    Oh,
    a few tips for those installing HellaNZB:
    • Use the -force-reinstall parameter of ipkg if installation doesn't go right the first time
    • Install Nano to view/edit your files on Linux
    • If you've used the tutorial in this thread, make sure you set your download path to /tmp/harddisk/.... otherwise you'll run out of diskspace pretty quick.
    • READ THIS THREAD


    So, next up: installing a web frontend for monitoring progress....
    Last edited by Jeroen van Omme; 03-12-2007 at 12:05.

  15. #15

    Wink Me again

    Just installed Zussaweb, with lighttpd and fcgi-php (called php-fcgi in the package listing!).
    Did the modifications noted in this thread, but when I try to open
    http://192.168.1.210:8081/zussaweb/
    it returns a
    Fault: Code: 6 Reason 'No data received from server.'

    Any suggestions?

Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •