As I stated, I have the code in hand.
I wish I had a GUI interface with QNAP to allow this to be configurable and give everyone the option of how they want it – but I don’t.
I’ll never be able to please everyone. Finding that “works for everyone without angering” is the catch and why I’m still contemplating.
If there is more feedback to help me decide / understand what everyone wants, Publishing the new packaging is easy.
I think if you set the expectation that it will operate a certain way and the reason, that will help smooth a lot of it out. Having things in context helps. Now that I know other platforms use PlexData share, I feel better about having it do it on QTS vs what it does natively. And, knowing that I can then use built-in capabilities to backup/replicate that directory solves my use case. I think that anyone using your code will probably have a similar use case, it’s for disaster recovery. Is the current version of the code published or is that something that will occur after you get the feedback you are looking for? Totally agree you’ll never please anyone, I work for a company that makes products that have a lot of devs behind it, so I know this all too well 
There was an earlier comment about Script Jockeys.
I’ve been one for some 35+ years now (Engineering). I have written some “killer” scripting in my days which, all by itself, goes out and surveys the LAN; identifies which hosts have useful data on them; mounts that data and makes it immediately available to the application – all without user intervention.
Doing that sort of thing is very hard-core Unix/Linux level work and it works well. Coming up with an equivalent for the ‘domestic’ customer hasn’t been so easy given these NAS boxes often are so grossly under powered and today’s consumer has very limited knowledge of what a CPU actually is / how it works / what its limits really are / (and unfortunately) how to actually use it .
Here is the link to the PlexData share
I will reopen if requested.
I would like to see the logs please.
If this truly is an iNotify problem, it will clearly show when restarting PMS
(make sure VERBOSE logging is OFF please – Only DEBUG ON)
I’ll be attempting a factory reset once I back my data up. Obviously something with either upgrading or downgrading is blocking the port from being open as you can see I’ve tried pretty much everything at this point.
We can also do it the console method:
Now you can see the console output as it starts. Any horrific errors will print there.
The path for 2. might vary depending on your install. I have it under /share/CE_CACHEDEV1_DATA/.qpkg/PlexMediaServer/
Any chance you can take that output and put it into a text file and attach to your original comment? That log is huge and takes a while to scroll past. Thanks!
Unless I am missing something, I see a discussion around the code but no attached .qpkg files or anything like that. I would request that the discussion be reopened - dane22’s original comments were that it is rare to see loss of data from uninstall of PMS, and that may be true, but as I quickly learned a failure of the NAS may have the same effect. I had only 2000 titles in my Plex but it’s going to take forever to get everything back the way it was because I had to modify at least several hundred subtitles and posters and info and fix matches… this is going to be an arduous task that I wish I could have been spared. This is important… There needs to be a good way to get this data properly backed up on a schedule. I would be happy to test this code and if needed, provide a write up with step-by-step instructions (including scheduled backup with QTS) so that others may reuse it more readily.
I have the same problem with my Synology NAS right now. A day ago it all worked just fine. I didn’t change any configuration in the mean time. Today when I try to access my Plex server in any way it doesn’t load. I wonder what’s wrong.
Hi Vcxy, if you didn’t upgrade PMS or the firmware on your box it’s probably a different problem. In fact, just because this thread is on QNAP I would be surprised if we find anything here that would be relevant to your issue. The prime suspect is buggy QNAP QTS firmware from all appearances, so that would not apply. I would recommend that you search synology threads and if you don’t see something applicable, create a new thread and provide logs from PMS so others can take a look.
Hi all.
I have not upgraded to 4.4.1.1117.
But my surprise has been that, this afternoon Plex did not work. It did not connect. Via terminal I have seen the following:
[admin@QTS PlexMediaServer]# ps -ef | grep -i plex
11325 admin 1040 S grep -i plex
26377 admin 147180 S ./Plex Media Server
31364 admin 72684 S /share/CACHEDEV2_DATA/.qpkg/Tautulli/bin/python Tautulli.py --daemon --port=8660 --datadir=/share/CACHEDEV2_DATA/.qpkg/Tautulli/DATADIR --config=/share/CACHEDEV2_DATA/.qpkg/Tautulli/CONFIGDIR/plexpy.conf
Only one Plex process. I kill the process.
[admin@QTS PlexMediaServer]# kill -9 26377
Start Plex.
[admin@QTS PlexMediaServer]# ./plex.sh start
Starting Plex Media Server…
[admin@QTS PlexMediaServer]# ps -ef | grep -i plex
13172 admin 50760 S ./Plex Media Server
13406 admin 28392 D Plex Plug-in [com.plexapp.system] /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-36236cc4c/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.18.2.2029-36236cc4c /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-36236cc4c/System.bundle
15337 admin 1036 S grep -i plex
31364 admin 77576 S /share/CACHEDEV2_DATA/.qpkg/Tautulli/bin/python Tautulli.py --daemon --port=8660 --datadir=/share/CACHEDEV2_DATA/.qpkg/Tautulli/DATADIR --config=/share/CACHEDEV2_DATA/.qpkg/Tautulli/CONFIGDIR/plexpy.conf
Everything works correctly.
Saludos.
strangely, Plex stopped working for me also. I only noticed when I got an email that Plex Media Server 1.18.2.2029 was available, so not sure exactly when it crashed since yesterday,
Yesterday I upgraded from 4.3.6.0993 to 4.3.6.1070 - I am now downgrading to see if it works again.
[edit: corrected PMS rev]
I’m on 1.18.2.2029 for PMS running on 4.3.6.1070 and all is working, but of course mine was rebuilt entirely from scratch. I did find initially that I couldn’t get GUI to load from QTS because I enabled forced HTTPS to QTS which then was using HTTPS for Plex which doesn’t work until you configure in PMS… so I changed HTTPS to HTTP and was able to get in, and then setup secure connection only and now I can get into PMS from QTS just fine. In any case, I can vouch that my version of PMS on 1070 QTS works.
OK, that’s good to know. It’s working again for me back on 1.18.12019, so I’ll try going back to 1070 again.
I know it was working immediately after I upgraded yesterday, but Plex has never crashed on my before and nothing else had changed (to my knowledge).
cheers.
I’m in direct contact with QNAP Engineering.
May I have info on model numbers, Yea/Nay with specific versions of QTS & PMS involved ?
TS-653A 8GB
For logs on why mine may have failed, my PMS logs are still linked on the 2nd post and available until 11/30.
TS-453bmini
All Plex released worked up to and including 4.3.6.0993
Plex crashed within a day of upgrading to 4.3.6.1070.
Plex working again having downgraded back to 4.3.6.0993. Will retry 1070 again tomorrow.
I don’t know if you resolved your issue. But in my case I found the info below and took out the s on my HTTP and the server is working. I can’t believe it.
If this is a first install, and after the install, you click on the Plex icon in the QNAP App-Center, in order to open the Plex Media Sever (PMS) page, you will fail due to the fact, that it tries to access PMS using the secure HTTPS protocol.
Sadly, unless claimed, PMS will only respond to pure HTTP calls, until claimed, and as such, simply remove the s from https://...
After claiming the PMS, all will work nicely
