Deleting the plugin and reinstalling PMS seems to have worked. TVDB and TVDBDVDOrder agents are now working correctly.
I backed up my library before doing this and also installed the new server via a manual jail rather than a plugin this time.
I also have the Plex Media Server folder linked via a storage mount of a ZFS dataset this time so if anything like this ever happens again I don’t have to back it all up (137,000 files) ( which took about 24 hours I-) ) before I reinstall. This is explained in the link on my previous post.
Strangely though the Plex Media Server folder used to be located in " /var/db/plexdata/ " when it was a plugin.
Now it is a manual jail the Plex Media Server folder is in " /usr/local/plexdata-plexpass/ "
Took me a while to figure this out, so might help someone else.
@treboR2Robert said:
Deleting the plugin and reinstalling PMS seems to have worked. TVDB and TVDBDVDOrder agents are now working correctly.
I backed up my library before doing this and also installed the new server via a manual jail rather than a plugin this time.
I also have the Plex Media Server folder linked via a storage mount of a ZFS dataset this time so if anything like this ever happens again I don’t have to back it all up (137,000 files) ( which took about 24 hours I-) ) before I reinstall. This is explained in the link on my previous post.
Strangely though the Plex Media Server folder used to be located in the " /var/db/plexdata/ " folder before when it was a plugin.
Now it is a manual jail the Plex Media Server folder is in " /usr/local/plexdata-plexpass/ "
Took me a while to figure this out, so might help someone else.
I also installed Plex in a jail. I kept the original install in case the Plex employee decides to test a fix. I didn’t create a storage mount for my Plex Media Server. The file size was around 50GB and took about an hour to rsync to the new folder.
I refreshed my library which fixed all the unmatched shows. Everything seems to work now.
@treboR2Robert said:
Deleting the plugin and reinstalling PMS seems to have worked. TVDB and TVDBDVDOrder agents are now working correctly.
I backed up my library before doing this and also installed the new server via a manual jail rather than a plugin this time.
I also have the Plex Media Server folder linked via a storage mount of a ZFS dataset this time so if anything like this ever happens again I don’t have to back it all up (137,000 files) ( which took about 24 hours I-) ) before I reinstall. This is explained in the link on my previous post.
Strangely though the Plex Media Server folder used to be located in the " /var/db/plexdata/ " folder before when it was a plugin.
Now it is a manual jail the Plex Media Server folder is in " /usr/local/plexdata-plexpass/ "
Took me a while to figure this out, so might help someone else.
I also installed Plex in a jail. I kept the original install in case the Plex employee decides to test a fix. I didn’t create a storage mount for my Plex Media Server. The file size was around 50GB and took about an hour to rsync to the new folder.
I refreshed my library which fixed all the unmatched shows. Everything seems to work now.
Yes I was told to use rsync too but all the code scarred me lol. I wasn’t expecting the 24 hour wait though with windows or I would have braved rsync.
I need to learn how to use freenas properly lol
That is why I decided to reinstall Plex which fixed the issue. This problem is only for a small subset of Plex users, so it will be a very low priority.
Only thing I cannot figure out is why “pkg update” isn’t detecting that there is an update to Plex. The FreshPorts website shows 1.3.4. I even did “pkg update -f”. It is like it is not in the repository yet.
I have plexmediaserver_plexpass installed in standard jail - is there deinstall/reinstall procedure that fixes this without having to nuke the library and start from scratch?
I tried pkg uninstall and deinstall from ports, but after reinstalling it’s still having tvdb problems…
I used the plex function to back up the database. I uninstalled the plugin and reinstalled it. I mapped the folders back to Plex and did a database import. Did the trick for me.
@treboR2Robert said:
So I just deleted a show from my tv shows folder. I then refreshed the tv library on plex so it was gone completely and then I also emptied the trash.
EDIT ! I also disabled logging and deleted all the previous old logs.
I then enabled logging, copied the show back to my tv shows folder and refreshed the plex tv library once again.
I have added 2 pictures showing what is there and also the tvdb log
Same identical problem as your pics! It only downloads the correct name(in Italian in my case) and the cover. If I force to use TheMovieDB as scraper it works very well. The problem is only with TheTVDB
PS: I’m on a QNAP NAS with the latest version of PLEX for Intel
For those of you with issues can you check if you have an ssl.py file in your <PMS_BINARIES>/Resources/lib/python2.7 folder?
Depending on OS the binaries will be in different places. If there is an ssl.py file. Stop PMS. Delete it, and install a fresh Plex binary on top of your install. That could fix it.
Well, I had the file at /usr/local/share/plexmediaserver-plexpass/Resources/Python/lib/python2.7/, moved it to my home (chickening out from deleting :-)), reinstalled the port (1.3.4) and lo and behold: It looks like it is working perfectly.
I broke down and backed up my plex instance, turned off the existing instance, installed a new one, then restored the backup files to the new instance. It worked like a charm. I was really hoping I could have avoided it, but it doesn’t seem like Plex is listening to this thread at all, and it is really annoying to not get updated episode information.
@hafnera said:
… but it doesn’t seem like Plex is listening to this thread at all…
C’mon man! This is just wrong. A Plex employee replied to this thread a say before your post with a possible fix (That others have said fix it for them).
Just to follow completely up on this. For those who aren’t comfortable manually doing this fix or prefer to wait. The issue will be fixed in our next 1.4.1 release and later. We will in our next release be overwriting the ssl.py file with the correct one. So as a note once 1.4.1 is out the will be no need to manually remove the ssl.py file.
@ziggimon said:
Just to follow completely up on this. For those who aren’t comfortable manually doing this fix or prefer to wait. The issue will be fixed in our next 1.4.1 release and later. We will in our next release be overwriting the ssl.py file with the correct one. So as a note once 1.4.1 is out the will be no need to manually remove the ssl.py file.
That is good news.
For those of us who completly reinstalled though with version 1.3.3 is it safe to update to newer versions like 1.3.4 ?
This is likely a stupid question, but I’m not following one of the steps here to correct. I’m running Plex in a FreeNAS jail, am able to delete/move the ssl.py file, but am not clear on what is meant by “reinstall the port” or “ran the latest update again”. Anyone know how to do this via FreeNAS? Can I just update the software within Plex using the GUI, or do I need to update it via the command line…? Thanks in advance…
Originally back in the 0.9.x days were were shipping our python files as .py files. At some point around 0.9.x -> 1.0.x we changed to ship .pyc (compiled python files). This is usually not a problem, but what happened on some systems is that when the Plex Media Server package is installed the devices package system does not clean up/out after the previous files installed, so in certain cases systems ended up with the old .py files and the new .pyc files. For the python lib files that wasn’t a case for a long time because we didn’t bump the server version of python. In the 1.3.x series we did exactly that. But since we are/were still shipping .pyc files, what happens is that the way python chooses which file to use is by comparing the internal time stamp of the compiled python code (.pyc) to the time stamp of the .py file, and if they don’t match it uses the .py file instead, thus causing PMS to use the old 2.7 version and not the latest 2.7.12 version that we compiled into the .pyc file.
In the next release we have moved back to shipping the .py files with python lib so that can never happen again. The compiled python files seemed like a smart idea at the time, but we didn’t foresee that some platforms would leave files behind. We are now a lesson wiser and a fix richer.
So users that did clean installs to fix are still safe to move to latest PMS release. And if in doubt wait for the 1.4.1 or later release.
