Bugman1400 Posted November 13, 2016 Share Posted November 13, 2016 I rebooted the server several times before but, for some reason, a reboot just now fixed my Save issue....all is well! Quote Link to comment
gl3nn Posted November 16, 2016 Share Posted November 16, 2016 is it possible to install ffmpeg into this docker? i'm asking this for nzbtomedia. Quote Link to comment
CptJames32 Posted November 17, 2016 Share Posted November 17, 2016 i keep getting the error "You require permission from Unix\nobody to make changes to this file." I changed the security>umask to 0000. and it still didn't help with the new files. Quote Link to comment
hernandito Posted December 11, 2016 Share Posted December 11, 2016 Super-Newbie (w/ NZBGEt) Question: Trying to switch from Sab to NZBGet because I get a lot of failed downloads lately with Sab/Sickrage. I just did a test to download an episode in NZBGet, and it did not post process in Sickrage. Download was extracted and placed in the proper directory as when using with Sab. I was not using any pp script in Sab. Do I need to add a post processing script to NZBGet to process the episode after downloading? Thanks in advance. H. Quote Link to comment
Squid Posted December 11, 2016 Share Posted December 11, 2016 Super-Newbie (w/ NZBGEt) Question: Trying to switch from Sab to NZBGet because I get a lot of failed downloads lately with Sab/Sickrage. I just did a test to download an episode in NZBGet, and it did not post process in Sickrage. Download was extracted and placed in the proper directory as when using with Sab. I was not using any pp script in Sab. Do I need to add a post processing script to NZBGet to process the episode after downloading? Thanks in advance. H. Sick should do all the pp. You probably got something wrong in the paths http://lime-technology.com/forum/index.php?topic=40937.msg488507#msg488507 Explains how to set the paths up using sonarr as an example (IMO better than sick) Quote Link to comment
hernandito Posted December 12, 2016 Share Posted December 12, 2016 Sick should do all the pp. You probably got something wrong in the paths http://lime-technology.com/forum/index.php?topic=40937.msg488507#msg488507 Explains how to set the paths up using sonarr as an example (IMO better than sick) Thank you Squid. I think the issue was a download that I marked as failed... Will try to see how it performs with tonight's downloads. Thanks again, H. Quote Link to comment
Katherine Posted December 25, 2016 Share Posted December 25, 2016 WARNING Sat Dec 24 2016 19:45:23 Non-nzbget request received on port 6789 from 189.0.84.51 WARNING Sat Dec 24 2016 19:45:23 Non-nzbget request received on port 6789 from 189.0.84.51 WARNING Sat Dec 24 2016 19:42:19 Non-nzbget request received on port 6789 from 181.177.140.147 WARNING Sat Dec 24 2016 19:42:19 Non-nzbget request received on port 6789 from 181.177.140.147 WARNING Sat Dec 24 2016 19:33:43 Non-nzbget request received on port 6789 from 132.255.88.43 WARNING Sat Dec 24 2016 19:33:42 Non-nzbget request received on port 6789 from 132.255.88.43 WARNING Sat Dec 24 2016 19:30:26 Non-nzbget request received on port 6789 from 187.18.225.102 WARNING Sat Dec 24 2016 19:30:25 Non-nzbget request received on port 6789 from 187.18.225.102 I'm getting a bunch of these messages. Does anyone know what is triggering this? Is this linked to ControlIP or AuthorizedIP? My current setting: ControlIP: 0.0.0.0 AuthorizedIP: 127.0.0.1 Quote Link to comment
CHBMB Posted December 25, 2016 Share Posted December 25, 2016 WARNING Sat Dec 24 2016 19:45:23 Non-nzbget request received on port 6789 from 189.0.84.51 WARNING Sat Dec 24 2016 19:45:23 Non-nzbget request received on port 6789 from 189.0.84.51 WARNING Sat Dec 24 2016 19:42:19 Non-nzbget request received on port 6789 from 181.177.140.147 WARNING Sat Dec 24 2016 19:42:19 Non-nzbget request received on port 6789 from 181.177.140.147 WARNING Sat Dec 24 2016 19:33:43 Non-nzbget request received on port 6789 from 132.255.88.43 WARNING Sat Dec 24 2016 19:33:42 Non-nzbget request received on port 6789 from 132.255.88.43 WARNING Sat Dec 24 2016 19:30:26 Non-nzbget request received on port 6789 from 187.18.225.102 WARNING Sat Dec 24 2016 19:30:25 Non-nzbget request received on port 6789 from 187.18.225.102 I'm getting a bunch of these messages. Does anyone know what is triggering this? Is this linked to ControlIP or AuthorizedIP? My current setting: ControlIP: 0.0.0.0 AuthorizedIP: 127.0.0.1 You got that port open by any chance on your router? Quote Link to comment
Techn0mancer Posted December 25, 2016 Share Posted December 25, 2016 I started seeing the same message so I closed the port Quote Link to comment
Katherine Posted December 27, 2016 Share Posted December 27, 2016 Removing 6789 from the router's port forwarding list fixed the problem. Thank you CHBMB and Techn0mancer. Quote Link to comment
CHBMB Posted December 31, 2016 Share Posted December 31, 2016 Removing 6789 from the router's port forwarding list fixed the problem. Thank you CHBMB and Techn0mancer. You want to access it from outside your LAN and I'd recommend setting up a reverse proxy with our letsencrypt container. Quote Link to comment
bobmagnuson Posted January 16, 2017 Share Posted January 16, 2017 Would it be possible to get MKVToolNix included in this container?? Would be handy for post processing scripts. Quote Link to comment
littlered Posted January 17, 2017 Share Posted January 17, 2017 As of the last few days, I keep getting an error "Low disk space on /downloads/dst. Pausing download" and "Low disk space on /downloads/inter. Pausing download" and the downloads keep pausing. My docker container is located on a cache drive and I do have a lot of space left on it. In the docker container log, I see this error: [ERROR] Error saving diskstate: Could not rename file /config/queue/stats.new to /config/queue/stats: No space left on device Thank you in advance! Quote Link to comment
trurl Posted January 17, 2017 Share Posted January 17, 2017 As of the last few days, I keep getting an error "Low disk space on /downloads/dst. Pausing download" and "Low disk space on /downloads/inter. Pausing download" and the downloads keep pausing. My docker container is located on a cache drive and I do have a lot of space left on it. In the docker container log, I see this error: [ERROR] Error saving diskstate: Could not rename file /config/queue/stats.new to /config/queue/stats: No space left on device Thank you in advance! Tools - Diagnostics Quote Link to comment
littlered Posted January 17, 2017 Share Posted January 17, 2017 As of the last few days, I keep getting an error "Low disk space on /downloads/dst. Pausing download" and "Low disk space on /downloads/inter. Pausing download" and the downloads keep pausing. My docker container is located on a cache drive and I do have a lot of space left on it. In the docker container log, I see this error: [ERROR] Error saving diskstate: Could not rename file /config/queue/stats.new to /config/queue/stats: No space left on device Thank you in advance! Tools - Diagnostics Here is the diagnostics file. unraid-diagnostics-20170116-1304.zip Quote Link to comment
trurl Posted January 17, 2017 Share Posted January 17, 2017 As of the last few days, I keep getting an error "Low disk space on /downloads/dst. Pausing download" and "Low disk space on /downloads/inter. Pausing download" and the downloads keep pausing. My docker container is located on a cache drive and I do have a lot of space left on it. In the docker container log, I see this error: [ERROR] Error saving diskstate: Could not rename file /config/queue/stats.new to /config/queue/stats: No space left on device Thank you in advance! Tools - Diagnostics Here is the diagnostics file. Check_Disk_Filesystems-Drives_formatted_with_BTRFS Quote Link to comment
littlered Posted January 17, 2017 Share Posted January 17, 2017 As of the last few days, I keep getting an error "Low disk space on /downloads/dst. Pausing download" and "Low disk space on /downloads/inter. Pausing download" and the downloads keep pausing. My docker container is located on a cache drive and I do have a lot of space left on it. In the docker container log, I see this error: [ERROR] Error saving diskstate: Could not rename file /config/queue/stats.new to /config/queue/stats: No space left on device Thank you in advance! Tools - Diagnostics Here is the diagnostics file. Check_Disk_Filesystems-Drives_formatted_with_BTRFS I ran the tool on the cache drive and this is the result: scrub status for 15f4a7a5-7e67-4411-af76-2791c4b724b6 scrub started at Mon Jan 16 13:32:20 2017 and finished after 00:01:58 total bytes scrubbed: 48.51GiB with 0 errors Quote Link to comment
trurl Posted January 17, 2017 Share Posted January 17, 2017 Your previous diagnostics was showing lots of cache drive full messages in syslog. Also df was showing it 100% used. You may have to reformat it. Quote Link to comment
littlered Posted January 17, 2017 Share Posted January 17, 2017 How do I go about doing that? Would I lose the docker configurations? Your previous diagnostics was showing lots of cache drive full messages in syslog. Also df was showing it 100% used. You may have to reformat it. Quote Link to comment
trurl Posted January 17, 2017 Share Posted January 17, 2017 You can just use the replace cache drive procedure from the FAQ: How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) except instead of replacing the drive you can change its filesystem to get it formatted. Quote Link to comment
littlered Posted January 17, 2017 Share Posted January 17, 2017 Should I keep using btrfs for the cache or change it to xfs? What would you recommend? You can just use the replace cache drive procedure from the FAQ: How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) except instead of replacing the drive you can change its filesystem to get it formatted. Quote Link to comment
trurl Posted January 17, 2017 Share Posted January 17, 2017 Should I keep using btrfs for the cache or change it to xfs? What would you recommend? You can just use the replace cache drive procedure from the FAQ: How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) except instead of replacing the drive you can change its filesystem to get it formatted. If you expect to add additional cache drives in the future then btrfs is the only choice. If you will only use a single cache drive then many people here think XFS is more reliable. Quote Link to comment
littlered Posted January 17, 2017 Share Posted January 17, 2017 Ok, thanks! Should I keep using btrfs for the cache or change it to xfs? What would you recommend? You can just use the replace cache drive procedure from the FAQ: How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) except instead of replacing the drive you can change its filesystem to get it formatted. If you expect to add additional cache drives in the future then btrfs is the only choice. If you will only use a single cache drive then many people here think XFS is more reliable. Quote Link to comment
littlered Posted January 18, 2017 Share Posted January 18, 2017 Quick question - I am going through the steps as per the FAQ, but I have Docker user share. Should I also set it Use Cache Disk to 'Yes'? You can just use the replace cache drive procedure from the FAQ: How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) except instead of replacing the drive you can change its filesystem to get it formatted. Quote Link to comment
trurl Posted January 18, 2017 Share Posted January 18, 2017 Quick question - I am going through the steps as per the FAQ, but I have Docker user share. Should I also set it Use Cache Disk to 'Yes'? If you go to the settings page for a user share and turn on Help it will explain the various settings including the use cache setting. The Help button is a toggle and will stay on until you turn it off. If it is turned on the webUI will show you help for any of its pages. Try that and let me know if you don't understand why Yes is the wrong answer. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.