SABnzbd Forums

Posted: **May 21st, 2016, 4:04 am**

The problem still exists for me, please see below from starting the application on the command line.

[/etc/init.d] # ./sabnzbd.sh start
x86_64
Performing SABnzbdplus prestartup checks at Sat May 21 17:02:43 BST 2016...
Checking for git... Found!
HEAD is now at c50957d V10.14 ready for merge
Already up-to-date.
Checking environment
Checking if all configured directories exist....... Done
Creating Symbolic links for required utils. Done
Done
Already up-to-date.
Starting SABnzbdplus Done (Sat May 21 17:03:05 BST 2016)
[/etc/init.d] #

Posted: **May 21st, 2016, 5:08 am**

That commit it refers to belongs to nzbToMedia, so somehow it is not updating sabnzbd.
Weird! Maybe something in the script?

You are also on 1.1.x when you go into the Config?

Posted: **May 21st, 2016, 7:28 am**

It's now working, thanks for all the help.

Posted: **May 21st, 2016, 7:36 am**

Ok, what did you do?

Actually, I'm now pretty confused by this QNAP package. I tried to use these "Control Tags" (text files in the "log" directory with specific names that should trigger the package to do certain things, e.g. loading a given source file instead of going to git, etc.) and it's ignoring them. I looked at the sabnzbd.sh script that starts/stops the server and checks for updates. Interestingly I couldn't find any code that would deal with such control tags (maybe I missed it ...).

What I found is the following code it uses to load the version from git:

Code: Select all

        if [ ! -d ${QPKG_DIR}/sabnzbd/.git ]; then
                git clone https://github.com/sabnzbd/sabnzbd.git ${QPKG_DIR}/sabnzbd || git clone git://github.com/sabnzbd/sabnzbd.git ${QPKG_DIR}/sabnzbd
        fi
        cd ${QPKG_DIR}/sabnzbd
        git pull

It looks like this pulls the dev branch with the latest V1.1.x "alpha" version and not the latest stable version. Does somebody know how to re-write this to pull the latest stable version?

Posted: **May 21st, 2016, 7:56 am**

I found in the .git directory under sabnzbd the file "config". It contains this info:
====
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = https://github.com/sabnzbd/sabnzbd.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "develop"]
remote = origin
merge = refs/heads/develop
=====
This file seems to set were the current version is obtained from. But i'm not at all experienced with linux or python, so i don't know if setting branch to "0.1.x" does the job or crashes the whole thing at the next restart...

Seems to be a discussion for the qnap forum, i don't know if this place is appropriate for this discussion...

Posted: **May 21st, 2016, 8:07 am**

Ah, interesting, good catch!
I think we're in exactly the right forum for this because the sabnzbd developers can for sure tell us which branch is the correct one for the latest stable version

Posted: **May 21st, 2016, 10:05 am**

"1.0.x"

But soon we will have a "1.1.x" branch for the next release (beta at first). We're going to make the master branch the stable one, but that one is stuck on 1.0.0 for now. Work in progress

Asking the creator of the wrapper to use master in the future.

Posted: **May 22nd, 2016, 3:31 am**

Ok, I'm at the end of my possibilities as I have no clue about git.
I tried the following two changes to the git config file:

Code: Select all

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = https://github.com/sabnzbd/sabnzbd.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "1.0.x"]
        remote = origin
        merge = refs/heads/1.0.x

Code: Select all

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = https://github.com/sabnzbd/sabnzbd.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "1.0.x"]
        remote = origin
        merge = refs/heads/develop

Both ended with the following error messages:

Code: Select all

There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> develop

I don't know if this is regular git handling or a specific setup to the wrapper script. So I guess we have to take it to the QNAP forum and ask Clinton.Hall for his help. It's not a sabnzbd problem, of course, but related to the wrapper script.

Posted: **May 23rd, 2016, 8:59 am**

@safihre @Sirupflex:

Clinton.Hall has put an update for the sabnzbd wrapper on the qnap forum two hours ago. The updates pulls from the masterbranch.
So when the stable Sabnzbd version will be located in the masterbranch, the wrapper pulls the latest stable version.

Thx for your efforts on this!

Posted: **May 23rd, 2016, 2:23 pm**

I'm having a similar issue on a Synology DS415+. The DL starts off at a few KBs/sec, then goes up to about 6-8MB, then starts plummeting, down to zero, and every download fails. I have 2 servers, Astraweb, and Usenetserver. Both SSL (previously they were both on 119). My SAB version is the "test" Syno Community 1.0, but it was previously the .70 version I think. Neither are working.

My ISP is Time Warner, and I'm wondering if the Comcast merger has anything to do with this?

My speed tests results are as expected....200/20. Up until a couple of days ago, I was hitting 20-30MB down on SAB...now everything crawls to a fail.

Any ideas?

Posted: **May 23rd, 2016, 3:50 pm**

Try going back to non ssl version, so on port 119. Does that improve it in any way?

However, your problem is different from the others in this topic.

Posted: **May 23rd, 2016, 4:28 pm**

Sorry to have hijacked...I didn't realize the issue was different since the symptoms sounded so similar.

I had only changed to SSL after 119 started slowing down. Switching back changed nothing.

EDIT, it looks like I got about 25 dead nzbs, strangely all unrelated....the perfect storm of expired or passworded files that made me think something was very wrong.

my speeds are still slower than normal, but not anywhere near as bad as i had thought.

Posted: **May 24th, 2016, 10:34 am**

F.Saucer wrote: Clinton.Hall has put an update for the sabnzbd wrapper on the qnap forum two hours ago. The updates pulls from the masterbranch.
So when the stable Sabnzbd version will be located in the masterbranch, the wrapper pulls the latest stable version.

Thx for your efforts on this!

Great news, thanks for all your efforts, too!

Is there a possibility to find out once the master branch has v1.0.2? If I understand correctly, the master branch has v1.0.0 at the moment and I don't want to go back to this version. There's no hurry for me as the current V1.1.x version runs fine at the moment.

Posted: **October 30th, 2016, 7:27 pm**

Where is the git config file located for Sabnzbd?

Posted: **October 31st, 2016, 2:43 am**

Iceman24 wrote:Where is the git config file located for Sabnzbd?

The git config file?
I don't understand the question.

SABnzbd Forums

Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%

Re: Downloads Randomly Slow Down to 0%