Jump to content

deusxanime

Members
  • Content Count

    117
  • Joined

  • Last visited

Community Reputation

13 Good

About deusxanime

  • Rank
    Advanced Member
  • Birthday July 3

Converted

  • Gender
    Male

Recent Profile Visitors

746 profile views
  1. Plex internally makes it's own backups of the db as well I believe. In the same directory as the main db but appended with the date, like "com.plexapp.plugins.library.db-2020-05-02". Have you tried to go back to one of those using these instructions? Hopefully the backups aren't corrupt as well.
  2. I ran into a couple annoyances with the update over the weekend (v0.3.13) and thought I'd post here to let others be aware of them: 1. I had a download that didn't seem to be getting processed. It turns out there was a bug with the scheduler that it seems like the frequency you set to post-process your completed download directory was ignored and just sets to run every 24h instead. Manually forcing a post-process worked though. Github issue thread. Looks like they've already put up a new release v0.3.14 with a fix and it has been applied to the docker image. Just run another update to your container in unRAID web interface to fix it. 2. Luckily(?) due to the above I ran that manual post-process and found out about this other change. I run a post-processing shell (bash) script and I noticed that it didn't work when I looked at the post-processing log output. I was getting the error "Extra script /config/postproc.sh is not a Python file". I looked back at the release log for v0.3.13 due to the above issue and found out they changed so it can only run python scripts now for post-processing. Here is a new wiki entry they just put up a few days ago explaining this along with a small python snippet you can use to work as an intermediary between python and whatever your script is. If you run a bash script like I did, you'll want to create a python file similar to this and change your post-processing script in Settings to point at it now instead. /config/postproc-shiv.py import subprocess import sys subprocess.call(['/bin/bash', '/config/postproc.sh'] + sys.argv[1:]) # If you need to run more scripts (optional) # subprocess.call(['my_cmd2', 'my_script2'] + sys.argv[1:]) Hope that helps someone who might run into the same issues!
  3. Not sure what happened but seems like since I updated over the weekend that Medusa is no longer letting me log in with my credentials. Is there something that could have reset them or caused some issue with the latest update? Edit: No idea what caused it, but I shut down the container, went into config.ini and blanked out the web_password, logged in with no pwd, and then re-set the same password in Settings again. Seems to be working for now anyway.
  4. Good to know, I thought it was only Samsung drives affected. Definitely want to do some research before purchasing new ones then to be sure they'll work correctly. I blew $600 (at the time) on two 850 EVO 1TB drives specifically to use as my unRAID cache drives in a mirror and was quite frustrated that it didn't work (and still doesn't a couple years later!). Hopefully others will be spared the pain and expense.
  5. If you were planning to use them for this specific purpose and have the option to return them still, I'd say to do that. Right now there is no idea if/when this issue will be resolved. As far as what to replace them with, I think anything non-Samsung will do. I believe the issue is specific to their drives, but someone correct me if I'm wrong.
  6. I use rTorrent-VPN from binhex which also includes Privoxy and I use it with JDownloader. I just went under Settings in JDownloader, went under Connection Manager, and added the Privoxy address (same as my unRAID server since I'm not doing anything fancy with my docker network settings) with port 8118. That's what it is set to use in rTorrent-VPN, not sure if that is default or would be the same address/port for you. Also make sure to uncheck the "No Proxy" entry so it doesn't try to download stuff without the proxy/VPN.
  7. Just having a VPN isn't quite enough. What you need is a proxy to direct it through. If you are using binhex's DelugeVPN container, I believe he usually includes the Privoxy proxy host as part of that. If so, you should be able to go into JDownloader's Settings and look under Connection Manager. You'll want to add the Privoxy proxy there using your unRAID server's host/IP address (or the DelugeVPN container's IP if you have it set to use a different one from the unRAID server, which is uncommon) and port 8118, with user and password left blank. Also make sure to uncheck the No Proxy line so it doesn't try to use your non-VPN'ed internet connection. Once you have that set you should be good to go. Just to add on - to double-check you are using your proxy, look in the Connection column of your Downloads when something is running. I think it will say in there what IP address you are using to download (might have to hover over the icons to see in a tool tip popup). Verify that is different from your normal IP you are using for your home connection. If you don't know how to check your home connection's IP, just open a browser on your home system and go to Google and search "what is my ip" and it will tell you.
  8. I was trying to write up a better detailed tutorial/step-by-step for how to do it for others who aren't as savvy, but realized there was a step that was more complicated and I was wondering how you did it. That is copying the OmbiExternal.db back to the appdata folder (or altering it in place). By default I think the permissions are for "nobody" and so you can't write to the folder or alter the file as your Windows user. I know how to alter permissions via linux command line, so I did it that way so I could change the file and then set them back to what they were before, but was wondering how you did it? Trying to think of an easier way to put in my steps for people who may not use CLI.
  9. Ran into this too and it looks like this is the issue. Look at my post there (currently the last one) for a fix you can do without having to install anything into your container. It looks like they added a new column to a table and the container must have jumped versions too much and missed out on the intermediary release that included the code to add that column. So now the current version expects it to be there, but it is missing. edit: My post isn't the bottom one anymore and to avoid confusion, I'll just repost it here: I had this problem also and fixed it by running the previously recommended SQL query against OmbiExternal.db ALTER TABLE PlexServerContent ADD COLUMN RequestId INTEGER NULL; I didn't want to install stuff into my container so I just used the zip version (no install needed on your desktop either) of this SQLite browser/editor. I stopped my Ombi container, opened the OmbiExternal.db with the SQLite editor program, ran the query above, verified it had added the column into the proper table, saved it, and then started the Ombi container back up again. Everything looks like it working again with movies and TV posters showing up, as well as the "no such columns" error now no longer showing up in the logs.
  10. I've said repeatedly I'll do what you suggest if it breaks again. I needed to remotely access my system this week and thus needed it working, so I had rebuilt it from scratch again already before that suggestion was brought up as a troubleshooting step. It is currently functioning as is. Since I don't know what causes it to break, I can't force that to happen yet. Just posted because I saw others posting with the same issue which I thought was worth noting.
  11. Sorry, when you were saying my appdata was the problem it seemed you were implying there was an issue with the way it is set up in unRAID, the drive was failing/corrupting, or something like that. None of which appears to be true from my observations so far. Obviously from the error the issue seems to be that files are going missing randomly in the appdata folder and I've said that the only way I've been able to get mine working or "fix" it is to do the same thing as that person - delete the docker container and appdata folder completely and rebuild it from scratch. I've had to do this a few times now. Due to the fact that it has happened to multiple separate people with likely disparate systems/builds, it seems like whatever is causing the files to go missing or corrupt is coming from inside the container, or at least not specific to my system. What that is I'm not sure as I'm not a dev and it is just a hypothesis, but I figured I'd report it here, and seeing other reports of the same thing tended to confirm my suspicions. As I said, I'll try your suggestion and report here if it happens again, but at least something is documented in case it rears its head again on mine or someone else's system.
  12. I don't believe it is an issue with my appdata, unless it is universal to more users than just me. As you can see others are having this problem as well (above and previous pages). If it happens to me again though I can try to change the path of my /config to /mnt/cache/appdata/openvpn-as and see what happens.
  13. Never had an issue with my appdata in the couple years I've been running unRAID. I have about 25 docker containers on there (about half running usually). All others have been stable/no issues currently. Single drive Samsung SSD cache drive with all appdata written to it. Appdata share is set to use cache drive only. For openvpn-as I just left all parameters at their defaults when loading the container. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='openvpn-as' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'PGID'='100' -e 'PUID'='99' -p '943:943/tcp' -p '9443:9443/tcp' -p '1194:1194/udp' -v '/mnt/user/appdata/openvpn-as':'/config':'rw' --cap-add=NET_ADMIN 'linuxserver/openvpn-as'
  14. So I set up the whole container from scratch a couple weeks ago due to the issues I had earlier (see below or my previous posts a page back). Had to relearn how to do it all again since it had been a couple years since I've had to set it up, but with @SpaceInvaderOne's videos and some reading on Github I was able to get it going again. Used it a couple times on my phone and laptop and it was working fine. Now I just did an update today and I'm back to the same thing again. Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-time: executing... [cont-init.d] 20-time: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-openvpn-init: executing... find: ‘/config/etc/db’: No such file or directory /var/run/s6/etc/cont-init.d/40-openvpn-init: line 14: /usr/local/openvpn_as/bin/ovpn-init: No such file or directory Stopping openvpn-as now; will start again later after configuring cat: /var/run/openvpnas.pid: No such file or directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] [cont-init.d] 40-openvpn-init: exited 0. [cont-init.d] 50-interface: executing... /var/run/s6/etc/cont-init.d/50-interface: line 9: /usr/local/openvpn_as/scripts/confdba: No such file or directory /var/run/s6/etc/cont-init.d/50-interface: line 10: /usr/local/openvpn_as/scripts/confdba: No such file or directory /var/run/s6/etc/cont-init.d/50-interface: line 11: /usr/local/openvpn_as/scripts/confdba: No such file or directory /var/run/s6/etc/cont-init.d/50-interface: line 12: /usr/local/openvpn_as/scripts/confdba: No such file or directory [cont-init.d] 50-interface: exited 127. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory ./run: line 3: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory The last line just continually keeps popping up/repeating until I kill it. Tried a restart of the container as well as stop/start. I really don't want to have to re-set this thing up from scratch every couple weeks or when there is an update. Is there any idea what causes this and how to fix it from happening again? I know others previously had the same issue, did you get this again or has it worked since you've resetup from scratch? edit: Been messing with it, including removing and re-adding the container (with existing appdata), but no luck. I need to use it tomorrow to connect remotely, so I ended up re-setting it up from scratch again and it is working... for now.
  15. OK. Is there a way to clear/reset the ruTorrent settings without having to reload the entire container? A conf file(s) or folder(s) that I can just delete and will be recreated with defaults when I restart the container? Seems like maybe a stuck or old setting in there is messing things up. Edit: Actually I do have some RSS saved in ruTorrent so I guess I don't want to delete the entire configuration. I see /config/rutorrent/share/settings/throttle.dat file which looks like it maybe relates to the channels. If I delete that will it recreate with defaults upon a restart? Edit2: So I took a closer look at that throttle.dat file. O:9:"rThrottle":3:{s:4:"hash";s:12:"throttle.dat";s:3:"thr";a:10:{i:0;a:3:{s:2:"up";i:64;s:4:"down";i:0;s:4:"name";s:4:"up32";}i:1;a:3:{s:2:"up";i:128;s:4:"down";i:0;s:4:"name";s:5:"up128";}i:2;a:3:{s:2:"up";i:64;s:4:"down";i:256;s:4:"name";s:11:"up64down256";}i:3;a:3:{s:2:"up";i:128;s:4:"down";i:1024;s:4:"name";s:13:"up128down1024";}i:4;a:3:{s:2:"up";i:256;s:4:"down";i:2048;s:4:"name";s:13:"up256down2048";}i:5;a:3:{s:2:"up";i:0;s:4:"down";i:16;s:4:"name";s:6:"down16";}i:6;a:3:{s:2:"up";i:0;s:4:"down";i:32;s:4:"name";s:6:"down32";}i:7;a:3:{s:2:"up";i:0;s:4:"down";i:64;s:4:"name";s:6:"down64";}i:8;a:3:{s:2:"up";i:0;s:4:"down";i:128;s:4:"name";s:7:"down128";}i:9;a:3:{s:2:"up";i:0;s:4:"down";i:256;s:4:"name";s:7:"down256";}}s:7:"default";i:5;} Looking at this reminded me that I did play with channels a while back and setup some custom ones in the web GUI. I also played with setting a default channel, which was #5 at the time. I think when I restarted the container they just went back to defaults so I didn't bother with them anymore since they didn't seem to stick. Even though the ruTorrent GUI settings didn't show the above custom channels anymore and didn't seem to be using them either, it seems like it would occasionally use the default channel as #5 lately, which in the default channels is "up256". It looks like it would happen when Medusa was sending torrents/magnets over, maybe because it doesn't use the "admin" user but just a default of some kind via SCGI? Still doesn't explain the "Don't Download" priority being set sometimes, but maybe related somehow. Anyway, I stopped the container, deleted the /config/rutorrent/share/settings/throttle.dat file, and started it up again. It didn't initially recreate the file. I logged into the ruTorrent web GUI as admin and made a change to the channels and then it created a file under /config/rutorrent/share/users/admin/settings/throttle.dat instead. Now that I know how it works I'll probably just delete that file anyway and leave it at defaults as I don't really use channels currently. Here's what that new default (except small change on one channel) file looks like: O:9:"rThrottle":3:{s:4:"hash";s:12:"throttle.dat";s:3:"thr";a:10:{i:0;a:3:{s:2:"up";i:16;s:4:"down";i:0;s:4:"name";s:4:"up16";}i:1;a:3:{s:2:"up";i:32;s:4:"down";i:0;s:4:"name";s:4:"up32";}i:2;a:3:{s:2:"up";i:64;s:4:"down";i:0;s:4:"name";s:4:"up64";}i:3;a:3:{s:2:"up";i:128;s:4:"down";i:0;s:4:"name";s:5:"up128";}i:4;a:3:{s:2:"up";i:256;s:4:"down";i:1024;s:4:"name";s:5:"up256";}i:5;a:3:{s:2:"up";i:0;s:4:"down";i:16;s:4:"name";s:6:"down16";}i:6;a:3:{s:2:"up";i:0;s:4:"down";i:32;s:4:"name";s:6:"down32";}i:7;a:3:{s:2:"up";i:0;s:4:"down";i:64;s:4:"name";s:6:"down64";}i:8;a:3:{s:2:"up";i:0;s:4:"down";i:128;s:4:"name";s:7:"down128";}i:9;a:3:{s:2:"up";i:0;s:4:"down";i:256;s:4:"name";s:7:"down256";}}s:7:"default";i:0;} If it continues doing weird stuff, I'll try to update here. Otherwise hopefully this will help somebody else if something similar happens to them.