Jump to content

Viperkc

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Viperkc

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Confirmed working fine here now. thank you
  2. todays update broke docker. reverted back to previous and all good. thanks
  3. That worked perfectly. Thank you
  4. Hi great plugin! I am running 6.7.2 and get this error when installing the plugin: Warning: SQLite3::query(): Unable to prepare statement: 1, no such table: settings_group in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 1062 Fatal error: Uncaught Error: Call to a member function fetchArray() on boolean in /usr/local/emhttp/plugins/disklocation/pages/system.php:1064 Stack trace: #0 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 1064 Thanks
  5. Sorry i forgot to update. It was actually Radaar changing file dates randomly as it did a scan. There is a setting there that can turn that off and when i did it stopped moving things to my uploads folder. Regarding the not moving to folder problem that ended up being a typo in my upload script. All is working perfectly now. Thanks
  6. New setup here working great so far thanks to your awesome scripts. And BIG thanks to Kaizac for his awesome help in getting me up and running. So i have one question, i am moving my library manually to the upload folder a little bit at a time, when the first batch was uploading i started to notice more files automatically showing up in the upload folder. I think this might be due to the --min-age 30m setting, but could be wrong. If that is causing it to auto move files can i remove it? until i get the manual part done? I also noticed when it did the move my files were not put in my media folders (IE: Movies and TV Shows) they were just dumped in the root folder on my gdrive. Thanks
  7. Hi Everyone Trying to set this up, i created the config and gdrives test fine. The next step in the guide says to: touch mountcheck When i do this i don't see anything created on my grives? Is this normal and OK to proceed with next steps or should i stop and figure out why i don't see anything. I get no errors when doing touch mountcheck it just returns to command line. Also what if any shares do i need to create in unraid before doing this or do the scripts do for me automagically? thanks
  8. Edit the container and paste this under repository: binhex/arch-sabnzbdvpn:2.3.8-1-01 When he announces the fix for be sure to change it back to binhex/arch-sabnzbdvpn This way you get furture updates
  9. That version is the working version. If you updated yesterday you would be on 2.3.8 (daf9f50) This is the version we had problems with. I reverted back to 0dd1f64 and it works fine.
  10. OK thanks, I rolled back one version and all is working fine now. Will check later for an update
  11. I saw there was an update today so i updated. Now Radarr and Sonarr cannot connect to SAB, I have ran the same configuration for more then a year and never had this problem. Any ideas what i might check? Here are logs if this might help 2019-05-03 20:00:13,740 DEBG 'watchdog-script' stdout output: [info] Attempting to start SABnzbd... 2019-05-03 20:00:13,771 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22497825666760 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stdout)> 2019-05-03 20:00:13,771 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22497825666688 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stderr)> 2019-05-03 20:00:13,771 INFO exited: privoxy-script (exit status 0; expected) 2019-05-03 20:00:13,772 DEBG received SIGCLD indicating a child quit 2019-05-03 20:00:43,694 DEBG 'watchdog-script' stdout output: [warn] Wait for SABnzbd process to start aborted, too many retries [warn] Showing output from command before exit... 2019-05-03 20:00:44,368 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22497825669064 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stdout)> 2019-05-03 20:00:44,368 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22497825666832 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stderr)> 2019-05-03 20:00:44,368 INFO exited: watchdog-script (exit status 1; not expected) 2019-05-03 20:00:44,369 DEBG received SIGCLD indicating a child quit
  12. I am having the same issue. When mover runs all trans coded Plex streams buffer. Has not been this way in the past, it could have started when i installed my P2000 and started trans-coding with the Nvidia version of Unraid. But i am not certain of that. I see no noticeable higher CPU or Memory usage when this happens. Thanks
  13. Yes this would be awesome if we could passthru Nvidia to this docker. One other question is 0.0.1-beta3 the latest version? I have josh5/unmanic:latest set for repository. Thanks for the awesome docker!
  14. Thats my fix also ATM. I exclusively only use binhex dockers.
  15. The problem only exists when using the docker in this topic. Which i prefer over the others. The transcode to RAM method works fine in other Plex dockers so there would be no need to post in the topic i linked.