infi704

Not 100% sure, but ram usage on unraid runs about 11gig/32 used, and ramdisk usage never exceeded 5gig, but i wasnt monitoring it that closely, so it is possible. Are you running your plex db's on ramdisk? I would like to hear about a success story before I try again, the errors i was getting (sorry didnt save the logs, was trying to bring plex back as top priority), when researched, came back to forum results about DB corruption on NFS when strict locking was not implemented, so i was under the assumption that many tmpfs doesnt have the locking capabilities other real FS's have.

I dont think that was it, as i was only running the script by hand at the terminal, and the database became corrupted after a long period of not running it.

The script does most of that, it will check if plex is idle, stop the container, copy the databases to /dev/shm/folder, validate the databases are not corrupted (notify you if they are), use fusefs to mount the ramdisk over the plex database location, and start plex. It also has protections in place to not mount twice, using the mountpoint command. The script only puts the database in ramdisk (about 860MB in my case) after it validates the database, it will copy it to a Last_Known_Good folder, so you should be able to recover from that incase it detects corruption. Even after all that, the database got randomly corrupted during a massive metadata import. It could have just been something I did, which is why i provided the script, but i will not be using it anymore. The difference was about 5 seconds vs 1 second to start playing content, and i can live with that extra delay knowing my database is less likely to be corrupted.

I was really interested in running the PlexDB to ramdisk, that i wrote a script to do it. I used /dev/shm instead of /tmp (/tmp appears to be set to 1MB) It was really fast, i would say almost 5x faster at loading content, but during heavy operations, plex would complain about db corruption, and Transactions not existing. I do not recommend this approach, but if anyone wants to try out the script, it should be easy to get up and running: https://github.com/vaparr/plex-ramdisk you have to map /dev/shm to /dev/shm in your docker configuration. Only use on a test instance of plex, as it will likely work fine for a while, then corrupt your database.

Im having an issue with Next-Gen PIA support. My LAN network is 10.0.0.0/24, with the router as 10.0.0.1. 2020-09-29 17:53:10.640597 [info] LAN_NETWORK defined as '10.0.0.0/24' it looks like we use this same IP to generate a token: 2020-09-29 17:53:53,873 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken' [info] 12 retries left [info] Retrying in 10 secs... as a workaround, i am able to open a shell in the docker, and route that IP thru the VPN, which fixes the issue: sh-5.0# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.2.112.1 128.0.0.0 UG 0 0 0 tun0 0.0.0.0 172.17.0.1 0.0.0.0 UG 0 0 0 eth0 10.0.0.0 172.17.0.1 255.255.255.0 UG 0 0 0 eth0 10.2.112.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0 128.0.0.0 10.2.112.1 128.0.0.0 UG 0 0 0 tun0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 172.98.71.68 172.17.0.1 255.255.255.255 UGH 0 0 0 eth0 sh-5.0# route add 10.0.0.1 gw 10.2.112.1 And its all working now. I have to apply this workaround each time the docker restarts, as the VPN IP changes each time. Edit: https://github.com/binhex/arch-int-openvpn/issues/15

Looks like the newest docker now has multi remote opvn support