6 hours ago, deteria said:

How did you set up your libraries?

I used to have that issue where I had to run mover manually since I set up the directory to the disk share.

If you set the directory as a user mount share, it should work.

 

 

Everything in user share. My plex worked fine before I upgraded to Unraid ver 6.7.2. My plex library is in a share using disk cache, so maybe I'll try moving them back to aray. Thank you man!

Edited July 3, 20197 yr by Hoanh

15 hours ago, deteria said:

I updated the docker again via the usual update link and it failed and removed the docker image.  Had to go back to CA Previous Apps to re-install the previous app to install properly.  Anyone else having this issue?

 

Not really an issue with the container.

You have something in your template that fails. This can be a dvb device or nvidia card and for some reason they are not available.

On 6/30/2019 at 3:36 PM, aptalca said:

Your db was likely already corrupted before the switch. Google how to restore Plex db

But that would allow things to still run while the app data is in /mnt/user/appdata/PlexMediaServer/ but then get caught in a crash loop when I only change the directory in the docker template to /mnt/cache/appdata/PlexMediaServer/ ? 

 

Here is what the specific entry in the docker log looks like when I do that

 

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.2.1297-4b7ace214/PLEX MEDIA SERVER/55e3a89d-90b5-b4b2-3afbf75b-4e9ba94f.dmp
Starting Plex Media Server.
terminate called after throwing an instance of 'std::runtime_error'

And then when I change the directory back to /mnt/user/appdata/PlexMediaServer/ everything returns to normal, and then randomly the DB will start giving that SQLite error.

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

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/sdc1Jul 4 09:34:14 Tower kernel: intel_powerclamp: No package C-state availableJul 4 09:34:14 Tower kernel: intel_powerclamp: No package C-state availableJul 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/sdh1Jul 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/sde1Jul 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/sdn1Jul 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/sdl1Jul 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/sdt1Jul 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/sdp1Jul 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

You should post your diagnostics in a new thread it doesnt look like it has anything to do with plex

Sent from my NSA monitored device

5 minutes ago, Squid said:

You should post your diagnostics in a new thread it doesnt look like it has anything to do with plex

Sent from my NSA monitored device
 

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!

Does anyone know how to roll back to previous build of Plex? I have some problems with the ver 1.16.2.1297.

19 hours ago, Hoanh said:

Does anyone know how to roll back to previous build of Plex? I have some problems with the ver 1.16.2.1297.

You can pull an earlier tag from docker hub but badge sure the version variable is set to docker so it doesn't update on start

14 hours ago, aptalca said:

You can pull an earlier tag from docker hub but badge sure the version variable is set to docker so it doesn't update on start

I went to docker hub to get the previous ver of plex. However, it didn't work. It seems like the app can not found a repository to pull data.

 

44 minutes ago, Hoanh said:

I went to docker hub to get the previous ver of plex. However, it didn't work. It seems like the app can not found a repository to pull data.

 

 You didn't follow the instructions.

You set the tag in the repository field after linuxserver/plex with an : between the existing text and the tag.

The version variable should be set as docker.

5 hours ago, saarg said:

 You didn't follow the instructions.

You set the tag in the repository field after linuxserver/plex with an : between the existing text and the tag.

The version variable should be set as docker.

I have no idea how it can be done. Can you give me a briefly guide? Thank.

2 hours ago, Hoanh said:

I have no idea how it can be done. Can you give me a briefly guide? Thank.

https://lmgtfy.com/?q=How+to+use+docker+tags

On 7/6/2019 at 8:09 PM, Hoanh said:

I have no idea how it can be done. Can you give me a briefly guide? Thank.

at the end of the docker name you just have to :tag [plex/arm86] .... something along those lines 

Edit the container and change the :latest tag to the new tag you want, you get the tags from the dockerhub page https://hub.docker.com/r/linuxserver/plex/

Edited July 8, 20196 yr by Fiservedpi

Hey guys,

So I am at a loss.  I can log into my plex docker through plex.tv but when I try to launch the webgui I get an error:

This page isn’t working "my host ip address"

didn’t send any data.
ERR_EMPTY_RESPONSE

Any ideas?!

 

Update: 

Now it works on the plex.tv but not internally from localhost.  Any ideas?!

Edited July 12, 20196 yr by GreenEyedMonster

I can not add new stuff or edit item in my plex server. Please help!

 

On 7/14/2019 at 11:20 PM, Hoanh said:

I can not add new stuff or edit item in my plex server. Please help!

Not enough information for any help.

 

See first link in the Docker FAQ:

 

https://forums.unraid.net/topic/57181-real-docker-faq/

 

 

I believe I would like to migrate from the Limetech Plex Docker to Linuxserver's Docker.  This really has to do with the speed at which updates for Plex are released and while I appreciate the conservative view in not running to fast into new updates, I am about to lose my DVR service over an update and can't seem to get a response on when the update will be added to the respository.  So with all respect to them, I have a friend who uses Linuxserver and has not had any issues.

 

The question I have for this group is how do i install a new Plex docker and point it to my old Plex database?  I'd rather not have to re-scan and make manual adjustments to my libraries.   Is this even possible?

4 hours ago, TODDLT said:

I believe I would like to migrate from the Limetech Plex Docker to Linuxserver's Docker.  This really has to do with the speed at which updates for Plex are released and while I appreciate the conservative view in not running to fast into new updates, I am about to lose my DVR service over an update and can't seem to get a response on when the update will be added to the respository.  So with all respect to them, I have a friend who uses Linuxserver and has not had any issues.

 

The question I have for this group is how do i install a new Plex docker and point it to my old Plex database?  I'd rather not have to re-scan and make manual adjustments to my libraries.   Is this even possible?

First, make a backup of your Plex data just in case (you can use the backup and restore plug-in)

 

The image/container structure should be compatible. Stop the other container, then just create a new container with the linuxserver image and point the config folder to the same folder the other container was pointing to. That's really it.

12 hours ago, TODDLT said:

The question I have for this group is how do i install a new Plex docker and point it to my old Plex database?  I'd rather not have to re-scan and make manual adjustments to my libraries.   Is this even possible?

Hi TODDLT you managed this yet as was thinking about it myself but total NOOB and totally dont want to loose anything.

First, make a backup of your Plex data just in case (you can use the backup and restore plug-in)
 
The image/container structure should be compatible. Stop the other container, then just create a new container with the linuxserver image and point the config folder to the same folder the other container was pointing to. That's really it.

Yep, this works as he has stated, had to do my radarr since it hosed itself worked like a charm.

Sent from my SM-N960U using Tapatalk

Just wanted to double check, the version in the settings for this should be set to "docker" right to get the latest? 

 

3 minutes ago, yanksno1 said:

Just wanted to double check, the version in the settings for this should be set to "docker" right to get the latest? 

 

 

From the docs linked in the first post here are the VERSION options:

 

docker: Let Docker handle the Plex Version, we keep our Dockerhub Endpoint up to date with the latest public builds. This is the same as leaving this setting out of your create command.

 

latest: will update plex to the latest version available that you are entitled to.

 

public: will update plexpass users to the latest public version, useful for plexpass users that don't want to be on the bleeding edge but still want the latest public updates.

 

specific-version: will select a specific version (eg 0.9.12.4.1192-9a47d21) of plex to install, note you cannot use this to access plexpass versions if you do not have plexpass.

16 hours ago, coblck said:

Hi TODDLT you managed this yet as was thinking about it myself but total NOOB and totally dont want to loose anything.

yes just tried it, and worked fine.

 

On 7/24/2019 at 12:00 AM, aptalca said:

First, make a backup of your Plex data just in case (you can use the backup and restore plug-in)

 

The image/container structure should be compatible. Stop the other container, then just create a new container with the linuxserver image and point the config folder to the same folder the other container was pointing to. That's really it.

Thanks!!

 

 

14 minutes ago, TODDLT said:

yes just tried it, and worked fine.

 

Thanks!!

 

 

Did you just point it too the appdata folder on your cache 

5 hours ago, yanksno1 said:

Just wanted to double check, the version in the settings for this should be set to "docker" right to get the latest? 

 

I don't have this option in my docker container, how do i add this