Jump to content

clowrym

Members
  • Content Count

    436
  • Joined

  • Last visited

Community Reputation

14 Good

1 Follower

About clowrym

  • Rank
    Advanced Member
  • Birthday 01/26/1975

Converted

  • Gender
    Male
  • Location
    Calgary, Alberta

Recent Profile Visitors

1288 profile views
  1. I havent run into this issue, I typically use the web interface though with a different gui set.....
  2. I beleive your openvpn config is incorrect, should be the same as found on this page Proton VPN config Files
  3. I've never used this particular setting, But I believe your key should be set to TRANSMISSION_UMASK , not just UMASK Basically any variable you see here or here can be added to your docker template with TRANSMISSION_whichever_setting_you_want_to_be_Static_after_reboot_of_the_container set as the key as you indicated in your post. For instance, I have my Queue size set :
  4. 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'
  5. 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:
  6. 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?
  7. 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.
  8. change your local network to 192.168.1.0/24
  9. 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
  10. 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!
  11. 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
  12. 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.
  13. 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