Jump to content
binhex

[Support] binhex - NZBGet

151 posts in this topic Last Reply

Recommended Posts

Overview: Support for Docker image arch-nzbget in the binhex repo.

Application: NZBGet - http://nzbget.net/

Docker Hub: https://hub.docker.com/r/binhex/arch-nzbget/

GitHub: https://github.com/binhex/arch-nzbget

 

If you appreciate my work, then please consider buying me a beer  :D

 

btn_donate_SM.gif

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

Edited by binhex

Share this post


Link to post

Thanks for all the hard work.

 

Donated

Share this post


Link to post

Thanks for all the hard work.

 

Donated

 

Thank you, i appreciate the donation.

Share this post


Link to post

Hi,

 

I have problem with unpack and moving files in nzbget. I downloading it to MainDir on SSD drive after verify it should unpack and move file to shares /mnt/user/Incoming but I have error with  that.

 

ERROR Mon Mar 07 2016 21:09:52 Unpack for xxx.2005.720p.BrRip.x264-YIFY failed.

ERROR Mon Mar 07 2016 21:09:43 Could not delete temporary directory /mnt/user/Incoming/xxx.2005.720p.BrRip.x264-YIFY/_unpack:

ERROR Mon Mar 07 2016 21:09:43 Unrar error code: 10

ERROR Mon Mar 07 2016 21:09:43 Could not create directory /mnt/user/Incoming/xxx.2005.720p.BrRip.x264-YIFY/_unpack: could not create directory /mnt/user:

 

Thats like docker don't see shares. I have try  lot of Volume Mappings but with no result.

 

/config  /mnt/cache/.Apps/

/data  /mnt/cache/.Apps/Downloads/

/DestDir  /mnt/user/Incoming/

 

SAB crasches and freezes unraid on large files and speeds and i'm looking for alternate nzb client. I se nzbget is much lighter and more responsivle.

I'm really not good with linux systems... and I need some help.

 

Share this post


Link to post

Hi,

 

I have problem with unpack and moving files in nzbget. I downloading it to MainDir on SSD drive after verify it should unpack and move file to shares /mnt/user/Incoming but I have error with  that.

 

ERROR Mon Mar 07 2016 21:09:52 Unpack for xxx.2005.720p.BrRip.x264-YIFY failed.

ERROR Mon Mar 07 2016 21:09:43 Could not delete temporary directory /mnt/user/Incoming/xxx.2005.720p.BrRip.x264-YIFY/_unpack:

ERROR Mon Mar 07 2016 21:09:43 Unrar error code: 10

ERROR Mon Mar 07 2016 21:09:43 Could not create directory /mnt/user/Incoming/xxx.2005.720p.BrRip.x264-YIFY/_unpack: could not create directory /mnt/user:

 

Thats like docker don't see shares. I have try  lot of Volume Mappings but with no result.

 

/config  /mnt/cache/.Apps/

/data  /mnt/cache/.Apps/Downloads/

/DestDir  /mnt/user/Incoming/

 

SAB crasches and freezes unraid on large files and speeds and i'm looking for alternate nzb client. I se nzbget is much lighter and more responsivle.

I'm really not good with linux systems... and I need some help.

 

Ok problem solved.

 

In Volume Mapping add

 

/media /mnt/user/Incoming    thats in my case

 

and in nzbget

 

DestDir /media

Share this post


Link to post

I'm getting a lot of these entries in the logs:

 

Sun Aug 14 16:52:40 2016 ERROR Binding socket failed for 0.0.0.0: ErrNo 98, Address already in use

Sun Aug 14 16:52:40 2016 ERROR Binding socket failed for 0.0.0.0: ErrNo 98, Address already in use

Sun Aug 14 16:52:41 2016 ERROR Binding socket failed for 0.0.0.0: ErrNo 98, Address already in use

Sun Aug 14 16:52:41 2016 ERROR Binding socket failed for 0.0.0.0: ErrNo 98, Address already in use

 

This is because there are two copies of NZBGet running in the docker:

 

# docker exec -ti binhex-nzbget /bin/bash

[root@b9bc0eb389a2 /]# ps -aux

USER      PID %CPU %MEM    VSZ  RSS TTY      STAT START  TIME COMMAND

root        1  0.1  0.0  15760  3280 ?        Ss  16:52  0:00 /bin/bash /root/init.sh

root        12  0.8  0.1  98144 18832 ?        S    16:52  0:00 /usr/bin/python2 /usr/bin/supervisord -c /etc/supervisor.conf -n

nobody      17  0.7  0.0 247496  3460 ?        Ssl  16:52  0:00 /usr/bin/nzbget -D -c /config/nzbget.conf

nobody      30  0.7  0.0 247496  3588 ?        Ssl  16:52  0:00 /usr/bin/nzbget -D -c /config/nzbget.conf

root        41  0.4  0.0  15892  3508 ?        Ss  16:52  0:00 /bin/bash

root        45  0.0  0.0  34616  3080 ?        R+  16:52  0:00 ps -aux

 

How do we fix this?

Share this post


Link to post

How do we fix this?

 

there are a few different ways to go about it; figured i'd just open an issue - for now you can just kill one of the processes after bringing it up so it doesn't continually try to start.

Share this post


Link to post

How do we fix this?

 

there are a few different ways to go about it; figured i'd just open an issue - for now you can just kill one of the processes after bringing it up so it doesn't continually try to start.

 

This must of changed, ok ive now tweaked the script so that it runs as a foreground process again, yes this does mean it will write the chatter to the supervisord.log, will have to see how chatty it really is, if its nasty i will have to redirect stdout to a file. so if you do an update you should see this change now.

Share this post


Link to post

Just updated today, and now the docker log is getting spammed with this:

2016-10-07 22:09:27,019 DEBG 'nzbget' stdout output:
[1d[37m[44m8[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:28,029 DEBG 'nzbget' stdout output:
[1d[37m[44m9[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:29,044 DEBG 'nzbget' stdout output:
[1d[37m[44m40[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:30,054 DEBG 'nzbget' stdout output:
[1d[37m[44m1[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:31,061 DEBG 'nzbget' stdout output:
[1d[37m[44m2[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:32,071 DEBG 'nzbget' stdout output:
[1d[37m[44m3[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:33,078 DEBG 'nzbget' stdout output:
[1d[37m[44m4[24;80H(B[m[39;49m[37m[40m

 

New entry every second. Is anyone else seeing this?

I did change  Setting/Logging/WriteLog  within nzbget from 'Append' to 'Rotate', but no other changes made apart from this.

I've reverted that config change but the logs are still getting spammed.

 

 

Share this post


Link to post

Just updated today, and now the docker log is getting spammed with this:

2016-10-07 22:09:27,019 DEBG 'nzbget' stdout output:
[1d[37m[44m8[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:28,029 DEBG 'nzbget' stdout output:
[1d[37m[44m9[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:29,044 DEBG 'nzbget' stdout output:
[1d[37m[44m40[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:30,054 DEBG 'nzbget' stdout output:
[1d[37m[44m1[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:31,061 DEBG 'nzbget' stdout output:
[1d[37m[44m2[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:32,071 DEBG 'nzbget' stdout output:
[1d[37m[44m3[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:33,078 DEBG 'nzbget' stdout output:
[1d[37m[44m4[24;80H(B[m[39;49m[37m[40m

 

New entry every second. Is anyone else seeing this?

I did change  Setting/Logging/WriteLog  within nzbget from 'Append' to 'Rotate', but no other changes made apart from this.

I've reverted that config change but the logs are still getting spammed.

 

ok so it looks like it does write lots of crap to stdout in console mode, i think the timestamps your seeing are triggered from the auto refresh for nzbget web interface. i have tweaked the image again and it now closes stdout, ive also created /data/dst as for some bizarre reason it doesnt create it, even though thats where the logs go, sounds like a bug to me but hey its now fixed for the docker image, so please pull down the latest and give it a whirl.

Share this post


Link to post

Just updated today, and now the docker log is getting spammed with this:

2016-10-07 22:09:27,019 DEBG 'nzbget' stdout output:
[1d[37m[44m8[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:28,029 DEBG 'nzbget' stdout output:
[1d[37m[44m9[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:29,044 DEBG 'nzbget' stdout output:
[1d[37m[44m40[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:30,054 DEBG 'nzbget' stdout output:
[1d[37m[44m1[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:31,061 DEBG 'nzbget' stdout output:
[1d[37m[44m2[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:32,071 DEBG 'nzbget' stdout output:
[1d[37m[44m3[24;80H(B[m[39;49m[37m[40m
2016-10-07 22:09:33,078 DEBG 'nzbget' stdout output:
[1d[37m[44m4[24;80H(B[m[39;49m[37m[40m

 

New entry every second. Is anyone else seeing this?

I did change  Setting/Logging/WriteLog  within nzbget from 'Append' to 'Rotate', but no other changes made apart from this.

I've reverted that config change but the logs are still getting spammed.

 

ok so it looks like it does write lots of crap to stdout in console mode, i think the timestamps your seeing are triggered from the auto refresh for nzbget web interface. i have tweaked the image again and it now closes stdout, ive also created /data/dst as for some bizarre reason it doesnt create it, even though thats where the logs go, sounds like a bug to me but hey its now fixed for the docker image, so please pull down the latest and give it a whirl.

Success! Logs are nice and clean again. Thanks for the quick fix, and thanks for putting so much effort into these dockers, it's very much appreciated!

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post

I think nzbget is better...

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

Hey Guys, After upgrading from 6.1.8 to 6.2.4 I can no longer connect to :6789. I keep getting connection refused. My other dockers work fine but just not Nzb get. Please help!

Share this post


Link to post

Hey Guys, After upgrading from 6.1.8 to 6.2.4 I can no longer connect to :6789. I keep getting connection refused. My other dockers work fine but just not Nzb get. Please help!

 

Tried a browser cache clear?  Or try it from a different computer/phone.

 

Post your docker run command as well.  Link in my sigs.

 

Docker logs would be relevant also.

Share this post


Link to post

Hey Guys, After upgrading from 6.1.8 to 6.2.4 I can no longer connect to :6789. I keep getting connection refused. My other dockers work fine but just not Nzb get. Please help!

 

Another thought, there was some "stuff" you had to do when moving from unraid 6.1.x to 6.2.x, i think it was in the release notes, it def was on the forum release posts, and im 100% sure it was related to blowing away the docker image file completely due to docker engine changes.

Share this post


Link to post

Hey Guys,

 

So I just decided to created a new docker image to see if that would help the issue. I placed it in the new recommended spot /user/system

 

but I am getting the following error in the log

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[iNFO] nzbget 17.1 server-mode
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is  >= this->size() (which is 
[iNFO] nzbget 17.1 server-mode
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is  >= this->size() (which is 
[iNFO] nzbget 17.1 server-mode

it loops the terminate call until I shut it down.

 

The run command

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name="binhex-nzbget" --net="bridge" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 7890:6789/tcp -v "/mnt/user/Completed Downloads/":"/data":rw -v "/mnt/user/appdata/nzbgetbinhex":"/config":rw binhex/arch-nzbget
ce472aefad6c5032fcbbeca463b5513822a365eb2eae28156f1ec044fca8f638

The command finished successfully!

 

the -p 7890 is because I was trying to see if it was a port issue... I have just changed it but still nothing.

 

Thanks for your replies guys, my mom and girlfriend are getting antsy without their precious TV!

 

 

Share this post


Link to post

Hey Guys,

 

So I just decided to created a new docker image to see if that would help the issue. I placed it in the new recommended spot /user/system

 

but I am getting the following error in the log

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[iNFO] nzbget 17.1 server-mode
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is  >= this->size() (which is 
[iNFO] nzbget 17.1 server-mode
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is  >= this->size() (which is 
[iNFO] nzbget 17.1 server-mode

it loops the terminate call until I shut it down.

 

The run command

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name="binhex-nzbget" --net="bridge" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 7890:6789/tcp -v "/mnt/user/Completed Downloads/":"/data":rw -v "/mnt/user/appdata/nzbgetbinhex":"/config":rw binhex/arch-nzbget
ce472aefad6c5032fcbbeca463b5513822a365eb2eae28156f1ec044fca8f638

The command finished successfully!

 

the -p 7890 is because I was trying to see if it was a port issue... I have just changed it but still nothing.

 

Thanks for your replies guys, my mom and girlfriend are getting antsy without their precious TV!

 

the only thing that looks even remotely strange is this:-

 

-v "/mnt/user/Completed Downloads/":"/data":rw 

 

so the fact that the folder on the host side has a space in it, i mean docker should cope ok with this and it is wrapped in double quotes so in theory it should be ok, but if possible just to test it isnt this you could point /data at a path with no spaces in, other than that the docker create command looks fine to me.

 

also if you have existing configs for this docker just rename the config folder and try with a blank config, maybe its some corruption of a config file and/or database stored in the config folder (dunno how nzbget stores its settings)

Share this post


Link to post

So pointing to /data did work and then going back to completed downloads rebroke it. I did however fix the problem by changing the mnt/user/completed downloads to mnt/user/completed\ downloads . Its weird because I am selecting the folder from the dropdown menu, however I had to place the \ to make up for the space!

 

So weird.... Thanks guys for the help and continued support in the forum!!

 

Have a great weekend :)

 

Tayshun

Share this post


Link to post

So pointing to /data did work and then going back to completed downloads rebroke it. I did however fix the problem by changing the mnt/user/completed downloads to mnt/user/completed\ downloads . Its weird because I am selecting the folder from the dropdown menu, however I had to place the \ to make up for the space!

 

So weird.... Thanks guys for the help and continued support in the forum!!

 

Have a great weekend :)

 

Tayshun

 

You should report this in the defect reports subforum.  This isn't expected behaviour,

Share this post


Link to post

hi, need some assistance from folks.. bit of a newb...

 

lately my sonarr shows appear to be downloading successfully but the size of the file is way off. eg. nzbget says its a 2.8GB file when it gets moved to my final tv library the file is say only half or less than half the size of what nzbget has reported as downloaded. i can take the same file and then manually download it but this time not allowing nzbget to extract but choosing to do it myself manually and the file size is accurate. has anyone seen this, any suggestions of where to look for what the issue may be...

 

i am running nzbget 17.1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now