Jump to content

clowrym

Members
  • Content Count

    433
  • Joined

  • Last visited

Everything posted by clowrym

  1. can you switch to advanced view and send again.... Should look similar to this: Looking at your run command there is somthing wrong with your second one as your getting '1198:admin/udp' rather then '1198:1198/udp'
  2. Can you click edit on your port entries and show me whats inside, there is something wrong. Mine looks like this: -p '9091:9091/tcp' -p '1198:1198/udp' Where your's look like this:
  3. Thats an odd issue, I have always had mine set to the Host IP & only Transmission traffic is routed through my VPN. can you post your settings for the container?
  4. Basically you just have to place the world files inside of your servers Folder, for instance, My sons sever & Downloaded worlds are placed in /mnt/cache/appdata/minecraftOS/servers/RykersServer/ where ~/mazerunner was a Maze runner map we downloaded that was based on the maze runner movie. There is also a folder for Hogwarts, temple, labyrinth, etc. one for each world you want to have on your server. If you have multiple worlds, you may also need a plugin so they can travel between them easily, ie. creative gates.
  5. change your local network to 192.168.1.0/24
  6. I have been having an issue for the last couple months anytime My Plex Docker updates I get the following Errors in my syslog. On occasion doing an update to the plex container will kill all Network access to my server, Or will shut my server down completely. I have tried adjusting my folder mappings & posted in Linuxservers Plex docker support thread who suggested this isnt likely an issue with the container. Its only an issue when updating my plex container, none of the other seems to have the problem. Jul 11 04:00:05 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Jul 11 04:00:15 Tower Docker Auto Update: Stopping plex Jul 11 04:00:18 Tower Docker Auto Update: Stopping radarr Jul 11 04:00:23 Tower kernel: veth650c3aa: renamed from eth0 Jul 11 04:00:23 Tower kernel: docker0: port 2(vethcacec4b) entered disabled state Jul 11 04:00:23 Tower avahi-daemon[10153]: Interface vethcacec4b.IPv6 no longer relevant for mDNS. Jul 11 04:00:23 Tower avahi-daemon[10153]: Leaving mDNS multicast group on interface vethcacec4b.IPv6 with address fe80::bc75:9ff:feac:7216. Jul 11 04:00:23 Tower kernel: docker0: port 2(vethcacec4b) entered disabled state Jul 11 04:00:23 Tower kernel: device vethcacec4b left promiscuous mode Jul 11 04:00:23 Tower kernel: docker0: port 2(vethcacec4b) entered disabled state Jul 11 04:00:23 Tower avahi-daemon[10153]: Withdrawing address record for fe80::bc75:9ff:feac:7216 on vethcacec4b. Jul 11 04:00:23 Tower Docker Auto Update: Installing Updates for plex radarr Jul 11 04:00:46 Tower Docker Auto Update: Restarting plex Jul 11 04:00:47 Tower Docker Auto Update: Restarting radarr Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered blocking state Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered disabled state Jul 11 04:00:47 Tower kernel: device veth5b9bbf5 entered promiscuous mode Jul 11 04:00:47 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth5b9bbf5: link is not ready Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered blocking state Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered forwarding state Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered disabled state Jul 11 04:00:47 Tower kernel: eth0: renamed from vethbf235a3 Jul 11 04:00:47 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5b9bbf5: link becomes ready Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered blocking state Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered forwarding state Jul 11 04:00:48 Tower Docker Auto Update: Community Applications Docker Autoupdate finished Jul 11 04:00:49 Tower avahi-daemon[10153]: Joining mDNS multicast group on interface veth5b9bbf5.IPv6 with address fe80::d40f:23ff:fe6f:dcdc. Jul 11 04:00:49 Tower avahi-daemon[10153]: New relevant interface veth5b9bbf5.IPv6 for mDNS. Jul 11 04:00:49 Tower avahi-daemon[10153]: Registering new address record for fe80::d40f:23ff:fe6f:dcdc on veth5b9bbf5.*. Jul 11 04:00:58 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdc1 Jul 11 04:00:58 Tower kernel: BTRFS warning (device md6): duplicate device fsid:devid for e5144b2d-b213-4aae-8b7a-07a4556cae15:1 old:/dev/md6 new:/dev/sde1 Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available Jul 11 04:00:58 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdn1 Jul 11 04:00:59 Tower kernel: BTRFS warning (device md5): duplicate device fsid:devid for fe9954eb-fe72-400e-9e51-a93a620db2b6:1 old:/dev/md5 new:/dev/sdp1 Jul 11 04:01:03 Tower kernel: BTRFS warning (device md8): duplicate device fsid:devid for fe834164-5e8e-4dad-8ad1-3186ed9ca15d:1 old:/dev/md8 new:/dev/sdl1 Jul 11 04:01:03 Tower kernel: BTRFS warning (device md4): duplicate device fsid:devid for 16d6aaf7-f0d9-419d-ac06-d0351d960bdb:1 old:/dev/md4 new:/dev/sdt1 Jul 11 04:01:05 Tower kernel: BTRFS warning (device md1): duplicate device fsid:devid for 1b8fa8ee-850f-48f2-8614-af47d6577726:1 old:/dev/md1 new:/dev/sdh1 Jul 11 04:01:07 Tower kernel: BTRFS warning (device md3): duplicate device fsid:devid for ef88f475-319d-426d-b02d-89353e6cc2be:1 old:/dev/md3 new:/dev/sdf1 Jul 11 04:40:02 Tower kernel: mdcmd (516): spindown 18 Jul 11 04:51:34 Tower kernel: mdcmd (517): spindown 19 tower-diagnostics-20190711-1711.zip
  7. could be i suppose, although its only the plex container that causes the issue when updated / restarted!! all my other dockers dont cause these issues!
  8. Every time I restart the plex container, or do a force update I get the following errors in my unraid logs, Any idea what could cause this? On a few occasions I lose all network access to my server & have to do a hard restart Jul 4 09:34:14 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdc1 Jul 4 09:34:14 Tower kernel: intel_powerclamp: No package C-state available Jul 4 09:34:14 Tower kernel: intel_powerclamp: No package C-state available Jul 4 09:34:14 Tower kernel: BTRFS warning (device md1): duplicate device fsid:devid for 1b8fa8ee-850f-48f2-8614-af47d6577726:1 old:/dev/md1 new:/dev/sdh1 Jul 4 09:34:14 Tower kernel: BTRFS warning (device md6): duplicate device fsid:devid for e5144b2d-b213-4aae-8b7a-07a4556cae15:1 old:/dev/md6 new:/dev/sde1 Jul 4 09:34:14 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdn1 Jul 4 09:34:19 Tower kernel: BTRFS warning (device md8): duplicate device fsid:devid for fe834164-5e8e-4dad-8ad1-3186ed9ca15d:1 old:/dev/md8 new:/dev/sdl1 Jul 4 09:34:19 Tower kernel: BTRFS warning (device md4): duplicate device fsid:devid for 16d6aaf7-f0d9-419d-ac06-d0351d960bdb:1 old:/dev/md4 new:/dev/sdt1 Jul 4 09:34:19 Tower kernel: BTRFS warning (device md5): duplicate device fsid:devid for fe9954eb-fe72-400e-9e51-a93a620db2b6:1 old:/dev/md5 new:/dev/sdp1 Jul 4 09:34:23 Tower kernel: BTRFS warning (device md3): duplicate device fsid:devid for ef88f475-319d-426d-b02d-89353e6cc2be:1 old:/dev/md3 new:/dev/sdf1 Docker run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' --privileged=true -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e '100'='100' -v '/mnt':'/mnt':'rw,slave' -v '/mnt/cache/appdata/plextmp':'/transcode':'rw,slave' -v '/mnt/cache/appdata/plex':'/config':'rw,slave' -v '':'/movies':'rw' -v '':'/tv':'rw' -v '':'/music':'rw' --restart=unless-stopped 'linuxserver/plex' 5c573a3ade05b394289b7bccfd7c059da74774c3257f86077048cddd0b3e29f4
  9. could be I suppose, I've always been on the plexpass version I believe this was the post regarding the crash ive been seeing every couple days https://forums.plex.tv/t/ubuntu-18-04-2-lts-plex-server-crashes-double-free-or-corruption-prev/385447 as far as force update killing my server, its only the plex docker that causes this.
  10. I've been having this issue the last month or so, and it looks like others on linux are as well. I've read a post on plex forums regarding the crash... but cant seem to find it now. I've also been having issues if I click force update on plex where it either crashes my server, or kills all networking where I have to hard reboot my server to gain access again. This morning was the first time clicking force restart actually shut my server down (turned off completly). Since it shut my server right off, i can't grab the logs
  11. if you click advanced view on the docker page, you should get an option to force update.
  12. Just looking at this Pic posted to github, is there a space after the 1?
  13. I checked your naming & such, as well as read your issue posted on the git page. I don't see any reason that It shouldn't work, I personally use PIA, so I have no way of testing. If your VPN_PROVIDER & VPN_PROVIDER_CONFIGS values are correct, there is no reason this shouldn't work That I can see. As haugene had suggested, sis you try and pull the image again? (Force Update)
  14. You can go here and request that your VPN provider be added, Alternativly, if your using a VPN that is already there, you can add options here, seperated by a vertical line. Then they will show up in the drop down. This is also the same process if you are using something other than PIA, as this Docker template is set up for PIA Specifically
  15. I didnt create the program, only the docker template, I can look at creating one for mineos-ruby .
  16. are you changing the default values? ie. local1|local2|local3 etc...? default value is where the config names are stored and have to have "|" in between ( this is the vertical line on your keyboard, not a capital i)
  17. Glad you got everything working to your liking!!
  18. on my server, Transmission only keeps the disks used spun up, so my Disk 2 spins down unless there are downloads / seeding on a particular disk. I expect yours should be the same. That being said, my disk 1 never spin's down, as its always active. You could try turning off the watch folder, but then I dont know if soarr/radarr use that should you be using those currently my disk 2 is spun down...
  19. That's why, transmission is always running and watching, if you only have one data disk, it will never spin down while transmission is running...
  20. interesting, I wonder if there is a plugin / docker that can tell you what is keeping the disk spun up, unless transmission is actually storing files on all the different disks, I dont see why yours would stay spun up. you can have a look at your downloads folder and see what/which disks its storing everything on. Looking at mine, there are some folders that span both disks, but almost all files are on one disk only. the files that are on both disks currently look like they are old recovery files from past downloads. All transmission conf. files & current downloads are all housed on disk 1. One thing I see that is different then my set up is your config directory, I map mine specifically to /mnt/cache/appdata, rather then /mnt/user/appdata, but i dont think that would make a difference unless your appdata share isnt set to cache only.
  21. Just reviewing my system, The majority of the time My downloads are small enough to stay on one disk, so my second disk in this sytem spins down just fine unless a torrent starts downloading / seeding from that disk. Maybe you have files seeding / downloading on multiple disks? One thing to note, I don't use a parody disk in the server that runs transmission, as this server only runs transmission! I believe as this Docker is always running for Download / seeding the disks won't spin down. You may be able to avoid all disks from staying up if you specify specific disk to the download share.
  22. I didnt actually create this Docker, Only the Unraid template. If I remember correctly, this was supposed to test your connection and restart it if it wasnt connected, Restart container if connection is lost If the VPN connection fails or the container for any other reason loses connectivity, you want it to recover from it. One way of doing this is to set environment variable OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60 and use the --restart=always flag when starting the container. This way OpenVPN will exit if ping fails over a period of time which will stop the container and then the Docker deamon will restart it.