subagon

Has anyone seen a update/fix to the connection timeout issue that was reported to Plex a month ago? My Plex server is working okay, but stuck on version 1.13.2.5154-fd05be322. I see that Plex is now up to version 1.13.7.5369, but i haven't seen anything in the release notes about a fix. Please forgive me for bringing up an old issue, but I don't want it to become forgotten.

I see Plex has released version 1.13.6.5339. I didn't see anything in the brief release notes about a fix for the connection timeout issue ☹️. Anyone try it anyway?

Thanks for the info. I downgraded to 1.13.2.5154 a couple of days ago and things are much better. I am still seeing connection timeout errors, but not as many. I'm no longer seeing the down 5 minutes, up 30 seconds on 1.13.2.5154. I'm sure once we get a fix from Plex, someone here will let everyone know.

BCinBC, You said "Engineering is working on that now and , AFAIK, will be in next update". Who is "Engineering"? Plex or the Linuxserver.io guys? In other words, what release will fix the issue, Plex or Docker?

I see that there's a update to the Plex docker. Anyone know if it fixed the connection timeout issue?

This seems to be working for me. However, I'm still seeing connect timeout errors in the log file. Upside is that everyone is able to watch movies/shows and that's all they care about right now. Just have to sit back and wait for a fix to the current version.

Well I installed an old version of Plex (1.13.3.5223-cd1e0da1b) and no luck. I have 4 physical NICs and I've shut all but one of them down (wasn't really using them). Shut down VM manager (no VMs). I did this to shutdown virt0 interface. I reinstalled the current version of Plex (plexpass) and set Plex to listen to all interfaces (it was set to "all" when the issues started). Now the only interfaces it sees are br0 and docker0. Connection is still timing out, going up and down every couple of minutes. Mostly down, only up for a few seconds. Server is running, just connection issue. Not seeing any other connection issues on other dockers or other computers/devices in the house. I'm running a pfsence router running most current version. Rebooted it a couple of times, because of "NAT" in an error message, no luck rebooting. That enough for now, late here, off to bed.

Thanks, also I just found this to monitor logs in realtime, docker logs -f plex Edit; Adding output from Plex server log snip . . Aug 14, 2018 21:35:39.151 [0x1470603ff700] ERROR - Sync: could not get sync list 15715627, sync item 23361763 to update status Aug 14, 2018 21:35:39.151 [0x1470603ff700] ERROR - Sync: could not get sync list 15715627, sync item 23361898 to update status Aug 14, 2018 21:35:39.151 [0x1470603ff700] ERROR - Sync: could not get sync list 15715627, sync item 27916817 to update status Aug 14, 2018 21:35:39.344 [0x1470603ff700] WARN - Held transaction for too long (../Versions/VersionGarbageCollector.cpp:78): 0.180000 seconds Aug 14, 2018 21:35:39.504 [0x1470603ff700] WARN - Held transaction for too long (../Versions/VersionGarbageCollector.cpp:78): 0.150000 seconds Aug 14, 2018 21:36:16.145 [0x1470577ff700] INFO - AutoUpdate: no updates available Aug 14, 2018 21:36:29.024 [0x14704e7ff700] WARN - NAT: PMP, timed out waiting for response. Aug 14, 2018 21:36:29.024 [0x14706a3ff700] ERROR - EventSource: Retrying in 15 seconds. Aug 14, 2018 21:36:29.024 [0x14706a3ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (be4a8010-28b8-4af9-857d-e288d25c128f, expected 9e4b9a05-f720-41ff-8afd-d115c2047063) Aug 14, 2018 21:38:52.384 [0x1470373fd700] WARN - NAT: PMP, timed out waiting for response. Aug 14, 2018 21:38:52.384 [0x14706a1fe700] ERROR - EventSource: Retrying in 15 seconds. Aug 14, 2018 21:38:52.384 [0x14706a1fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (e652e049-6fac-4b55-8fd5-4e9b9232fcb0, expected c96968dd-43c1-448b-93aa-ca901926cbb5) . . snip

Mine is set to "all", but I'll play with it setting to to the unraid interface, br0.

Thanks guys, I'll drop back to the prior version and see if that helps. Another quick question, where in the docker are the plex logs? I looked in /var/lib/plexmediaserver/ and it was empty. Running a find from root, but it's taking a long time since it's going thru the media directory too.

I've been having this same issue. Started about 10 days ago. No changes other than updating to latest docker. My logs file look just like this one, except for IP's. Did you resolve the issue? My Plex server is unreachable and the family is getting violent. Edit; It's back online right now, but it goes up and down. Same pattern for last 10 days, but seems to be getting worse. Edit #2; That didn't take long... Down again. Not having any other network type issues I'm aware of. Other dockers working okay. Samba okay, etc.

Thank you! I must comment that this is a poor GUI setup. I would suggest that all Edit buttons be displayed in either Basic or Advanced mode. having a mix is confusing.

Please look at my original post. There isn't an edit button for the /config path.

That will allow me to edit/select the path for /config, but doesn't allow me to select any of the "slave" modes.

I keep getting a warning from the Fix Common Problems plugin. Docker application plex has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option My Plex /config path is mapped to /mnt/disks/plex/, which is a SSD unassigned device. If I edit the Plex docker, there isn't any option to set/select RW Slave for this path. Any thoughts? Thanks, Mike

Thanks for the answer. Thought that was the process, but wanted to be safe/sure. Mike

unRAID 6.4.0 w/ 2 parity drives One of my parity drives is failing (Reallocated sector count = 12 and growing). How do I safely remove the failing parity drive? If it matters, I first created the array with a single parity drive and latter added a second parity drive. The first/original parity drive is failing. Drive is under warranty and I have an RMA ready to go. TIA, Mike

bonienl, One more question... As I said, my motherboard has 4 NICs. I now have eth0 setup to bridge and therefore have the br0 interface. I've turned off bonding (this server is in my home and I don't need redundancy). So I now have the following interfaces showing up on the Network Setting page; br0 br1 eth2 br3 I want to use br0, br1, and br3 for various dockers plus file sharing off of eth0/br0. I'd like to put Plex on eth2 all by itself. The problem is I can only see Bridge, Host, None, and br0 when editing the Plex (or any) docker. I tried the commands you provided above, but without any luck. How can I add br1,eth2, and br3 to the drop down list or manually edit the Plex docker file to use eth2? Thanks

bonienl, The commands restored the br0 interface and all my dockers are working again. If you're ever in Tampa, Florida, the beer is on me.

Some more info after reading this post https://lime-technology.com/forums/topic/61006-how-to-setup-ips-for-dockers/ root@asok:~# docker network ls NETWORK ID NAME DRIVER SCOPE 32176c05a279 bridge bridge local 7ce2002afcd5 host host local 5b8a210f2546 none null local root@asok:~# docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o parent=br0 br0 Error response from daemon: network dm-2f4a429bc5a3 is already using parent interface br0 root@asok:~# docker network rm dm-2f4a429bc5a3 Error response from daemon: network dm-2f4a429bc5a3 not found

unRAID 6.4.0 Supermicro - X9DRD-7LN4F with 4 NICs I have a couple of dockers that I had setup and working that I had bridged to their own IP addresses. My NICs were all bonded together in active-backup mode. I messed around with the network setting to setup some of the NICs as separate interfaces. Somewhere in this process the br0 interface was deleted/disappeared. I put everything back to the way it was before (I think), but the br0 is gone from the GUI. Here's a sample from the log file; Jan 23 10:47:25 asok root: pihole: Error response from daemon: network br0 not found Error: failed to start containers: pihole And some screenshots below. Reboot server a few times, started and stopped docker and VM service many times... How do I get br0 back?

Thanks for the reply Unlimited drives is good to hear. That and the old single parity drive kept me from trying unRAID a couple of years ago. I just need to dust off an old computer so I can test out unRAID with a trial. One last question, I want to have a single SSD drive to use for tmp files (transcoded Plex files, etc). Can I NOT include it in the unRAID array and still use it from say a Plex docker? TIA, Mike

I currently have 24x3.5" bays + 2x2.5" bays 4U NAS server running vanilla linux (drives are 6x8TB, 6x6TB, 12x3TB and 2x1TB<-2.5"). I want to move to either unRAID or FreeNAS. I really like that I can easily use different drive sizes with unRAID. If I go with FreeNAS I'll have to buy some more drives and retire several good drives. All my 3.5" drives are used for data and parity, while the 2.5" drives contain the OS + mirror. Questions: What is the current maximum number of drives for unRAID 6.2? Are parity and cache drives included in the maximum number of drives? Can I start with a single cache drive and add a second one without rebuilding the array? (i.e. wipe data, create new array, and recover from a backup) Can I start with one parity drive and then at a latter time add a second one without rebuilding the array? (i.e. wipe data, create new array, and recover from a backup) Thanks, Mike